x402.yodeler.xyz/v1/news
Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.
1.Catalog declaration
| Resource URL | https://x402.yodeler.xyz/v1/news |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x0093406a8805adf3b397c28366402aad9163afda |
| Declared price (base units) | 10000 |
| Catalog status | delisted (since 2026-09-14 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-13 01:03 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-13 22:40 UTC | GET | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-13 04:40 UTC | GET | fail | — | 10011 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-12 13:40 UTC | GET | fail | — | 10003 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 677 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 672 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 806 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 638 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 835 ms | — |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 900 ms | — |
| 2026-09-08 14:40 UTC | GET | pass | 402 | 639 ms | — |
| 2026-09-07 17:40 UTC | GET | pass | 402 | 1037 ms | — |
| 2026-09-07 05:40 UTC | GET | pass | 402 | 2325 ms | — |
| 2026-09-06 17:40 UTC | GET | pass | 402 | 848 ms | — |
| 2026-09-06 05:40 UTC | GET | pass | 402 | 714 ms | — |
| 2026-09-05 17:40 UTC | GET | pass | 402 | 801 ms | — |
| 2026-09-05 05:40 UTC | GET | pass | 402 | 670 ms | — |
| 2026-09-04 17:40 UTC | GET | pass | 402 | 628 ms | — |
| 2026-09-04 05:40 UTC | GET | pass | 402 | 617 ms | — |
| 2026-09-03 17:40 UTC | GET | pass | 402 | 1633 ms | — |
| 2026-09-03 05:40 UTC | GET | pass | 402 | 1023 ms | — |
| 2026-09-02 17:40 UTC | GET | pass | 402 | 467 ms | — |
| 2026-09-02 11:25 UTC | GET | pass | 402 | 705 ms | — |
| 2026-08-19 10:56 UTC | GET | fail | 402 | 982 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
1 of 1 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 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 the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.
Terms in this table
settled (amount + payee)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset: the on-chain re-read matched payer, payee, amount and asset and did not bind a one-time value (rows before 2026-09-04, and Stellar).
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 “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 09-04 07:002026-09-04 07:00 UTC | settled (amount + payee) | 200 | 0xa9dbc254…b251 | Base | 2585 ms |
| 10000 units (≈ $0.01 USDC) · L2 mismatchWhose 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 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/facae12c-7801-44e1-92b2-a97e6da15d65)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-14 | 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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. 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.