Leaderboard / work-1-rsrpfxxjxldyrqri.prod-runtime.all-hands.dev / endpoint
GET https://work-1-rsrpfxxjxldyrqri.prod-runtime.all-hands.dev/paid/tenders
Scores measure reliability and honesty, not output quality.
- Responded without asking for payment on 6 probes; it may no longer be an x402 endpoint.
- Listed only 1 day 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
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 14m ago
- Next probe
- 2026-11-18 04:04 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 25h 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 |
|---|---|---|---|---|---|
| 2h ago | Other | 15% | llm | v1 | claude-haiku-5-5: The resource path '/paid/tenders' suggests procurement or tender listings, which could be public_data, but there is no service name, description, tags, or example fields, so the listing says too little to determine the category. |
| 25h ago | Public data | 50% | rules | v1 | rule public_data matched "tenders" in metadata |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 14m ago | free | 404 | 123 ms | — | no | — | — | not_foundstatus_not_402 |
| 6h ago | free | 404 | 65 ms | — | no | — | — | not_foundstatus_not_402 |
| 13h ago | free | 404 | 54 ms | — | no | — | — | not_foundstatus_not_402 |
| 20h ago | free | 404 | 55 ms | — | no | — | — | not_foundstatus_not_402 |
| 27h ago | free | 404 | 159 ms | — | no | — | — | not_foundstatus_not_402 |
| 33h ago | free | 404 | 180 ms | — | no | — | — | not_foundstatus_not_402 |
| 39h ago | free | 404 | 50 ms | — | no | — | — | not_foundstatus_not_402 |