api.rtkmotion.io/paid/mocap
1.Catalog declaration
| Resource URL | https://api.rtkmotion.io/paid/mocap |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x6c11f8a21f7ca922f483ed21c3b6c2d9b305b10c |
| Declared price (base units) | 250000 |
| Catalog status | delisted (since 2026-09-19 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-18 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-18 13:40 UTC | GET | pass | 402 | 489 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 593 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 303 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 75 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 564 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 363 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 294 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 258 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 603 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 238 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 291 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 372 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 512 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 319 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 326 ms | — |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 311 ms | — |
| 2026-09-08 14:40 UTC | GET | pass | 402 | 619 ms | — |
| 2026-09-07 23:40 UTC | GET | pass | 402 | 379 ms | — |
| 2026-09-07 14:40 UTC | GET | pass | 402 | 445 ms | — |
| 2026-09-06 23:40 UTC | GET | pass | 402 | 365 ms | — |
| 2026-09-06 14:40 UTC | GET | pass | 402 | 339 ms | — |
| 2026-09-05 23:40 UTC | GET | pass | 402 | 332 ms | — |
| 2026-09-02 11:25 UTC | GET | pass | 402 | 297 ms | — |
| 2026-08-19 10:56 UTC | GET | fail | 402 | 260 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 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-05 19:002026-09-05 19:00 UTC | settled (nonce-bound) | 200 | 0x0c4f8940…b44a | 1918 ms |
| 250000 units (≈ $0.25 USDC) · L2 no_declarationWhose 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/8a3c6d91-5635-4a6e-a8cb-912b1ea72b5a)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-19 | 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
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.