apexrunner.ai/signals/btc-price-tick
1.Catalog declaration
| Resource URL | https://apexrunner.ai/signals/btc-price-tick |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x8d0663bbb967ebf1c047405a888ddf865f3e8854 |
| Declared price (base units) | 7000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 5 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | GET | pass | 402 | 310 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 276 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 128 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 149 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 65 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 170 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 2327 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 326 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 219 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 345 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 313 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 429 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 82 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 198 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 342 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 71 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 114 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 505 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 167 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 38 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 36 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 38 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 147 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 90 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 94 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 221 ms | — |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 41 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled with a receipt, and 3 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-17 00:012026-09-17 00:01 UTC | settled (nonce-bound) | 200 | 0x86e2c9be…5d99 | 1279 ms |
| 7000 units (≈ $0.007 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-10 19:012026-09-10 19:01 UTC | settled (nonce-bound) | 200 | 0xe5365b9a…946f | 1295 ms |
| 7000 units (≈ $0.007 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-04 12:072026-09-04 12:07 UTC | settled (nonce-bound) | 200 | 0xb6ff09af…6c33 | 1205 ms |
| 7000 units (≈ $0.007 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/5a8cc66a-185d-4fae-8288-7b01ef55efbb)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.