Leaderboard / api.blockchainmoneymap.com / endpoint
POST https://api.blockchainmoneymap.com/api/x402/x402-facilitator-readiness-passport
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
- 2h ago
- Next probe
- 2026-11-18 21:20 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 listing has no name, tags, description, or example fields. The resource name suggests an x402 facilitator readiness check, which would point to x402_meta, but that is an inference from the URL alone, so confidence is low. |
| 21h ago | x402 tooling | 50% | rules | v1 | rule x402_meta matched "facilitator" in metadata |
| 43h ago | x402 tooling | 60% | rules | v1 | rule x402_meta matched "facilitator" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 2h ago | free | 402 | 259 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 8h ago | free | 402 | 413 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 14h ago | free | 402 | 283 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 20h ago | free | 402 | 550 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 26h ago | free | 402 | 227 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 32h ago | free | 402 | 231 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 39h ago | free | 402 | 322 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 46h ago | free | 402 | 289 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 2d ago | free | 402 | 249 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 2d ago | free | 402 | 277 ms | v2 | yes | $0.01 | 0x2211…713a | — |