api.babyblueviper.com/regime
1.Catalog declaration
| Resource URL | https://api.babyblueviper.com/regime |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x161dbdd73d025e9aedd4918a67c28e5bf9a87fb9 |
| Declared price (base units) | 24750 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-11 01:02 UTC |
| Catalog-reported calls / payers (30d) | 3 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-11 03:40 UTC | GET | pass | 402 | 338 ms | — |
| 2026-10-09 21:40 UTC | GET | fail | 402 | 389 ms | price_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 24759 of 0x8335…2913, 17775 of XRP. |
| 2026-10-08 16:40 UTC | GET | fail | 402 | 245 ms | price_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 24363 of 0x8335…2913, 18018 of XRP. |
| 2026-10-07 16:40 UTC | GET | fail | 402 | 549 ms | price_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25026 of 0x8335…2913, 17466 of XRP. |
| 2026-10-06 16:40 UTC | GET | fail | 402 | 280 ms | price_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25669 of 0x8335…2913, 17138 of XRP. |
| 2026-10-05 22:40 UTC | GET | fail | 402 | 579 ms | price_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25775 of 0x8335…2913, 17059 of XRP. |
| 2026-10-04 13:40 UTC | GET | fail | 402 | 2217 ms | price_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25571 of 0x8335…2913, 17003 of XRP. |
| 2026-10-03 16:40 UTC | GET | fail | 402 | 286 ms | price_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25441 of 0x8335…2913, 17083 of XRP. |
| 2026-10-02 22:40 UTC | GET | fail | 402 | 247 ms | price_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25353 of 0x8335…2913, 17152 of XRP. |
| 2026-10-02 04:40 UTC | GET | fail | 402 | 789 ms | price_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25964 of 0x8335…2913, 17009 of XRP. |
| 2026-09-29 10:30 UTC | GET | fail | 402 | 338 ms | price_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25231 of 0x8335…2913, 16738 of XRP. |
| 2026-09-29 07:38 UTC | GET | fail | 402 | 727 ms | price_mismatchDeclared 22908 of 0x8335…2913; the 402 offered 25211 of 0x8335…2913, 16702 of XRP. |
| 2026-09-28 13:40 UTC | GET | fail | 402 | 244 ms | price_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 UTC | GET | fail | 402 | 211 ms | price_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 UTC | GET | fail | 402 | 706 ms | price_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 UTC | GET | fail | 402 | 255 ms | price_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 UTC | GET | fail | 402 | 578 ms | price_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 UTC | GET | fail | 402 | 714 ms | price_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 UTC | GET | fail | 402 | 324 ms | price_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 UTC | GET | fail | 402 | 278 ms | price_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 UTC | GET | fail | 402 | 2049 ms | price_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 UTC | GET | fail | 402 | 277 ms | price_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 UTC | GET | fail | 402 | 331 ms | price_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 UTC | GET | fail | 402 | 2201 ms | price_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 UTC | GET | fail | 402 | 226 ms | price_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 UTC | GET | fail | 402 | 265 ms | price_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 UTC | GET | fail | 402 | 444 ms | price_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 UTC | GET | fail | 402 | 223 ms | price_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 UTC | GET | fail | 402 | 359 ms | price_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 UTC | GET | fail | 402 | 319 ms | price_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).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 10-11 05:002026-10-11 05:00 UTC | settle_claimed | 200 | 0x61f947b0…927f | 1524 ms |
| 24750 units (≈ $0.02 USDC) · L2 no_declarationWhose side: not sorted: awaiting on-chain verification | ||||
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.