web-production-78e17.up.railway.app/v1/summarize
1.Catalog declaration
| Resource URL | https://web-production-78e17.up.railway.app/v1/summarize |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x8fc4006534801c17a3368075a1fb3b3c511edb1f |
| Declared price (base units) | 5000 |
| Catalog status | delisted (since 2026-09-12 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-11 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-11 16:40 UTC | POST | pass | 402 | 170 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 328 ms | — |
| 2026-09-10 14:40 UTC | POST | pass | 402 | 205 ms | — |
| 2026-09-09 23:40 UTC | POST | pass | 402 | 354 ms | — |
| 2026-09-09 05:40 UTC | POST | pass | 402 | 317 ms | — |
| 2026-09-08 17:40 UTC | POST | pass | 402 | 117 ms | — |
| 2026-09-08 05:40 UTC | POST | pass | 402 | 245 ms | — |
| 2026-09-07 17:40 UTC | POST | pass | 402 | 156 ms | — |
| 2026-09-07 05:40 UTC | POST | pass | 402 | 417 ms | — |
| 2026-09-06 17:40 UTC | POST | pass | 402 | 116 ms | — |
| 2026-09-06 05:40 UTC | POST | pass | 402 | 251 ms | — |
| 2026-09-05 17:40 UTC | POST | pass | 402 | 123 ms | — |
| 2026-09-05 05:40 UTC | POST | pass | 402 | 111 ms | — |
| 2026-09-04 17:40 UTC | POST | pass | 402 | 173 ms | — |
| 2026-09-04 05:40 UTC | POST | pass | 402 | 213 ms | — |
| 2026-09-03 17:40 UTC | POST | pass | 402 | 181 ms | — |
| 2026-09-03 05:40 UTC | POST | pass | 402 | 360 ms | — |
| 2026-09-02 17:40 UTC | POST | pass | 402 | 199 ms | — |
| 2026-09-02 11:24 UTC | POST | pass | 402 | 206 ms | — |
| 2026-08-14 08:53 UTC | POST | fail | 402 | 105 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
1 of 1 paid attempts settled on-chain, and 0 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.
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).
1 of those paid attempts are held as inconclusive rather than counted against this seller (1 settled and answered 4xx, 0 answered 4xx with no settlement receipt, 0 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).
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.
settled_4xx- held_reason in the export: the payment settled, then the paid request got a 4xx.
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.
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-07 07:012026-09-07 07:01 UTC | settled (nonce-bound)tx from our index | 422 | 0xeac5de23…1ab0 | 1320 ms |
| 5000 units (≈ $0.005 USDC) · L2 not_checkedWhose side: not sorted: charged, then rejected an input vet402 had not sent | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 0 delivered · 1 inconclusive 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/d9f82a39-3581-469c-943f-0af7fa5988a2)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-12 | 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.