Leaderboard / agent-data-tools.revmesh2074.workers.dev / endpoint
GET https://agent-data-tools.revmesh2074.workers.dev/pack/api-health
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 8 probes in the last 7 days.
- Category
- x402 tooling by llm, confidence 50%
- Latest quote
- $0.01 on Base to 0x6293…f800
- 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 05:56 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Arbitrum | 0xaf88…5831 | 10000 | 0x6293…f800 | default | yes | 5h ago |
| cdp | exact | Base | 0x8335…2913 | $0.01 | 0x6293…f800 | default | yes | 5h ago |
| cdp | exact | Polygon | 0x3c49…3359 | 10000 | 0x6293…f800 | default | yes | 5h ago |
| cdp | exact | Solana | EPjFWd…Dt1v | 10000 | 82wfSC…a9Q6 | default | yes | 5h 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 |
|---|---|---|---|---|---|
| 20h ago | x402 tooling | 50% | llm | v1 | claude-haiku-5-5: The endpoint health-checks a supplied API URL, reporting uptime, latency, redirects, security headers, and x402 payment terms. That most closely matches web_audit (audit of a URL you supply), but its explicit x402 endpoint detection and payment-terms reporting also fit x402_meta. It is a monitoring check rather than a pure site audit, so confidence is moderate. |
| 30h ago | x402 tooling | 60% | rules | v1 | rule x402_meta matched "x402 endpoint" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 4h ago | free | 402 | 25 ms | v2 | yes | $0.01 | 0x6293…f800 | — |
| 10h ago | free | 402 | 343 ms | v2 | yes | $0.01 | 0x6293…f800 | — |
| 17h ago | free | 402 | 1732 ms | v2 | yes | $0.01 | 0x6293…f800 | — |
| 23h ago | free | 402 | 97 ms | v2 | yes | $0.01 | 0x6293…f800 | — |
| 29h ago | free | 402 | 80 ms | v2 | yes | $0.01 | 0x6293…f800 | — |
| 35h ago | free | 402 | 25 ms | v2 | yes | $0.01 | 0x6293…f800 | — |
| 41h ago | free | 402 | 21 ms | v2 | yes | $0.01 | 0x6293…f800 | — |
| 47h ago | free | 402 | 25 ms | v2 | yes | $0.01 | 0x6293…f800 | — |