ai-data-marketplace-1042299154756.us-central1.run.app/api/v1/ai_model_pricing
1.Catalog declaration
| Resource URL | https://ai-data-marketplace-1042299154756.us-central1.run.app/api/v1/ai_model_pricing |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x8647f7d7a1368a467ad1ff757fbc2e7167973558 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-15 01:36 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 4 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 13:40 UTC | GET | pass | 402 | 2017 ms | — |
| 2026-10-17 16:40 UTC | GET | pass | 402 | 43 ms | — |
| 2026-10-16 12:40 UTC | GET | pass | 402 | 82 ms | — |
| 2026-10-14 21:40 UTC | GET | pass | 402 | 1874 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 52 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 145 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 1984 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 1999 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 287 ms | — |
| 2026-10-08 04:40 UTC | GET | pass | 402 | 87 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 208 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 598 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 262 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 245 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 485 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 147 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 292 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 220 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 68 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 119 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 318 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 86 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 108 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 390 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 597 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 137 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 116 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 224 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 99 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 2032 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 (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 match- the response had the fields the listing's output schema declares.
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 07:002026-09-04 07:00 UTC | settled (amount + payee) | 200 | 0xe6ccec92…a1b4 | 1339 ms |
| 10000 units (≈ $0.01 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/73c92279-ff0a-4a25-abfc-8ccd532712b3)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-28 | 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.