An exact transfer event matches the declared amount and recipient.
TableProof independent agent tools
Base native USDC · evidence, before totals
Three payout claims.
One transfer counted twice?
Compare exact recipient, atomic amount and optional sender against public transfer events. Catch reused evidence before your agent treats separate claims as separate payouts.
The same event also matches B. It cannot prove a second payout.
A different amount has no exact match in the returned successful receipt.
Invented example. These cards describe a synthetic fixture, not transactions or customers. Inspect the full example JSON.
Check your public claims
0.05 USDC on Base per completed batch of 1–3 claims
POST /v1/payout-claims using an x402-compatible client and its own purchase permissions. A regular browser link does not authorize payment. Native Dots purchase support and compatibility are unverified.
{"claims":[{"id":"invoice-a","tx_hash":"0x…64 hex digits…","recipient":"0x…40 hex digits…","amount_atomic":"50000"}]}Amounts are positive decimal strings in USDC atomic units. Never send a private key, signed transaction, account credential or private invoice. Only public hashes and addresses are needed.
Request schema and HTTP contract · Price and payment requirements
A transfer is one piece of evidence
The result distinguishes observed transfers, unmatched claims, failed transactions and unknown observations. Missing receipts remain unknown. If any observation is unknown, this endpoint returns503 and the current payment middleware skips settlement. A completed check can report a mismatch; the price is for checking, not for obtaining a positive match.
This reads one fixed public RPC. It does not verify finality, canonical blocks, party identities, delivery, ownership or USD conversion. It never sends a transaction or totals earned USD. Duplicate evidence is reported by event ID.
Maximum16000UTF8 request bytes,3claims,1000logs per receipt and262144bytes per RPC response. Request contents are not stored. Only successful settlement-response counts are recorded in aggregate; counters are not proof of earned USD. Actual paid settlement has not yet been independently exercised.Free unsigned payment-terms checker · Free CSV structure check
Tried this tool? Share optional anonymous feedback. Nothing is sent until you choose an experience and submit. No order or follow-up is created.