apiacre.com/v1/data/us-weather-forecast
1.Catalog declaration
| Resource URL | https://apiacre.com/v1/data/us-weather-forecast |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xa0bfa4f07281c9b248dc3aed2217836bca24869b |
| Declared price (base units) | 3000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 4 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | POST | pass | 402 | 403 ms | — |
| 2026-10-18 16:40 UTC | POST | pass | 402 | 189 ms | — |
| 2026-10-17 13:40 UTC | POST | pass | 402 | 280 ms | — |
| 2026-10-15 21:40 UTC | POST | pass | 402 | 304 ms | — |
| 2026-10-14 12:40 UTC | POST | pass | 402 | 2221 ms | — |
| 2026-10-13 03:40 UTC | POST | pass | 402 | 373 ms | — |
| 2026-10-12 03:40 UTC | POST | pass | 402 | 609 ms | — |
| 2026-10-11 03:40 UTC | POST | pass | 402 | 408 ms | — |
| 2026-10-09 21:40 UTC | POST | pass | 402 | 226 ms | — |
| 2026-10-08 16:40 UTC | POST | pass | 402 | 161 ms | — |
| 2026-10-07 16:40 UTC | POST | pass | 402 | 155 ms | — |
| 2026-10-06 16:40 UTC | POST | pass | 402 | 198 ms | — |
| 2026-10-05 22:40 UTC | POST | pass | 402 | 293 ms | — |
| 2026-10-04 16:40 UTC | POST | pass | 402 | 184 ms | — |
| 2026-10-01 10:30 UTC | POST | pass | 402 | 372 ms | — |
| 2026-09-25 10:31 UTC | POST | pass | 402 | 328 ms | — |
| 2026-09-21 11:24 UTC | POST | pass | 402 | 305 ms | — |
| 2026-09-17 16:19 UTC | POST | pass | 402 | 380 ms | — |
| 2026-09-14 11:24 UTC | POST | pass | 402 | 321 ms | — |
| 2026-09-11 11:24 UTC | POST | pass | 402 | 187 ms | — |
| 2026-09-07 11:24 UTC | POST | pass | 402 | 297 ms | — |
| 2026-09-02 11:24 UTC | POST | pass | 402 | 673 ms | — |
| 2026-08-14 08:53 UTC | POST | fail | 402 | 367 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
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 (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 | On-chain tx | Latency |
|---|---|---|---|---|
| 10-11 05:012026-10-11 05:01 UTC | settled (nonce-bound) | 200 | 0x21c00f45…3c90 | 2586 ms |
| 3000 units (≈ $0.003 USDC) · L2 matchWhose 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.
[](https://vet402.com/observatory/e/661767a6-2a55-4602-862f-1e78897a449a)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.