apiacre.com/v1/crypto/base-network-status
1.Catalog declaration
| Resource URL | https://apiacre.com/v1/crypto/base-network-status |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xa0bfa4f07281c9b248dc3aed2217836bca24869b |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 15 / 13 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | POST | pass | 402 | 346 ms | — |
| 2026-09-27 22:40 UTC | POST | pass | 402 | 287 ms | — |
| 2026-09-27 04:40 UTC | POST | pass | 402 | 2241 ms | — |
| 2026-09-26 13:40 UTC | POST | pass | 402 | 637 ms | — |
| 2026-09-25 16:40 UTC | POST | pass | 402 | 200 ms | — |
| 2026-09-24 22:40 UTC | POST | pass | 402 | 459 ms | — |
| 2026-09-24 04:40 UTC | POST | pass | 402 | 209 ms | — |
| 2026-09-23 13:40 UTC | POST | pass | 402 | 182 ms | — |
| 2026-09-22 16:40 UTC | POST | pass | 402 | 258 ms | — |
| 2026-09-21 22:40 UTC | POST | pass | 402 | 235 ms | — |
| 2026-09-21 13:40 UTC | POST | pass | 402 | 442 ms | — |
| 2026-09-20 16:40 UTC | POST | pass | 402 | 216 ms | — |
| 2026-09-19 22:40 UTC | POST | pass | 402 | 171 ms | — |
| 2026-09-19 04:40 UTC | POST | pass | 402 | 135 ms | — |
| 2026-09-18 13:40 UTC | POST | pass | 402 | 220 ms | — |
| 2026-09-17 16:40 UTC | POST | pass | 402 | 367 ms | — |
| 2026-09-17 04:40 UTC | POST | pass | 402 | 331 ms | — |
| 2026-09-16 13:40 UTC | POST | pass | 402 | 175 ms | — |
| 2026-09-15 16:40 UTC | POST | pass | 402 | 362 ms | — |
| 2026-09-14 22:40 UTC | POST | pass | 402 | 208 ms | — |
| 2026-09-14 04:40 UTC | POST | pass | 402 | 129 ms | — |
| 2026-09-13 16:40 UTC | POST | pass | 402 | 307 ms | — |
| 2026-09-13 04:40 UTC | POST | pass | 402 | 667 ms | — |
| 2026-09-12 13:40 UTC | POST | pass | 402 | 146 ms | — |
| 2026-09-11 22:40 UTC | POST | pass | 402 | 145 ms | — |
| 2026-09-11 04:40 UTC | POST | pass | 402 | 158 ms | — |
| 2026-09-10 17:40 UTC | POST | pass | 402 | 249 ms | — |
| 2026-09-10 05:40 UTC | POST | pass | 402 | 156 ms | — |
| 2026-09-09 17:40 UTC | POST | pass | 402 | 433 ms | — |
| 2026-09-07 11:24 UTC | POST | pass | 402 | 444 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled with a receipt, and 2 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.
Terms in this table
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.
L2 match- the response had the fields the listing's output schema declares.
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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-22 06:012026-09-22 06:01 UTC | settled (nonce-bound) | 200 | 0x424cf8e2…0871 | 1654 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-09 19:002026-09-09 19:00 UTC | settled (nonce-bound) | 200 | 0x5f9b3f40…797e | 1957 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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.
[](https://vet402.com/observatory/e/6dff9030-1b2f-43cc-a929-35728566e6e3)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-09-15T23:49:40Z (UTC). The form starts with that time; add what you saw instead.