Leaderboard / api.blockchainmoneymap.com / endpoint
POST https://api.blockchainmoneymap.com/api/x402/x402-response-contract-linter
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 10 probes in the last 7 days.
- Category
- Other by llm, confidence 15%
- Latest quote
- $0.01 on Base to 0x2211…713a
- 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
- 4h ago
- Next probe
- 2026-11-18 18:52 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 21h ago | disappeared | — | — |
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 |
|---|---|---|---|---|---|
| 21h ago | Other | 15% | llm | v1 | claude-haiku-5-5: The resource name suggests an x402 response contract linter, which would fit x402_meta, but the listing has no description, tags, or example fields, so the name alone is the only evidence and the purpose is uncertain. |
| 21h ago | Other | 20% | rules | v1 | rule none matched "" in none |
| 27h ago | x402 tooling | 80% | llm | v1 | claude-haiku-5-5: The endpoint lints caller-submitted x402 and agent API response samples for contract completeness, which is an x402 payment-protocol tooling function, so x402_meta fits best despite it being a generic linter. |
| 43h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 4h ago | free | 402 | 188 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 10h ago | free | 402 | 177 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 16h ago | free | 402 | 197 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 23h ago | free | 402 | 310 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 30h ago | free | 402 | 336 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 36h ago | free | 402 | 206 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 42h ago | free | 402 | 190 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 2d ago | free | 402 | 173 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 2d ago | free | 402 | 289 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 3d ago | free | 402 | 158 ms | v2 | yes | $0.01 | 0x2211…713a | — |