Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-11 · today

api.babyblueviper.com/regime

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.babyblueviper.com/regime
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x161dbdd73d025e9aedd4918a67c28e5bf9a87fb9
Declared price (base units)24750
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-10-11 01:02 UTC
Catalog-reported calls / payers (30d)3 / 2

2.Probe history

2026-09-162026-10-11
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-10-11 03:40 UTCGETpass402338 ms—
2026-10-09 21:40 UTCGETfail402389 msprice_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 24759 of 0x8335…2913, 17775 of XRP.
2026-10-08 16:40 UTCGETfail402245 msprice_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 24363 of 0x8335…2913, 18018 of XRP.
2026-10-07 16:40 UTCGETfail402549 msprice_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25026 of 0x8335…2913, 17466 of XRP.
2026-10-06 16:40 UTCGETfail402280 msprice_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25669 of 0x8335…2913, 17138 of XRP.
2026-10-05 22:40 UTCGETfail402579 msprice_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25775 of 0x8335…2913, 17059 of XRP.
2026-10-04 13:40 UTCGETfail4022217 msprice_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25571 of 0x8335…2913, 17003 of XRP.
2026-10-03 16:40 UTCGETfail402286 msprice_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25441 of 0x8335…2913, 17083 of XRP.
2026-10-02 22:40 UTCGETfail402247 msprice_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25353 of 0x8335…2913, 17152 of XRP.
2026-10-02 04:40 UTCGETfail402789 msprice_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25964 of 0x8335…2913, 17009 of XRP.
2026-09-29 10:30 UTCGETfail402338 msprice_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25231 of 0x8335…2913, 16738 of XRP.
2026-09-29 07:38 UTCGETfail402727 msprice_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25211 of 0x8335…2913, 16702 of XRP.
2026-09-28 13:40 UTCGETfail402244 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-27 16:40 UTCGETfail402211 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-27 04:40 UTCGETfail402706 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-26 13:40 UTCGETfail402255 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-25 16:40 UTCGETfail402578 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-24 22:40 UTCGETfail402714 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-24 04:40 UTCGETfail402324 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-23 13:40 UTCGETfail402278 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-22 16:40 UTCGETfail4022049 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-21 22:40 UTCGETfail402277 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-21 04:40 UTCGETfail402331 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-20 13:40 UTCGETfail4022201 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-19 16:40 UTCGETfail402226 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-18 22:40 UTCGETfail402265 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-18 13:40 UTCGETfail402444 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-17 16:40 UTCGETfail402223 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-16 22:40 UTCGETfail402359 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-16 13:40 UTCGETfail402319 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).

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_claimed
the seller returned a receipt that vet402 has not re-read on-chain yet.
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).
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
10-11 05:00settle_claimed2000x61f947b0…927f1524 ms
24750 units (≈ $0.02 USDC) · L2 no_declarationWhose side: not sorted: awaiting on-chain verification

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.

20–2,000 characters · 0 so far

api.babyblueviper.com/regime — x402 purchase and probe record | vet402