Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-11-05 · 6 days ago

tanod.dev/v1/chain/quote

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://tanod.dev/v1/chain/quote
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0x593857a4a4f619543ea12394137c3004ce841720
Declared price (base units)3000
Catalog statusactive
First seen / last seen2026-10-07 13:03 UTC / 2026-11-11 16:06 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-10-082026-11-05
Figure 1. Probe timeline, last 19 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-11-05 16:40 UTCPOSTpass402530 ms—
2026-11-02 16:40 UTCPOSTpass402558 ms—
2026-10-31 16:40 UTCPOSTpass402370 ms—
2026-10-29 16:40 UTCPOSTpass402306 ms—
2026-10-27 16:40 UTCPOSTpass402499 ms—
2026-10-26 00:40 UTCPOSTpass402329 ms—
2026-10-23 22:40 UTCPOSTpass4029201 ms—
2026-10-22 13:40 UTCPOSTpass402516 ms—
2026-10-20 22:40 UTCPOSTpass402952 ms—
2026-10-19 13:40 UTCPOSTpass402329 ms—
2026-10-17 22:40 UTCPOSTpass402410 ms—
2026-10-16 12:40 UTCPOSTpass402356 ms—
2026-10-14 21:40 UTCPOSTpass4022773 ms—
2026-10-13 15:40 UTCPOSTpass402535 ms—
2026-10-12 12:40 UTCPOSTpass402568 ms—
2026-10-11 12:40 UTCPOSTpass402880 ms—
2026-10-10 12:40 UTCPOSTpass402308 ms—
2026-10-09 12:40 UTCPOSTpass4021378 ms—
2026-10-08 04:40 UTCPOSTpass402423 ms—

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-10-11relisted{"status":"delisted"}{"status":"active"}
2026-10-10delisted{"status":"active"}{"status":"delisted"}

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. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. 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.

20–2,000 characters · 0 so far