Leaderboard / api.blockchainmoneymap.com / endpoint
POST https://api.blockchainmoneymap.com/api/devagentpal/recursive-commerce-loop-breaker
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.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
- 4h ago
- Next probe
- 2026-11-18 18:57 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 resource path 'recursive-commerce-loop-breaker' hints at commerce-related tooling but gives too little information to classify it confidently. |
| 21h ago | Public data | 50% | rules | v1 | rule public_data matched "e-commerce" in metadata |
| 27h ago | Compliance | 55% | llm | v1 | claude-haiku-5-5: The endpoint vets a proposed autonomous purchase against policy limits, delegation depth and spend bounds, which is a control or risk-gating check rather than commerce listing or signal output. Compliance is the closest fit, though it is agent-commerce governance and could plausibly be labeled other. |
| 43h ago | Public data | 50% | rules | v1 | rule public_data matched "e-commerce" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 4h ago | free | 402 | 181 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 10h ago | free | 402 | 190 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 17h ago | free | 402 | 176 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 23h ago | free | 402 | 379 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 29h ago | free | 402 | 233 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 36h ago | free | 402 | 174 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 42h ago | free | 402 | 202 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 2d ago | free | 402 | 194 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 2d ago | free | 402 | 172 ms | v2 | yes | $0.01 | 0x2211…713a | — |
| 3d ago | free | 402 | 195 ms | v2 | yes | $0.01 | 0x2211…713a | — |