Leaderboard / agent402.tools / endpoint
POST https://agent402.tools/api/receipts
Scores measure reliability and honesty, not output quality.
- Listed only 3 days ago; new listings earn trust over 30 days.
- Answered all 13 probes in the last 7 days.
- Category
- x402 tooling by llm, confidence 60%
- Latest quote
- $0.005 on Base to 0xaBF4…a9D0
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- Observed
- none reported yet (opt-in wrapper telemetry)
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 3h ago
- Next probe
- 2026-11-19 14:35 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.005 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | Polygon | 0x3c49…3359 | 5000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | Arbitrum | 0xaf88…5831 | 5000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | eip155:143 | 0x7547…b603 | 5000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | eip155:5042 | 0x3600…0000 | 5000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| payai | exact | Base | 0x8335…2913 | $0.005 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | Avalanche | 0xB97E…8a6E | 5000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | eip155:42220 | 0xcebA…118C | 5000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | eip155:1329 | 0xe15f…2392 | 5000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | eip155:10 | 0x0b2C…Ff85 | 6000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | eip155:4663 | 0x5fc5…d168 | 10000 | 0xaBF4…a9D0 | default | yes | 5h ago |
| cdp | exact | eip155:57073 | 0x2D27…EAEd | 5000 | 0xaBF4…a9D0 | default | yes | 5h ago |
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 40h ago | description_changed | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. Keyed to the wallet that pays for the call, so nobody can read another wallet's payables; no account, no export request, no support ticket. Requires an EIP-3009 payment (USDC on Base, Polygon, or Arbitrum). | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. |
| 40h ago | description_changed | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. Keyed to the wallet that pays for the call, so nobody can read another wallet's payables; no account, no export request, no support ticket. Requires an EIP-3009 payment (USDC on Base, Polygon, or Arbitrum). | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. |
| 40h ago | description_changed | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. Keyed to the wallet that pays for the call, so nobody can read another wallet's payables; no account, no export request, no support ticket. Requires an EIP-3009 payment (USDC on Base, Polygon, or Arbitrum). | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. |
| 40h ago | price_changed | 5000 | 10000 |
| 40h ago | description_changed | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. Keyed to the wallet that pays for the call, so nobody can read another wallet's payables; no account, no export request, no support ticket. Requires an EIP-3009 payment (USDC on Base, Polygon, or Arbitrum). | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. |
| 40h ago | description_changed | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. Keyed to the wallet that pays for the call, so nobody can read another wallet's payables; no account, no export request, no support ticket. Requires an EIP-3009 payment (USDC on Base, Polygon, or Arbitrum). | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. |
| 40h ago | description_changed | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. Keyed to the wallet that pays for the call, so nobody can read another wallet's payables; no account, no export request, no support ticket. Requires an EIP-3009 payment (USDC on Base, Polygon, or Arbitrum). | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. |
| 40h ago | description_changed | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. Keyed to the wallet that pays for the call, so nobody can read another wallet's payables; no account, no export request, no support ticket. Requires an EIP-3009 payment (USDC on Base, Polygon, or Arbitrum). | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. |
| 40h ago | description_changed | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. Keyed to the wallet that pays for the call, so nobody can read another wallet's payables; no account, no export request, no support ticket. Requires an EIP-3009 payment (USDC on Base, Polygon, or Arbitrum). | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. |
| 40h ago | description_changed | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. Keyed to the wallet that pays for the call, so nobody can read another wallet's payables; no account, no export request, no support ticket. Requires an EIP-3009 payment (USDC on Base, Polygon, or Arbitrum). | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. |
| 40h ago | description_changed | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. Keyed to the wallet that pays for the call, so nobody can read another wallet's payables; no account, no export request, no support ticket. Requires an EIP-3009 payment (USDC on Base, Polygon, or Arbitrum). | Your own settled calls in the shape a finance system posts: one row per payment with what was bought, the amount settled, the quoted ceiling where one applied, and the evidence - settlement transaction, sha256 of the bytes delivered, and the on-chain attestation id where one exists. |
Paid probes
No paid probes yet. Paid probing is off by default and runs weekly per host under a strict spend cap; each paid probe links to its on-chain transaction here.
Delivery checks
Inside each paid probe we ask for something whose correct answer we know, then compare. A pass means the seller delivered what it was paid for; a fail means it charged and returned something wrong; inconclusive means we could not judge (no reference, unknown input shape, or a non-2xx response). Every row carries the request, the response hash and the reference so the verdict can be reproduced. Judged results feed the "Delivery after payment" component (pass 1, error after payment 0.25, fail 0); inconclusive rows are excluded; a fail in the last 14 days caps the verdict at caution. Methodology.
No delivery checks yet. They run inside the weekly paid probe.
Classification history
Every classification is kept; the newest row is the current category. Rules match the listing text; the model is consulted only when the rules are unsure.
| When | Category | Confidence | Method | Version | Evidence |
|---|---|---|---|---|---|
| 39h ago | x402 tooling | 60% | llm | v1 | claude-haiku-5-5: The endpoint returns a caller's own settled x402 payment records (settlement transactions, quoted ceilings, delivery hashes) for accounting and reconciliation. That is payment-tooling metadata about x402 calls rather than a commerce listing or compliance check, so x402_meta is the closest fit, though the finance-accounting framing gives some ambiguity. |
| 39h ago | Data transform | 60% | rules | v1 | rule data_transform matched "sha256" in description |
| 45h ago | x402 tooling | 60% | llm | v1 | claude-haiku-5-5: The endpoint returns a wallet's own settled x402 payment records (receipts, settlement transactions, delivery hashes), which is payment accounting tooling rather than any data domain. Closest fit is x402_meta for payment-header and payment-related tools, though 'compliance' or 'commerce' are possible alternatives, so confidence is moderate. |
| 3d ago | x402 tooling | 60% | rules | v1 | rule x402_meta matched "eip-3009" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 3h ago | free | 402 | 54 ms | v2 | yes | $0.005 | 0xaBF4…a9D0 | — |
| 9h ago | free | 402 | 798 ms | v2 | yes | $0.005 | 0xaBF4…a9D0 | — |
| 15h ago | free | 402 | 1609 ms | v2 | yes | $0.005 | 0xaBF4…a9D0 | — |
| 23h ago | free | 402 | 20 ms | v2 | yes | $0.005 | 0xaBF4…a9D0 | — |
| 29h ago | free | 402 | 92 ms | v2 | yes | $0.005 | 0xaBF4…a9D0 | — |
| 35h ago | free | 402 | 363 ms | v2 | yes | $0.005 | 0xaBF4…a9D0 | — |
| 41h ago | free | 402 | 395 ms | v2 | yes | $0.005 | 0xaBF4…a9D0 | — |
| 2d ago | free | 402 | 372 ms | v2 | yes | $0.005 | 0xaBF4…a9D0 | — |
| 2d ago | free | 402 | 51 ms | v2 | yes | $0.005 | 0xaBF4…a9D0 | — |
| 3d ago | free | 402 | 23 ms | v2 | yes | $0.005 | 0xaBF4…a9D0 | — |
| 3d ago | free | 402 | 354 ms | v2 | yes | $0.005 | 0xaBF4…a9D0 | — |
| 3d ago | free | 402 | 22 ms | v2 | yes | $0.005 | 0xaBF4…a9D0 | — |
| 3d ago | free | 402 | 23 ms | v2 | yes | $0.005 | 0xaBF4…a9D0 | — |