Leaderboard / dorothy-x402.onrender.com / endpoint
POST https://dorothy-x402.onrender.com/base/tx-preflight
Scores measure reliability and honesty, not output quality.
- 10 probes got a response that was not a 402 payment challenge.
- Listed only 3 days ago; new listings earn trust over 30 days.
- Category
- Other by llm, confidence 15%
- Latest quote
- — on — to —
- 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 11:08 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 3d ago | disappeared | — | — |
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 |
|---|---|---|---|---|---|
| 37h ago | Other | 15% | llm | v1 | claude-haiku-5-5: The listing has no service name, description, tags, or example fields. The path '/base/tx-preflight' hints at a Base chain transaction check, possibly a simulation or pre-flight validation, but the endpoint's actual output cannot be determined from the listing, so the category is a low-confidence guess left as other. |
| 2d ago | Chain read | 60% | rules | v1 | rule chain_read matched "/base/" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 4h ago | free | 400 | 203 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 10h ago | free | 400 | 145 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 16h ago | free | 400 | 185 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 23h ago | free | 400 | 118 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 29h ago | free | 400 | 114 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 35h ago | free | 400 | 109 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 41h ago | free | 400 | 128 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 2d ago | free | 400 | 49 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 2d ago | free | 400 | 145 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 3d ago | free | 400 | 104 ms | — | no | — | — | unexpected_status:400status_not_402 |
| 3d ago | free | 402 | 126 ms | v2 | yes | $0.1 | 0xDF10…9aF8 | — |
| 3d ago | free | 402 | 46 ms | v2 | yes | $0.1 | 0xDF10…9aF8 | — |