route-a-worker.frostskynet-api.workers.dev/judge
1.Catalog declaration
| Resource URL | https://route-a-worker.frostskynet-api.workers.dev/judge |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x3a1121e787586a504ff74fc53e3acee19fade698 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-10-06 01:01 UTC / 2026-10-21 13:01 UTC |
| Catalog-reported calls / payers (30d) | 9 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-21 16:40 UTC | POST | pass | 402 | 51 ms | — |
| 2026-10-07 10:30 UTC | POST | fail | 402 | 900 ms | price_mismatchDeclared 10000 of 0x036C…CF7e; the 402 offered 10000 of 0x8335…2913. |
| 2026-10-06 10:30 UTC | POST | fail | 402 | 116 ms | price_mismatchDeclared 10000 of 0x036C…CF7e; the 402 offered 10000 of 0x8335…2913. |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
No listing changes observed.
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight. If it was right, it stands. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.