paddock.finance/api/paddock/mcp/gaps
1.Catalog declaration
| Resource URL | https://paddock.finance/api/paddock/mcp/gaps |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x153aa87807d8f6deb65bd53b137cee7ad2daccdb |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 9 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 16:40 UTC | GET | pass | 402 | 2237 ms | — |
| 2026-10-17 13:40 UTC | GET | pass | 402 | 527 ms | — |
| 2026-10-15 21:40 UTC | GET | pass | 402 | 346 ms | — |
| 2026-10-14 15:40 UTC | GET | pass | 402 | 206 ms | — |
| 2026-10-13 03:40 UTC | GET | pass | 402 | 145 ms | — |
| 2026-10-12 03:40 UTC | GET | pass | 402 | 219 ms | — |
| 2026-10-11 03:40 UTC | GET | pass | 402 | 173 ms | — |
| 2026-10-10 03:40 UTC | GET | pass | 402 | 149 ms | — |
| 2026-10-08 22:40 UTC | GET | pass | 402 | 202 ms | — |
| 2026-10-07 16:40 UTC | GET | pass | 402 | 278 ms | — |
| 2026-10-06 22:40 UTC | GET | pass | 402 | 352 ms | — |
| 2026-10-05 22:40 UTC | GET | pass | 402 | 313 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 423 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 254 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 454 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 218 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 500 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 486 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 310 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 275 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 237 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 225 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 375 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 714 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 374 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 2188 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 298 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 163 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 481 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 2303 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
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 |
|---|---|---|---|---|
| 09-17 15:262026-09-17 15:26 UTC | settled (nonce-bound) | 200 | 0x9fc22c98…a701 | 1533 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-10 07:022026-09-10 07:02 UTC | settled (nonce-bound) | 200 | 0x39c22524…a264 | 1222 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-30 12:082026-08-30 12:08 UTC | settled (amount + payee) | 200 | 0x284f5960…dd83 | 1044 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose 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/532ef217-7034-456d-be3f-baff356f0558)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.