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

api.oblique.markets/api/v1/paid/bazaar-price-stats

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.oblique.markets/api/v1/paid/bazaar-price-stats
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x970007590acc5c938cd51345b17af51b1b40d3ab
Declared price (base units)2000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC
Catalog-reported calls / payers (30d)12 / 9

2.Probe history

2026-09-092026-09-28
Figure 1. Probe timeline, last 30 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 UTCGETpass40254 ms—
2026-09-28 04:40 UTCGETpass40280 ms—
2026-09-27 13:40 UTCGETpass402122 ms—
2026-09-26 16:40 UTCGETpass402210 ms—
2026-09-25 22:40 UTCGETpass402264 ms—
2026-09-25 04:40 UTCGETpass402317 ms—
2026-09-24 13:40 UTCGETpass402318 ms—
2026-09-23 16:40 UTCGETpass4022265 ms—
2026-09-22 22:40 UTCGETpass402138 ms—
2026-09-22 13:40 UTCGETpass402256 ms—
2026-09-21 16:40 UTCGETpass402209 ms—
2026-09-20 22:40 UTCGETpass40292 ms—
2026-09-20 04:40 UTCGETpass40230 ms—
2026-09-19 13:40 UTCGETpass40242 ms—
2026-09-18 16:40 UTCGETpass40280 ms—
2026-09-17 22:40 UTCGETpass402384 ms—
2026-09-17 13:40 UTCGETpass4021941 ms—
2026-09-16 16:40 UTCGETpass40281 ms—
2026-09-15 22:40 UTCGETpass402154 ms—
2026-09-15 04:40 UTCGETpass40265 ms—
2026-09-14 13:40 UTCGETpass40240 ms—
2026-09-13 22:40 UTCGETpass40236 ms—
2026-09-13 04:40 UTCGETpass402406 ms—
2026-09-12 16:40 UTCGETpass40226 ms—
2026-09-12 04:40 UTCGETpass402224 ms—
2026-09-11 13:40 UTCGETpass40272 ms—
2026-09-10 23:40 UTCGETpass402125 ms—
2026-09-10 14:40 UTCGETpass402114 ms—
2026-09-09 17:40 UTCGETpass40276 ms—
2026-09-09 05:40 UTCGETpass40227 ms—

3.L1 — real purchases

4 of 5 paid attempts settled with a receipt, and 4 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.

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

settle_failed
vet402 signed a payment and got no settlement receipt back.
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).
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.
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).
4/5
Figure 2. Settle-through: one cell per paid attempt. Filled = settled with an on-chain receipt, crossed = signed, and not settled on-chain.
L1 purchase history, newest first
Attempted atResultHTTPReceipt (tx)Latency
09-15 12:08settle_failed500—425 ms
2000 units (≈ $0.002 USDC) · L2 not_checkedWhose side: vet402's side
09-09 07:02settled (nonce-bound)2000xa88b6ed9…fc04967 ms
2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered)
08-28 12:19settled (amount + payee)2000xe3f66296…06bb862 ms
2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered)
08-21 12:21settled (amount + payee)2000x389d2567…72eb1115 ms
2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered)
08-14 10:11settled (amount + payee)2000x6fe4f433…7b2e885 ms
2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered)

Embed this record

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

vet402: 4 of 4 paid attempts settled with an on-chain receipt, and 4 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. 1 further paid attempt failed on vet402's side (for example its wallet was out of USDC, or it did not send the input the listing declares) and is left out of these counts. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (api.oblique.markets · measured 2026-09-15)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/8a362c71-97bf-442b-b371-dce2c1bd7a37.svg)](https://vet402.com/observatory/e/8a362c71-97bf-442b-b371-dce2c1bd7a37)

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

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-08-21T12:21:40Z (UTC). The form starts with that time; add what you saw instead.

20–2,000 characters · 59 so far