x402.asterpay.io/v2/x402/offramp/quote
1.Catalog declaration
| Resource URL | https://x402.asterpay.io/v2/x402/offramp/quote |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0xd5f8481d8f25d3966d2010dbf9b47ffbdf745a9e |
| Declared price (base units) | 7500 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-11-16 06:05 UTC |
| Catalog-reported calls / payers (30d) | 28 / 27 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-11-16 04:40 UTC | POST | pass | 402 | 523 ms | — |
| 2026-11-12 16:40 UTC | POST | fail | 404 | 634 ms | no_402HTTP 404 instead of 402 to an unpaid POST. |
| 2026-11-10 13:40 UTC | POST | fail | 404 | 312 ms | no_402HTTP 404 instead of 402 to an unpaid POST. |
| 2026-11-08 04:40 UTC | POST | pass | 402 | 295 ms | — |
| 2026-11-06 04:40 UTC | POST | pass | 402 | 161 ms | — |
| 2026-11-03 21:40 UTC | POST | pass | 402 | 412 ms | — |
| 2026-10-31 22:40 UTC | POST | pass | 402 | 258 ms | — |
| 2026-10-29 22:40 UTC | POST | pass | 402 | 164 ms | — |
| 2026-10-28 04:40 UTC | POST | pass | 402 | 125 ms | — |
| 2026-10-26 15:40 UTC | POST | pass | 402 | 314 ms | — |
| 2026-10-24 13:40 UTC | POST | pass | 402 | 586 ms | — |
| 2026-10-22 16:40 UTC | POST | pass | 402 | 375 ms | — |
| 2026-10-21 04:40 UTC | POST | pass | 402 | 886 ms | — |
| 2026-10-19 16:40 UTC | POST | pass | 402 | 483 ms | — |
| 2026-10-18 04:40 UTC | POST | pass | 402 | 516 ms | — |
| 2026-10-16 21:40 UTC | POST | pass | 402 | 853 ms | — |
| 2026-10-15 12:40 UTC | POST | pass | 402 | 464 ms | — |
| 2026-10-14 03:40 UTC | POST | pass | 402 | 607 ms | — |
| 2026-10-06 10:30 UTC | POST | pass | 402 | 291 ms | — |
| 2026-08-20 10:50 UTC | POST | fail | 402 | 191 ms | accepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's. |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
Terms in this table
settled (nonce-bound)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
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 in the 402 (extensions.bazaar.info.output.example) counts as a declaration. When the catalog also declares an output, the example's top-level keys are required. When it does not, vet402 checks that the response is a JSON object or array, and the record page reads match (no required keys).
Stage delivered- vet402 re-read the payment on the chain and the paid request returned HTTP 2xx other than 202 Accepted with a body vet402 did not record as empty.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 10-27 18:022026-10-27 18:02 UTC | settled (nonce-bound)tx from our index | 200 | 0x04851a4f…bf2a | Base | 1873 ms |
| 7500 units (≈ $0.0075 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 10-21 12:022026-10-21 12:02 UTC | settled (nonce-bound)tx from our index | 200 | 0xf8585fcd…af54 | Base | 1831 ms |
| 7500 units (≈ $0.0075 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
| 10-15 05:012026-10-15 05:01 UTC | settled (nonce-bound)tx from our index | 200 | 0x9810a666…5358 | Base | 1450 ms |
| 7500 units (≈ $0.0075 USDC) · L2 no_declarationWhose side: no failure (delivered)Stage: delivered | |||||
Add this badge to your docs
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/16cf51c1-b5d2-4da0-b174-f8876a6572ac)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-06 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-30 | 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
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.