Leaderboard / amanchain-relay.gitajhd.workers.dev / endpoint
POST https://amanchain-relay.gitajhd.workers.dev/api/x402/aman-email-validate
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
- Email by llm, confidence 90%
- Latest quote
- $0.007476 on Base to 0xfB56…2f39
- 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
- 5h ago
- Next probe
- 2026-11-18 05:30 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.007476 | 0xfB56…2f39 | default | yes | 6m 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 |
|---|---|---|---|---|---|
| 28h ago | 90% | llm | v1 | claude-haiku-5-5: The endpoint is an email validation API covering syntax checks, MX record verification and disposable-email detection, so it fits the email category. The description's boilerplate about on-chain execution does not change what the caller receives. | |
| 31h ago | 60% | rules | v1 | rule email matched "email validation api — syntax check" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 5h ago | free | 402 | 420 ms | v2 | yes | $0.007476 | 0xfB56…2f39 | — |
| 12h ago | free | 402 | 290 ms | v2 | yes | $0.007476 | 0xfB56…2f39 | — |
| 18h ago | free | 402 | 736 ms | v2 | yes | $0.007476 | 0xfB56…2f39 | — |
| 24h ago | free | 402 | 267 ms | v2 | yes | $0.007476 | 0xfB56…2f39 | — |
| 31h ago | free | 402 | 859 ms | v2 | yes | $0.007476 | 0xfB56…2f39 | — |
| 37h ago | free | 402 | 1032 ms | v2 | yes | $0.007476 | 0xfB56…2f39 | — |
| 43h ago | free | 402 | 287 ms | v2 | yes | $0.007476 | 0xfB56…2f39 | — |
| 2d ago | free | 402 | 364 ms | v2 | yes | $0.007476 | 0xfB56…2f39 | — |