apexrunner.ai/signals/live-fill-rate
Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.
1.Catalog declaration
| Resource URL | https://apexrunner.ai/signals/live-fill-rate |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x8d0663bbb967ebf1c047405a888ddf865f3e8854 |
| Declared price (base units) | 7000 |
| Catalog status | delisted (since 2026-10-06 01:01 UTC) |
| First seen / last seen | 2026-09-09 01:03 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-04 22:40 UTC | GET | fail | 410 | 74 ms | no_402HTTP 410 instead of 402 to an unpaid GET. |
| 2026-10-04 04:40 UTC | GET | fail | 410 | 120 ms | no_402HTTP 410 instead of 402 to an unpaid GET. |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 76 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 196 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 82 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 245 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 430 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 529 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 273 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 71 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 206 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 176 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 279 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 256 ms | — |
| 2026-09-22 11:24 UTC | GET | pass | 402 | 32 ms | — |
| 2026-09-19 11:24 UTC | GET | pass | 402 | 95 ms | — |
| 2026-09-16 11:24 UTC | GET | pass | 402 | 45 ms | — |
| 2026-09-12 11:24 UTC | GET | pass | 402 | 15 ms | — |
| 2026-09-09 11:24 UTC | GET | pass | 402 | 34 ms | — |
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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 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 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
L2 match- the response parsed as JSON and had the keys the listing marks as required. With an example that marks no key as required, a JSON object or array is enough.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 09-24 06:012026-09-24 06:01 UTC | settled (nonce-bound) | 200 | 0x261d79d4…b909 | Base | 1376 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 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/14e85729-bc27-4758-bc4f-cbde96fcb083)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-06 | delisted | {"status":"active"} | {"status":"delisted"} |
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.