Leaderboard / api.blockchainmoneymap.com / endpoint
POST https://api.blockchainmoneymap.com/api/x402/x402-agent-commerce-digital-twin
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 35%
- 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
- 58m ago
- Next probe
- 2026-11-18 22:07 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.01 | 0x2211…713a | default | yes | 6h ago |
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 | 35% | llm | v1 | claude-haiku-5-5: The description says it builds a sanitized simulation twin of an agent-commerce mission before payment or execution, which fits no clear category. It is closest to compliance or x402_meta, but the listing gives too little concrete output detail to choose confidently, so it is classed as other with low confidence. |
| 43h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 58m ago | free | 402 | 489 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 7h ago | free | 402 | 327 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 13h ago | free | 402 | 407 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 19h ago | free | 402 | 352 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 26h ago | free | 402 | 242 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 32h ago | free | 402 | 201 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 39h ago | free | 402 | 245 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 46h ago | free | 402 | 493 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 2d ago | free | 402 | 238 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 2d ago | free | 402 | 389 ms | v2 | yes | $0.01 | 0x2211…713a | — |