Leaderboard / api.blockchainmoneymap.com / endpoint
POST https://api.blockchainmoneymap.com/api/devagentpal/human-intent-checksum
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 10%
- Latest quote
- $0.05 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 19:04 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 | 10% | llm | v1 | claude-haiku-5-5: The listing has no service name, tags, description, or example fields. The path 'human-intent-checksum' hints at a checksum or hashing utility, but that is speculative, so the endpoint cannot be classified with confidence and falls under other. |
| 21h ago | Data transform | 50% | rules | v1 | rule data_transform matched "checksum" in metadata |
| 27h ago | Data transform | 45% | llm | v1 | claude-haiku-5-5: The endpoint issues or verifies a canonical checksum and deterministic constraints for a mandate, which is deterministic transform-like output; however, the signature trust-policy and mandate framing is ambiguous and could also fit compliance or other, so confidence is moderate. |
| 43h ago | Data transform | 60% | rules | v1 | rule data_transform matched "checksum" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 4h ago | free | 402 | 191 ms | v2 | yes | $0.05 | 0x2211…713a | — |
| 10h ago | free | 402 | 201 ms | v2 | yes | $0.05 | 0x2211…713a | — |
| 17h ago | free | 402 | 192 ms | v2 | yes | $0.05 | 0x2211…713a | — |
| 23h ago | free | 402 | 282 ms | v2 | yes | $0.05 | 0x2211…713a | — |
| 30h ago | free | 402 | 297 ms | v2 | yes | $0.05 | 0x2211…713a | — |
| 36h ago | free | 402 | 184 ms | v2 | yes | $0.05 | 0x2211…713a | — |
| 42h ago | free | 402 | 194 ms | v2 | yes | $0.05 | 0x2211…713a | — |
| 2d ago | free | 402 | 144 ms | v2 | yes | $0.05 | 0x2211…713a | — |
| 2d ago | free | 402 | 176 ms | v2 | yes | $0.05 | 0x2211…713a | — |
| 3d ago | free | 402 | 200 ms | v2 | yes | $0.05 | 0x2211…713a | — |