Tx Receipt Verify
by ReceiptSure in Onchain & crypto
Check whether a mined Base transaction did what your agent meant it to do. Fetches the receipt, decodes its ERC-20, ERC-721 and ERC-1155 transfer and approval logs, and reports each declared movement as matched, missing or short, with the observed amount beside the expected one. Catches reverts, success with no effect, fee-on-transfer skims and transfers to recipients you never named. Returns unknown rather than guessing. Not a guarantee that a transaction was safe.
https://receipt.schemasure.com/v1/tx/receipt-verify- Price
- $0.02
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 357 ms
- 479 ms slowest 5%
- Last check
- Passed
- 3 h ago, next any minute now
Reliability
How to call it
POST https://receipt.schemasure.com/v1/tx/receipt-verify
Each call costs $0.02 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://receipt.schemasure.com/v1/tx/receipt-verify
content-type: application/json
{
"expected_transfers": [
{
"amount": "10000",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"from": "0x9F2C5E4A8db1C3a7E6B0d4f8C1E2a5b7D9C0e3F4",
"to": "0x5d3e1a9b7c2f4e8a0b6d3c5f9e1a7b4d2c8f0a6e"
}
],
"tx_hash": "0x7f1c3a58e0b94d26c5af7318d0e42b96c1d85f0a3b72e648d9c05147ae2b6f30"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
expected_transfers | array of object | Yes | What you intended to move. Each entry is checked against the decoded logs and reported as matched, missing, short, or unverifiable. |
tx_hash | string | Yes | The Base transaction to check. A hash with no receipt yet answers unknown. |
Example response
The provider's example. We can't check it without paying.
Example response, 49 lines
{
"confidence": 1,
"data_versions": {
"denylist": "2026-08-03.1",
"event_abis": "2026-09-19.1",
"policy": "2026-09-19"
},
"ok": true,
"policy_version": "2026-09-19",
"request_hash": "sha256:3f9c…a71e",
"result": {
"effect": {
"has_logs": true,
"silent_success": false
},
"fee_on_transfer": [
{
"implied_fee_percent": "1.00%",
"skimmed_base_units": "100"
}
],
"receipt": {
"log_count": 2,
"status": "success"
},
"revert": {
"reason": null,
"reverted": false
},
"transfer_checks": [
{
"amounts": {
"expected_base_units": "10000",
"observed_base_units": "9900",
"shortfall_base_units": "100"
},
"status": "amount_mismatch"
}
],
"unexpected_recipients": [],
"unresolved": []
},
"risk_codes": [
"AMOUNT_MISMATCH",
"FEE_ON_TRANSFER_SKIM"
],
"verdict": "block",
"warnings": []
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.02.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://receipt.schemasure.com/v1/tx/receipt-verify' \
-H 'content-type: application/json' \
--data-raw '{"expected_transfers":[{"amount":"10000","asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","from":"0x9F2C5E4A8db1C3a7E6B0d4f8C1E2a5b7D9C0e3F4","to":"0x5d3e1a9b7c2f4e8a0b6d3c5f9e1a7b4d2c8f0a6e"}],"tx_hash":"0x7f1c3a58e0b94d26c5af7318d0e42b96c1d85f0a3b72e648d9c05147ae2b6f30"}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://receipt.schemasure.com/v1/tx/receipt-verify' \
-H 'content-type: application/json' \
--data-raw '{"expected_transfers":[{"amount":"10000","asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","from":"0x9F2C5E4A8db1C3a7E6B0d4f8C1E2a5b7D9C0e3F4","to":"0x5d3e1a9b7c2f4e8a0b6d3c5f9e1a7b4d2c8f0a6e"}],"tx_hash":"0x7f1c3a58e0b94d26c5af7318d0e42b96c1d85f0a3b72e648d9c05147ae2b6f30"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Freceipt.schemasure.com%2Fv1%2Ftx%2Freceipt-verify&method=POST
const res = await pay("https://receipt.schemasure.com/v1/tx/receipt-verify", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"expected_transfers": [
{
"amount": "10000",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"from": "0x9F2C5E4A8db1C3a7E6B0d4f8C1E2a5b7D9C0e3F4",
"to": "0x5d3e1a9b7c2f4e8a0b6d3c5f9e1a7b4d2c8f0a6e"
}
],
"tx_hash": "0x7f1c3a58e0b94d26c5af7318d0e42b96c1d85f0a3b72e648d9c05147ae2b6f30"
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://receipt.schemasure.com/v1/tx/receipt-verify",
json={
"expected_transfers": [
{
"amount": "10000",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"from": "0x9F2C5E4A8db1C3a7E6B0d4f8C1E2a5b7D9C0e3F4",
"to": "0x5d3e1a9b7c2f4e8a0b6d3c5f9e1a7b4d2c8f0a6e",
},
],
"tx_hash": "0x7f1c3a58e0b94d26c5af7318d0e42b96c1d85f0a3b72e648d9c05147ae2b6f30",
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 h ago | Passed | 402 | 325 ms | $0.02 |
| 7 h ago | Passed | 402 | 450 ms | $0.02 |
| 11 h ago | Passed | 402 | 443 ms | $0.02 |
| 15 h ago | Passed | 402 | 395 ms | $0.02 |
| 19 h ago | Passed | 402 | 483 ms | $0.02 |
Show 10 older checks
| 23 h ago | Passed | 402 | 330 ms | $0.02 |
| 27 h ago | Passed | 402 | 357 ms | $0.02 |
| 31 h ago | Passed | 402 | 434 ms | $0.02 |
| 34 h ago | Passed | 402 | 440 ms | $0.02 |
| 38 h ago | Passed | 402 | 337 ms | $0.02 |
| 42 h ago | Passed | 402 | 320 ms | $0.02 |
| 45 h ago | Passed | 402 | 274 ms | $0.02 |
| 2 days ago | Passed | 402 | 334 ms | $0.02 |
| 2 days ago | Passed | 402 | 298 ms | $0.02 |
| 2 days ago | Passed | 402 | 457 ms | $0.02 |