Leaderboard / agentic-reservations.vercel.app / endpoint
GET https://agentic-reservations.vercel.app/api/wait-times
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
- Public data by llm, confidence 50%
- Latest quote
- $0.01 on Base to 0x6671…c0fa
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 3h ago
- Next probe
- 2026-11-17 23:00 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.01 | 0x6671…c0fa | default | yes | 37m ago |
| cdp | exact | Solana | EPjFWd…Dt1v | 10000 | FCFgb8…6zBS | default | yes | 37m 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 |
|---|---|---|---|---|---|
| 19h ago | Public data | 50% | llm | v1 | claude-haiku-5-5: Returns live restaurant wait times and crowd counts, which is closest to a live venue/location dataset rather than a fit for any specific crypto, search, or commerce category; restaurant reservations tags suggest travel/dining, so public_data is the best available match, though confidence is moderate because no clean category targets dining or reservations. |
| 22h ago | Public data | 50% | rules | v1 | rule public_data matched "travel" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 3h ago | free | 402 | 243 ms | v2 | yes | $0.01 | 0x6671…c0fa | — |
| 9h ago | free | 402 | 344 ms | v2 | yes | $0.01 | 0x6671…c0fa | — |
| 16h ago | free | 402 | 206 ms | v2 | yes | $0.01 | 0x6671…c0fa | — |
| 22h ago | free | 402 | 181 ms | v2 | yes | $0.01 | 0x6671…c0fa | — |
| 28h ago | free | 402 | 317 ms | v2 | yes | $0.01 | 0x6671…c0fa | — |
| 34h ago | free | 402 | 162 ms | v2 | yes | $0.01 | 0x6671…c0fa | — |
| 41h ago | free | 402 | 147 ms | v2 | yes | $0.01 | 0x6671…c0fa | — |