Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-28 · 1 day ago

agent-ready.dev/api/x402/scan

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://agent-ready.dev/api/x402/scan
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x5c08951b999cc133ee4161a3a2b299160f66c42e
Declared price (base units)20000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC
Catalog-reported calls / payers (30d)2 / 2

2.Probe history

2026-08-142026-09-28
Figure 1. Probe timeline, last 21 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-28 22:40 UTCPOSTpass402109 ms—
2026-09-28 04:40 UTCPOSTpass402170 ms—
2026-09-27 13:40 UTCPOSTpass4021843 ms—
2026-09-26 16:40 UTCPOSTpass402267 ms—
2026-09-25 22:40 UTCPOSTpass402176 ms—
2026-09-25 04:40 UTCPOSTpass402362 ms—
2026-09-24 13:40 UTCPOSTpass402460 ms—
2026-09-23 16:40 UTCPOSTpass402280 ms—
2026-09-22 22:40 UTCPOSTpass402183 ms—
2026-09-22 04:40 UTCPOSTpass402335 ms—
2026-09-21 13:40 UTCPOSTpass402900 ms—
2026-09-20 16:40 UTCPOSTpass402177 ms—
2026-09-20 04:40 UTCPOSTpass402302 ms—
2026-09-19 13:40 UTCPOSTpass402375 ms—
2026-09-18 16:40 UTCPOSTpass402163 ms—
2026-09-17 22:40 UTCPOSTpass402177 ms—
2026-09-17 11:24 UTCPOSTpass40296 ms—
2026-09-13 11:24 UTCPOSTpass402104 ms—
2026-09-09 11:24 UTCPOSTpass402140 ms—
2026-09-05 11:24 UTCPOSTpass402204 ms—
2026-08-14 08:53 UTCPOSTpass402411 ms—

3.L1 — real purchases

0 of 1 paid attempts settled on-chain, and 0 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.

Terms in this table

settle_failed
vet402 signed a payment and got no settlement receipt back.
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).
0/1
Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.
L1 purchase history, newest first
Attempted atResultHTTPOn-chain txLatency
08-14 10:09settle_failed402—229 ms
20000 units (≈ $0.02 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-03relisted{"status":"delisted"}{"status":"active"}
2026-08-30delisted{"status":"active"}{"status":"delisted"}

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-08-14T10:09:41Z (UTC). The form starts with that time; add what you saw instead.

20–2,000 characters · 59 so far