quotient-api-gateway.onrender.com/api/v1/assets
1.Catalog declaration
| Resource URL | https://quotient-api-gateway.onrender.com/api/v1/assets |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xc3d01fd2f79d4c57ad106ab8ecc12a5de24f97cb |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-28 01:11 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 6 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 22:40 UTC | GET | pass | 402 | 497 ms | — |
| 2026-10-18 04:40 UTC | GET | pass | 402 | 517 ms | — |
| 2026-10-16 21:40 UTC | GET | pass | 402 | 510 ms | — |
| 2026-10-15 12:40 UTC | GET | pass | 402 | 317 ms | — |
| 2026-10-14 03:40 UTC | GET | pass | 402 | 446 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 623 ms | — |
| 2026-10-11 15:40 UTC | GET | pass | 402 | 412 ms | — |
| 2026-10-10 15:40 UTC | GET | pass | 402 | 221 ms | — |
| 2026-10-09 15:40 UTC | GET | pass | 402 | 332 ms | — |
| 2026-10-08 13:40 UTC | GET | pass | 402 | 451 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 537 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 410 ms | — |
| 2026-10-04 22:40 UTC | GET | pass | 402 | 273 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 483 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 295 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 373 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 226 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 2324 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 589 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 605 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 418 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 479 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 283 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 457 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 572 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 371 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 827 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 356 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 402 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
L2 no_declaration- the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
L2 mismatch- the content type was not JSON although the listing marks required keys, or the body read in full did not parse as JSON, was JSON but not an object or array, or lacked a key the listing marks as required.
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 |
|---|---|---|---|---|
| 10-09 17:012026-10-09 17:01 UTC | settled (nonce-bound) | 200 | 0xa5070aec…fca1 | 13607 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-15 23:502026-09-15 23:50 UTC | settled (nonce-bound) | 200 | 0x82a6232b…491a | 9192 ms |
| 5000 units (≈ $0.005 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-05 01:012026-09-05 01:01 UTC | settled (nonce-bound) | 200 | 0x89b844f9…f0bc | 5001 ms |
| 5000 units (≈ $0.005 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/efdcb4fd-2f52-486f-b058-cb308f85b22f)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
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.