proxy.0000402.xyz/fetch
1.Catalog declaration
| Resource URL | https://proxy.0000402.xyz/fetch |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xee72b902af7466023595512e3359bb5bf312977c |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 49 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 04:40 UTC | POST | pass | 402 | 1780 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 999 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 899 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 1063 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 1641 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 1179 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 2267 ms | — |
| 2026-09-23 22:40 UTC | POST | pass | 402 | 1047 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 2463 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 2232 ms | — |
| 2026-09-21 16:40 UTC | POST | pass | 402 | 1510 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 2679 ms | — |
| 2026-09-20 04:40 UTC | POST | pass | 402 | 881 ms | — |
| 2026-09-19 16:40 UTC | POST | pass | 402 | 1149 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 1053 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 943 ms | — |
| 2026-09-17 13:40 UTC | POST | pass | 402 | 886 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 903 ms | — |
| 2026-09-15 22:40 UTC | POST | pass | 402 | 998 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 976 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 1527 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 2894 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 1535 ms | — |
| 2026-09-11 11:24 UTC | POST | pass | 402 | 887 ms | — |
| 2026-09-07 11:24 UTC | POST | pass | 402 | 1140 ms | — |
| 2026-09-02 11:25 UTC | POST | pass | 402 | 889 ms | — |
| 2026-08-19 10:56 UTC | POST | fail | 402 | 1004 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
2 of 3 paid attempts settled on-chain, and 2 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.
1 of those paid attempts are held as inconclusive rather than counted against this seller (0 settled and answered 4xx, 0 answered 4xx with no settlement receipt, 1 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.
payer_unfunded- held_reason in the export: a 402 or 5xx while vet402's Base wallet was out of USDC (2026-09-13 to 2026-09-15).
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 | On-chain tx | Latency |
|---|---|---|---|---|
| 09-27 00:002026-09-27 00:00 UTC | settled (nonce-bound) | 200 | 0x60ef5d71…ab82 | 3913 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-20 18:012026-09-20 18:01 UTC | settled (nonce-bound) | 200 | 0x44a20991…8002 | 4259 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-13 12:072026-09-13 12:07 UTC | settle_failed | 500 | — | 1633 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 2/2 settled · 2 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/27e3e4de-ab89-4549-a01c-4f8ca4c5de4b)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-13T12:07:44Z (UTC). The form starts with that time; add what you saw instead.