Leaderboard / api.facts402.com / endpoint
POST https://api.facts402.com/phone
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 7 probes in the last 7 days.
- Category
- Email by llm, confidence 35%
- Latest quote
- $0.01 on Base to 0x5498…f149
- 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
- 6h ago
- Next probe
- 2026-11-17 23:14 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.01 | 0x5498…f149 | default | yes | 42m 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 |
|---|---|---|---|---|---|
| 22h ago | 35% | llm | v1 | claude-haiku-5-5: Phone number validation returns validity, E.164 formatting, type and carrier data. None of the categories cover phone validation directly; enrichment (contact enrichment) and email (contact validation) are the closest, but the endpoint is a deterministic offline check of phone format and metadata, so it fits best under data_transform. Confidence is moderate-low given the mismatch. | |
| 25h ago | Enrichment | 60% | rules | v1 | rule enrichment matched "phone number validation" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 6h ago | free | 402 | 160 ms | v2 | yes | $0.01 | 0x5498…f149 | — |
| 12h ago | free | 402 | 492 ms | v2 | yes | $0.01 | 0x5498…f149 | — |
| 18h ago | free | 402 | 498 ms | v2 | yes | $0.01 | 0x5498…f149 | — |
| 25h ago | free | 402 | 454 ms | v2 | yes | $0.01 | 0x5498…f149 | — |
| 31h ago | free | 402 | 151 ms | v2 | yes | $0.01 | 0x5498…f149 | — |
| 37h ago | free | 402 | 154 ms | v2 | yes | $0.01 | 0x5498…f149 | — |
| 44h ago | free | 402 | 151 ms | v2 | yes | $0.01 | 0x5498…f149 | — |