mcpfax-intel.bowling-anthony.workers.dev/movers
1.Catalog declaration
| Resource URL | https://mcpfax-intel.bowling-anthony.workers.dev/movers |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x1831f336585a6c67b6a954d28f3e07f44c4eebbd |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 2 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | GET | pass | 402 | 241 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 403 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 287 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 95 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 213 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 60 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 160 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 312 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 372 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 122 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 2184 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 390 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 275 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 61 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 156 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 180 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 82 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 307 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 141 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 27 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 75 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 12 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 25 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 1958 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 30 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 87 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 198 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 306 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 508 ms | — |
| 2026-09-08 23:40 UTC | GET | fail | 402 | 2094 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
3.L1 — real purchases
0 of 2 paid attempts settled on-chain, and 0 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.
2 of those paid attempts are held as inconclusive rather than counted against this seller (0 settled and answered 4xx, 2 answered 4xx with no settlement receipt, 0 answered 402 or 5xx while our own payer wallet was out of USDC, 2026-09-13 00:00 to 2026-09-15 23:49 UTC). A 4xx says the request was not one the server would accept, and we cannot rule out that the request was ours to get wrong: vet402 buys with no API key of the seller's, and sends a POST body only when the seller declares one. This is the same principle the methodology already applied to path_template URLs, applied to the body and the authentication header as well. The rows are not deleted and not hidden — they are below, with their status and HTTP code, and they are out of the denominator for delivered (corrections).
Terms in this table
settle_failed- vet402 signed a payment and got no settlement receipt back.
unsettled_4xx- held_reason in the export: the paid request got a 4xx with no settlement receipt and no transaction.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
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-15 23:512026-09-15 23:51 UTC | settle_failed | 404 | — | 504 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checkedWhose side: not sorted: no charge | ||||
| 09-09 19:002026-09-09 19:00 UTC | settle_failed | 404 | — | 739 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checkedWhose side: not sorted: no charge | ||||
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-09T19:00:49Z (UTC). The form starts with that time; add what you saw instead.