Leaderboard / api.blockchainmoneymap.com / endpoint
POST https://api.blockchainmoneymap.com/api/x402/agent-compatibility-analyzer
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.25 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:49 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 service name, tags, description, or example inputs. The resource name 'agent-compatibility-analyzer' hints at analyzing agent or software compatibility, which does not map cleanly to any listed category, so the classification is low confidence. |
| 21h ago | Other | 20% | rules | v1 | rule none matched "" in none |
| 27h ago | x402 tooling | 60% | llm | v1 | claude-haiku-5-5: The endpoint diagnoses failed or malformed agent requests (error codes, HTTP status, request headers) and returns fix steps and corrected request templates, which is tooling for x402/agent API integration rather than any data domain. It fits x402_meta best, though the description is short and it is not explicitly an x402 checker. |
| 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 | 305 ms | v2 | yes | $0.25 | 0x2211…713a | — |
| 10h ago | free | 402 | 296 ms | v2 | yes | $0.25 | 0x2211…713a | — |
| 17h ago | free | 402 | 213 ms | v2 | yes | $0.25 | 0x2211…713a | — |
| 23h ago | free | 402 | 304 ms | v2 | yes | $0.25 | 0x2211…713a | — |
| 30h ago | free | 402 | 213 ms | v2 | yes | $0.25 | 0x2211…713a | — |
| 36h ago | free | 402 | 196 ms | v2 | yes | $0.25 | 0x2211…713a | — |
| 42h ago | free | 402 | 188 ms | v2 | yes | $0.25 | 0x2211…713a | — |
| 2d ago | free | 402 | 153 ms | v2 | yes | $0.25 | 0x2211…713a | — |
| 2d ago | free | 402 | 236 ms | v2 | yes | $0.25 | 0x2211…713a | — |
| 3d ago | free | 402 | 181 ms | v2 | yes | $0.25 | 0x2211…713a | — |