x402engine.app/api/crypto/price
1.Catalog declaration
| Resource URL | https://x402engine.app/api/crypto/price |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x7dd5be069f2d2ead75ec7c3423b116ff043c2629 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 12 / 9 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | GET | pass | 402 | 101 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 365 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 131 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 110 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 216 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 125 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 109 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 291 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 139 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 486 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 276 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 270 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 226 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 176 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 152 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 347 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 264 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 583 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 117 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 107 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 201 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 214 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 193 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 2144 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 251 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 126 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 126 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 524 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 225 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 228 ms | — |
3.L1 — real purchases
0 of 3 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.
3 of those paid attempts are held as inconclusive rather than counted against this seller (0 settled and answered 4xx, 2 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).
3 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.
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.
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 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-20 12:092026-09-20 12:09 UTC | settle_failed | 400 | — | 530 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: vet402's side | ||||
| 09-14 00:002026-09-14 00:00 UTC | settle_failed | 402 | — | 634 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: vet402's side | ||||
| 09-07 19:002026-09-07 19:00 UTC | settle_failed | 400 | — | 630 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: vet402's side | ||||
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-09 | settle_drop | {"calls30d":192} | {"calls30d":6} |
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.