api.strale.io/x402/v2/diff-json
1.Catalog declaration
| Resource URL | https://api.strale.io/x402/v2/diff-json |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x66d7c2f952362bfb24fd7f02a9bec9c754ea83bc |
| Declared price (base units) | 32400 |
| Catalog status | active |
| First seen / last seen | 2026-09-07 01:03 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | GET | pass | 402 | 139 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 250 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 233 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 125 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 273 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 351 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 147 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 419 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 151 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 220 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 150 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 108 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 52 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 160 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 64 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 140 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 207 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 95 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 124 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 121 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 236 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 190 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 140 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 232 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 139 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 143 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 92 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 286 ms | — |
3.L1 — real purchases
0 of 1 paid attempts settled with a receipt, and 0 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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, 1 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
settle_failed- vet402 signed a payment and got no settlement receipt back.
unsettled_4xx- held_reason in the export: the paid request got a 4xx with no settlement receipt and no transaction.
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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-09 07:012026-09-09 07:01 UTC | settle_failed | 405 | — | 274 ms |
| 32400 units (≈ $0.03 USDC) · L2 not_checkedWhose side: not sorted: no charge | ||||
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
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.
About the purchase at 2026-09-09T07:01:29Z (UTC). The form starts with that time; add what you saw instead.