Leaderboard / api.blockchainmoneymap.com / endpoint
POST https://api.blockchainmoneymap.com/api/x402/wallet-audit
Scores measure reliability and honesty, not output quality.
- Listed only 3 days ago; new listings earn trust over 30 days.
- Answered all 12 probes in the last 7 days.
- Category
- Other by llm, confidence 30%
- Latest quote
- $1 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
- 1m ago
- Next probe
- 2026-11-19 14:40 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 37h 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 |
|---|---|---|---|---|---|
| 37h ago | Other | 30% | llm | v1 | claude-haiku-5-5: The host and path suggest a wallet audit, which would likely be a chain-related or crypto-security check, but there is no description, tags, or example input to confirm what it returns. The listing says too little to classify with confidence. |
| 37h ago | Other | 20% | rules | v1 | rule none matched "" in none |
| 2d ago | Chain read | 60% | llm | v1 | claude-haiku-5-5: The endpoint audits wallets using onchain data (address, chain inputs, wallet snapshots and analysis), which returns on-chain account information. The description is generic and the tags also suggest wallet intelligence reporting, so confidence is moderate. |
| 2d ago | Chain read | 60% | rules | v1 | rule chain_read matched "in:address" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 1m ago | free | 402 | 146 ms | v2 | yes | $1 | 0x2211…713a | — |
| 6h ago | free | 402 | 307 ms | v2 | yes | $1 | 0x2211…713a | — |
| 13h ago | free | 402 | 149 ms | v2 | yes | $1 | 0x2211…713a | — |
| 20h ago | free | 402 | 425 ms | v2 | yes | $1 | 0x2211…713a | — |
| 26h ago | free | 402 | 226 ms | v2 | yes | $1 | 0x2211…713a | — |
| 33h ago | free | 402 | 164 ms | v2 | yes | $1 | 0x2211…713a | — |
| 39h ago | free | 402 | 220 ms | v2 | yes | $1 | 0x2211…713a | — |
| 46h ago | free | 402 | 186 ms | v2 | yes | $1 | 0x2211…713a | — |
| 2d ago | free | 402 | 274 ms | v2 | yes | $1 | 0x2211…713a | — |
| 2d ago | free | 402 | 184 ms | v2 | yes | $1 | 0x2211…713a | — |
| 3d ago | free | 402 | 290 ms | v2 | yes | $1 | 0x2211…713a | — |
| 3d ago | free | 402 | 249 ms | v2 | yes | $1 | 0x2211…713a | — |
| 3d ago | free | 402 | 161 ms | v2 | yes | $1 | 0x2211…713a | — |