datastand.dev/api/data/llm-pricing
1.Catalog declaration
| Resource URL | https://datastand.dev/api/data/llm-pricing |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x470a1b647d668d3820add26d70c8371557ff4c6b |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-16 01:07 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | GET | pass | 402 | 110 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 262 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 533 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 540 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 995 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 213 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 175 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 249 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 407 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 309 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 77 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 259 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 1752 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 101 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 78 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 290 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 331 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 316 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 195 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 85 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 65 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 91 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 370 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 443 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 58 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 2052 ms | — |
| 2026-09-10 11:24 UTC | GET | pass | 402 | 40 ms | — |
| 2026-09-06 11:24 UTC | GET | pass | 402 | 52 ms | — |
| 2026-09-01 23:14 UTC | GET | pass | 402 | 12 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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 mismatch- the response lacked 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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-11 01:002026-09-11 01:00 UTC | settled (nonce-bound) | 200 | 0xaafde4b4…3ac6 | 975 ms |
| 50000 units (≈ $0.05 USDC) · L2 mismatchWhose 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/c8039ad7-f259-4093-a285-7ac1ccd4fb30)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-11T01:00:05Z (UTC). The form starts with that time; add what you saw instead.