x402.agentutility.ai/stocks-news
1.Catalog declaration
| Resource URL | https://x402.agentutility.ai/stocks-news |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x6c0752c09e7f6fa6526fcdf40e456a159ebb5621 |
| Declared price (base units) | 5000 |
| Catalog status | delisted (since 2026-09-25 01:02 UTC) |
| First seen / last seen | 2026-08-25 01:58 UTC / 2026-09-24 01:02 UTC |
| Catalog-reported calls / payers (30d) | 112 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-24 13:40 UTC | POST | pass | 402 | 92 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 135 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 4419 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 286 ms | — |
| 2026-09-21 13:40 UTC | POST | pass | 402 | 82 ms | — |
| 2026-09-20 16:40 UTC | POST | fail | — | 10002 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-19 22:40 UTC | POST | pass | 402 | 227 ms | — |
| 2026-09-19 04:40 UTC | POST | pass | 402 | 2454 ms | — |
| 2026-09-18 13:40 UTC | POST | fail | — | 10000 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-17 16:40 UTC | POST | pass | 402 | 136 ms | — |
| 2026-09-16 22:40 UTC | POST | pass | 402 | 1487 ms | — |
| 2026-09-16 13:40 UTC | POST | pass | 402 | 146 ms | — |
| 2026-09-15 13:40 UTC | POST | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 9488 ms | — |
| 2026-09-13 22:40 UTC | POST | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-13 04:40 UTC | POST | pass | 402 | 180 ms | — |
| 2026-09-12 16:40 UTC | POST | pass | 402 | 184 ms | — |
| 2026-09-11 22:40 UTC | POST | fail | — | 10000 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-11 13:40 UTC | POST | fail | — | 10000 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-10 17:40 UTC | POST | pass | 402 | 118 ms | — |
| 2026-09-10 05:40 UTC | POST | pass | 402 | 4098 ms | — |
| 2026-09-09 17:40 UTC | POST | pass | 402 | 198 ms | — |
| 2026-09-08 23:40 UTC | POST | pass | 402 | 5244 ms | — |
| 2026-09-08 14:40 UTC | POST | pass | 402 | 4971 ms | — |
| 2026-09-07 23:40 UTC | POST | pass | 402 | 4627 ms | — |
| 2026-09-07 05:40 UTC | POST | pass | 402 | 3269 ms | — |
| 2026-09-06 17:40 UTC | POST | pass | 402 | 9117 ms | — |
| 2026-09-06 05:40 UTC | POST | pass | 402 | 2172 ms | — |
| 2026-09-05 17:40 UTC | POST | pass | 402 | 3993 ms | — |
| 2026-09-05 05:40 UTC | POST | pass | 402 | 3146 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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.
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 match (no required keys)- the declaration vet402 used marks no key as required, so vet402 checked that the response parsed as a JSON object or array, not which keys it carries.
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 |
|---|---|---|---|---|---|
| 09-04 19:022026-09-04 19:02 UTC | settled (nonce-bound) | 200 | 0x4321f766…7a68 | Base | 11112 ms |
| 5000 units (≈ $0.005 USDC) · L2 match (no required keys)Whose side: no failure (delivered)Stage: 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/ffc9e8a0-482a-4360-9aa1-d69ae60865b4)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-25 | 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.