toll402.dev/v1/t/jsonld_extract
1.Catalog declaration
| Resource URL | https://toll402.dev/v1/t/jsonld_extract |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x318d34fa0bd69eff17fac648d2df8cf7a88b3dbe |
| Declared price (base units) | 3000 |
| Catalog status | active |
| First seen / last seen | 2026-09-16 01:03 UTC / 2026-11-07 06:05 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-11-19 02:30 UTC | POST | pass | 402 | 377 ms | — |
| 2026-11-12 00:30 UTC | POST | pass | 402 | 337 ms | — |
| 2026-11-04 22:40 UTC | POST | pass | 402 | 63 ms | — |
| 2026-11-01 22:40 UTC | POST | pass | 402 | 115 ms | — |
| 2026-10-30 22:40 UTC | POST | pass | 402 | 253 ms | — |
| 2026-10-28 22:40 UTC | POST | pass | 402 | 205 ms | — |
| 2026-10-27 06:40 UTC | POST | pass | 402 | 226 ms | — |
| 2026-10-25 15:40 UTC | POST | pass | 402 | 124 ms | — |
| 2026-10-23 13:40 UTC | POST | pass | 402 | 366 ms | — |
| 2026-10-21 22:40 UTC | POST | pass | 402 | 109 ms | — |
| 2026-10-20 13:40 UTC | POST | pass | 402 | 114 ms | — |
| 2026-10-18 16:40 UTC | POST | pass | 402 | 172 ms | — |
| 2026-10-17 13:40 UTC | POST | pass | 402 | 36 ms | — |
| 2026-10-15 21:40 UTC | POST | pass | 402 | 44 ms | — |
| 2026-10-14 15:40 UTC | POST | pass | 402 | 37 ms | — |
| 2026-10-13 03:40 UTC | POST | pass | 402 | 73 ms | — |
| 2026-10-12 03:40 UTC | POST | pass | 402 | 150 ms | — |
| 2026-10-11 03:40 UTC | POST | pass | 402 | 99 ms | — |
| 2026-10-10 03:40 UTC | POST | pass | 402 | 588 ms | — |
| 2026-10-08 22:40 UTC | POST | pass | 402 | 127 ms | — |
| 2026-10-07 22:40 UTC | POST | pass | 402 | 181 ms | — |
| 2026-10-06 22:40 UTC | POST | pass | 402 | 198 ms | — |
| 2026-10-05 22:40 UTC | POST | pass | 402 | 10 ms | — |
| 2026-10-04 16:40 UTC | POST | pass | 402 | 29 ms | — |
| 2026-10-03 22:40 UTC | POST | pass | 402 | 218 ms | — |
| 2026-10-03 04:40 UTC | POST | pass | 402 | 158 ms | — |
| 2026-10-02 04:40 UTC | POST | pass | 402 | 787 ms | — |
| 2026-10-01 13:40 UTC | POST | pass | 402 | 29 ms | — |
| 2026-09-30 16:40 UTC | POST | pass | 402 | 330 ms | — |
| 2026-09-29 22:40 UTC | POST | pass | 402 | 32 ms | — |
3.L1 — real purchases
0 of 1 paid attempts settled on-chain, and 0 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 vet402's 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
settle_failed- vet402 signed a payment and got no settlement receipt back.
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.
Stage signed- vet402 signed a paid request. vet402 has not settled it on chain yet, or settlement failed, or the seller returned goods without a receipt.
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-16 12:082026-09-16 12:08 UTC | settle_failed | 502 | — | Base | 693 ms |
| 3000 units (≈ $0.003 USDC) · L2 not_checkedWhose side: not sorted: vet402 unprovenStage: signed | |||||
4.Catalog listing events
No listing changes observed.
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.