predict.memoryapi.org/x402/predict/mispricing
1.Catalog declaration
| Resource URL | https://predict.memoryapi.org/x402/predict/mispricing |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x24facafeb49b4e3facf0b3e69604a2f4640c9bf2 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 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-03 04:40 UTC | GET | pass | 402 | 743 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 286 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 241 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 116 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 290 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 267 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 237 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 331 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 407 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 179 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 200 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 98 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 332 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 299 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 241 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 244 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 127 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 1992 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 258 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 660 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 745 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 100 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 135 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 414 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 176 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 143 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 272 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 329 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 210 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 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-04 12:092026-09-04 12:09 UTC | settled (nonce-bound) | 200 | 0xd6c88cb1…45a4 | 8090 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 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/342718a3-b713-42a9-ad9b-777cb2a4af0c)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-30 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-28 | 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.