Leaderboard / atomic-verify-claim-poc.topadvancement-atomic.workers.dev / endpoint
POST https://atomic-verify-claim-poc.topadvancement-atomic.workers.dev/api/resolve-redirect-chain
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 9 probes in the last 7 days.
- Category
- DNS and domains by llm, confidence 60%
- Latest quote
- $0.01 on Base to 0x16F6…2B11
- 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
- 55m ago
- Next probe
- 2026-11-18 12:08 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.01 | 0x16F6…2B11 | default | yes | 2h 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 |
|---|---|---|---|---|---|
| 30h ago | DNS and domains | 60% | llm | v1 | claude-haiku-5-5: The endpoint follows a URL's redirect chain and returns per-hop HTTP status, final URL and safety findings, which is closest to network/domain infrastructure inspection. It is not a page scrape or a site audit of supplied security headers, so dns_domain fits best, though web_audit is a plausible alternative. |
| 33h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 55m ago | free | 402 | 658 ms | v2 | yes | $0.01 | 0x16F6…2B11 | — |
| 7h ago | free | 402 | 416 ms | v2 | yes | $0.01 | 0x16F6…2B11 | — |
| 14h ago | free | 402 | 535 ms | v2 | yes | $0.01 | 0x16F6…2B11 | — |
| 20h ago | free | 402 | 726 ms | v2 | yes | $0.01 | 0x16F6…2B11 | — |
| 27h ago | free | 402 | 429 ms | v2 | yes | $0.01 | 0x16F6…2B11 | — |
| 33h ago | free | 402 | 688 ms | v2 | yes | $0.01 | 0x16F6…2B11 | — |
| 39h ago | free | 402 | 1295 ms | v2 | yes | $0.01 | 0x16F6…2B11 | — |
| 45h ago | free | 402 | 372 ms | v2 | yes | $0.01 | 0x16F6…2B11 | — |
| 2d ago | free | 402 | 706 ms | v2 | yes | $0.01 | 0x16F6…2B11 | — |