aeml-x402.zeabur.app/pay/tier3
1.Catalog declaration
| Resource URL | https://aeml-x402.zeabur.app/pay/tier3 |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x2d16a243ba9facc6ac85519d5efad2149dc4c6c3 |
| Declared price (base units) | 100000 |
| Catalog status | delisted (since 2026-09-16 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-15 01:03 UTC |
| Catalog-reported calls / payers (30d) | 12 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-15 22:40 UTC | GET | pass | 402 | 965 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 1013 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 1220 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 948 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 958 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 836 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 987 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 813 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 635 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 377 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 371 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 726 ms | — |
| 2026-09-08 17:40 UTC | GET | pass | 402 | 769 ms | — |
| 2026-09-08 05:40 UTC | GET | pass | 402 | 472 ms | — |
| 2026-09-07 17:40 UTC | GET | pass | 402 | 251 ms | — |
| 2026-09-07 05:40 UTC | GET | pass | 402 | 265 ms | — |
| 2026-09-06 17:40 UTC | GET | pass | 402 | 991 ms | — |
| 2026-09-05 23:40 UTC | GET | pass | 402 | 1352 ms | — |
| 2026-09-05 14:40 UTC | GET | pass | 402 | 1174 ms | — |
| 2026-09-04 23:40 UTC | GET | pass | 402 | 994 ms | — |
| 2026-09-04 14:40 UTC | GET | pass | 402 | 1020 ms | — |
| 2026-09-03 23:40 UTC | GET | pass | 402 | 790 ms | — |
| 2026-09-03 14:40 UTC | GET | pass | 402 | 1064 ms | — |
| 2026-09-02 23:40 UTC | GET | pass | 402 | 1060 ms | — |
| 2026-09-02 14:40 UTC | GET | pass | 402 | 1252 ms | — |
| 2026-09-02 05:40 UTC | GET | pass | 402 | 731 ms | — |
| 2026-08-21 10:55 UTC | GET | fail | 402 | 950 ms | metadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
3.L1 — real purchases
1 of 2 paid attempts settled on-chain, and 1 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.
1 of those paid attempts are held as inconclusive rather than counted against this seller (0 settled and answered 4xx, 0 answered 4xx with no settlement receipt, 1 answered 402 or 5xx while our own payer wallet was out of USDC, 2026-09-13 00:00 to 2026-09-15 23:49 UTC). A 4xx says the request was not one the server would accept, and we cannot rule out that the request was ours to get wrong: vet402 buys with no API key of the seller's, and sends a POST body only when the seller declares one. This is the same principle the methodology already applied to path_template URLs, applied to the body and the authentication header as well. The rows are not deleted and not hidden — they are below, with their status and HTTP code, and they are out of the denominator for delivered (corrections).
1 of the paid attempts failed on vet402's side (for example our wallet was out of USDC, or we did not send the input the listing declares). The rows stay in the table; the embeddable badge below leaves them out of its count and names them as “vet402 side”.
Terms in this table
settle_failed- vet402 signed a payment and got no settlement receipt back.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
payer_unfunded- held_reason in the export: a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15).
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.
L2 no_declaration- the listing declares no output schema to check the response against.
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-14 00:002026-09-14 00:00 UTC | settle_failed | 402 | — | 902 ms |
| 100000 units (≈ $0.10 USDC) · L2 not_checkedWhose side: vet402's side | ||||
| 09-03 19:002026-09-03 19:00 UTC | settled (amount + payee) | 200 | 0x03f7228c…25bf | 2549 ms |
| 100000 units (≈ $0.10 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 delivered · vet402 side 1 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/8f054f95-6817-429f-9eda-b47da29aa613)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-16 | 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.