x402.shortforge.dev/x402/probe
1.Catalog declaration
| Resource URL | https://x402.shortforge.dev/x402/probe |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x61c67cf010f70f6ac7b46de2fd578204c923e29e |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-09-16 01:03 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | GET | pass | 402 | 149 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 379 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 787 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 295 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 222 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 768 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 390 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 2188 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 323 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 257 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 204 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 340 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 420 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 351 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 197 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 381 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 862 ms | — |
| 2026-09-16 11:24 UTC | GET | pass | 402 | 286 ms | — |
3.L1 — real purchases
1 of 2 paid attempts settled with a receipt, and 1 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.
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 (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).
1 of the paid attempts failed on vet402's side (for example our wallet was out of USDC, or we did not send the input the listing declares). The rows stay in the table; the embeddable badge below leaves them out of its count and names them as “vet402 side”.
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.
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 no_declaration- the listing declares no output schema to check the response against.
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-28 21:312026-09-28 21:31 UTC | settled (nonce-bound)tx from our index | 200 | 0xead77965…1306 | 1485 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-18 06:022026-09-18 06:02 UTC | settle_failed | 400 | — | 1202 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checkedWhose side: vet402's side | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 delivered · vet402 side 1 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/fdcd2645-8764-442b-a3a3-d73ff1de64fe)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-18T06:02:07Z (UTC). The form starts with that time; add what you saw instead.