Leaderboard / api.strale.io / endpoint
GET https://api.strale.io/x402/phone-normalize
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
- Data transform by llm, confidence 60%
- Latest quote
- $0.0324 on Base to 0x66D7…83bC
- 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-17 23:45 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.0324 | 0x66D7…83bC | default | yes | 3h 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 |
|---|---|---|---|---|---|
| 8h ago | Data transform | 60% | llm | v1 | claude-haiku-5-5: Phone number parsing and normalization to E.164 is a deterministic string transform; it is not a utility like geocoding or a validation service per se, so data_transform fits best, though utility is a plausible alternative. |
| 25h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 5h ago | free | 402 | 81 ms | v1 | yes | $0.0324 | 0x66D7…83bC | protocol_v1 |
| 11h ago | free | 402 | 107 ms | v1 | yes | $0.0324 | 0x66D7…83bC | protocol_v1 |
| 17h ago | free | 402 | 114 ms | v1 | yes | $0.0324 | 0x66D7…83bC | protocol_v1 |
| 23h ago | free | 402 | 108 ms | v1 | yes | $0.0324 | 0x66D7…83bC | protocol_v1 |
| 29h ago | free | 402 | 78 ms | v1 | yes | $0.0324 | 0x66D7…83bC | protocol_v1 |
| 36h ago | free | 402 | 82 ms | v1 | yes | $0.0324 | 0x66D7…83bC | protocol_v1 |
| 42h ago | free | 402 | 86 ms | v1 | yes | $0.0324 | 0x66D7…83bC | protocol_v1 |