Leaderboard / rexvalidate.com / endpoint
POST https://rexvalidate.com/api/agent/v1/phone
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 11 probes in the last 7 days.
- Category
- Email by llm, confidence 50%
- Latest quote
- $0.036 on Base to 0x362e…37D7
- 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-19 01:43 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.036 | 0x362e…37D7 | default | yes | 6h 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 |
|---|---|---|---|---|---|
| 46h ago | 50% | llm | v1 | claude-haiku-5-5: Phone number validation for lead quality is a contact-data verification service; closest fit among the categories is email (contact validation), though enrichment is also plausible. Confidence moderate since no 'phone' category exists. | |
| 2d ago | Enrichment | 60% | rules | v1 | rule enrichment matched "phone validation" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 4h ago | free | 402 | 825 ms | v2 | yes | $0.036 | 0x362e…37D7 | — |
| 11h ago | free | 402 | 274 ms | v2 | yes | $0.036 | 0x362e…37D7 | — |
| 17h ago | free | 402 | 376 ms | v2 | yes | $0.036 | 0x362e…37D7 | — |
| 23h ago | free | 402 | 414 ms | v2 | yes | $0.036 | 0x362e…37D7 | — |
| 30h ago | free | 402 | 464 ms | v2 | yes | $0.036 | 0x362e…37D7 | — |
| 36h ago | free | 402 | 345 ms | v2 | yes | $0.036 | 0x362e…37D7 | — |
| 42h ago | free | 402 | 412 ms | v2 | yes | $0.036 | 0x362e…37D7 | — |
| 2d ago | free | 402 | 676 ms | v2 | yes | $0.036 | 0x362e…37D7 | — |
| 2d ago | free | 402 | 388 ms | v2 | yes | $0.036 | 0x362e…37D7 | — |
| 3d ago | free | 402 | 299 ms | v2 | yes | $0.036 | 0x362e…37D7 | — |
| 3d ago | free | 402 | 277 ms | v2 | yes | $0.036 | 0x362e…37D7 | — |