Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-20 · today
vet402Back to the registerMethodology

x402render-u5vwpxpyua-uc.a.run.app/pm-markets

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://x402render-u5vwpxpyua-uc.a.run.app/pm-markets
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x71c09a4946d451ae56f22ecad4af4fe1380ae347
Declared price (base units)8000
Catalog statusactive
First seen / last seen2026-08-20 01:30 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)2 / 2

2.Probe history

2026-09-022026-10-20
Figure 1. Probe timeline, last 17 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-10-20 10:30 UTCGETpass40239 ms—
2026-09-09 23:40 UTCGETfail50337 msno_402HTTP 503 instead of 402 to an unpaid GET.
2026-09-09 14:40 UTCGETfail503255 msno_402HTTP 503 instead of 402 to an unpaid GET.
2026-09-08 23:40 UTCGETfail503207 msno_402HTTP 503 instead of 402 to an unpaid GET.
2026-09-08 05:40 UTCGETpass402112 ms—
2026-09-07 17:40 UTCGETpass40245 ms—
2026-09-07 05:40 UTCGETpass402157 ms—
2026-09-06 17:40 UTCGETpass402129 ms—
2026-09-06 05:40 UTCGETpass40287 ms—
2026-09-05 17:40 UTCGETpass402203 ms—
2026-09-05 05:40 UTCGETpass402490 ms—
2026-09-04 17:40 UTCGETpass402207 ms—
2026-09-04 05:40 UTCGETpass402221 ms—
2026-09-03 17:40 UTCGETpass402140 ms—
2026-09-03 05:40 UTCGETpass402114 ms—
2026-09-02 23:40 UTCGETpass402322 ms—
2026-09-02 14:40 UTCGETpass402475 ms—

3.L1 — real purchases

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

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).
L2 no_declaration
the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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).
1/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
09-03 12:09settled (amount + payee)2000x99698a2e…aaab1318 ms
8000 units (≈ $0.008 USDC) · L2 no_declarationWhose side: no failure (delivered)

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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.

vet402: 1 of 1 paid attempts settled with an on-chain receipt, and 1 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (x402render-u5vwpxpyua-uc.a.run.app · measured 2026-09-03)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/3538de6e-375a-4604-8b65-761bd6b60ab0.svg)](https://vet402.com/observatory/e/3538de6e-375a-4604-8b65-761bd6b60ab0)

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-10delisted{"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.

20–2,000 characters · 0 so far