x402factory.ai/base/coinprice
1.Catalog declaration
| Resource URL | https://x402factory.ai/base/coinprice |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | base |
| Receiving address | 0x402faccc3faeb72351cc2b68c7966faf5f22b0d4 |
| Declared price (base units) | — |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-30 01:03 UTC |
| Catalog-reported calls / payers (30d) | 8 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 13:40 UTC | POST | pass | 402 | 580 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 533 ms | — |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 454 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 518 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 414 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 473 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 521 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 494 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 490 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 347 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 344 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 858 ms | — |
| 2026-09-21 13:40 UTC | POST | pass | 402 | 340 ms | — |
| 2026-09-20 16:40 UTC | POST | pass | 402 | 381 ms | — |
| 2026-09-19 22:40 UTC | POST | pass | 402 | 294 ms | — |
| 2026-09-19 11:24 UTC | POST | pass | 402 | 295 ms | — |
| 2026-09-17 11:24 UTC | POST | pass | 402 | 426 ms | — |
| 2026-09-13 11:24 UTC | POST | pass | 402 | 686 ms | — |
| 2026-09-09 11:24 UTC | POST | pass | 402 | 356 ms | — |
| 2026-09-05 11:24 UTC | POST | pass | 402 | 338 ms | — |
| 2026-08-14 08:52 UTC | POST | pass | 402 | 252 ms | — |
3.L1 — real purchases
3 of 5 paid attempts settled on-chain, and 3 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.
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).
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.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
delivered_no_receipt- the paid request answered 2xx without a settlement receipt.
L2 no_declaration- the listing declares no output schema to check the response against.
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-26 00:012026-09-26 00:01 UTC | settled (nonce-bound)tx from our index | 200 | 0x8e9bd10e…ce25 | 1648 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-19 18:002026-09-19 18:00 UTC | settled (nonce-bound)tx from our index | 200 | 0x49d7d30a…4a85 | 2351 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-27 12:312026-08-27 12:31 UTC | settled (amount + payee)tx from our index | 200 | 0x4a48551c…6063 | 1851 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-20 12:552026-08-20 12:55 UTC | delivered_no_receipt | 200 | — | 1587 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: not sorted: no charge | ||||
| 08-14 09:542026-08-14 09:54 UTC | delivered_no_receipt | 200 | — | 1494 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: not sorted: no charge | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/5 settled · 3 delivered 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/423aca3b-f18c-4c60-84ce-21e624084f8e)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.