quotient-api-gateway.onrender.com/api/v1/markets/mispriced
1.Catalog declaration
| Resource URL | https://quotient-api-gateway.onrender.com/api/v1/markets/mispriced |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xc3d01fd2f79d4c57ad106ab8ecc12a5de24f97cb |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 24 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-05 04:40 UTC | GET | pass | 402 | 319 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 310 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 335 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 341 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 280 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 361 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 417 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 645 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 372 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 412 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 298 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 557 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 512 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 431 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 526 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 292 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 268 ms | — |
| 2026-09-22 11:24 UTC | GET | pass | 402 | 396 ms | — |
| 2026-09-19 11:24 UTC | GET | pass | 402 | 249 ms | — |
| 2026-09-16 11:24 UTC | GET | pass | 402 | 264 ms | — |
| 2026-09-12 11:24 UTC | GET | pass | 402 | 402 ms | — |
| 2026-09-09 11:24 UTC | GET | pass | 402 | 443 ms | — |
| 2026-09-03 11:24 UTC | GET | pass | 402 | 376 ms | — |
| 2026-08-24 11:11 UTC | GET | fail | 402 | 538 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
0 of 2 paid attempts settled on-chain, and 0 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
Terms in this table
settle_failed- vet402 signed a payment and got no settlement receipt back.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-29 18:012026-09-29 18:01 UTC | settle_failed | — | — | 20579 ms |
| 20000 units (≈ $0.02 USDC) · L2 not_checkedWhose side: not sorted: vet402 stopped waiting | ||||
| 09-22 12:082026-09-22 12:08 UTC | settle_failed | — | — | 20300 ms |
| 20000 units (≈ $0.02 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-09 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-08 | delisted | {"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
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. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.