api.cueframe.ai/v1/composition/validate
1.Catalog declaration
| Resource URL | https://api.cueframe.ai/v1/composition/validate |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xa82c8b6971a7379badb2fb96032d82af46eccc0a |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 04:40 UTC | POST | pass | 402 | 1181 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 869 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 2872 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 975 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 879 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 1251 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 1046 ms | — |
| 2026-09-23 22:40 UTC | POST | pass | 402 | 795 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 867 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 1166 ms | — |
| 2026-09-21 16:40 UTC | POST | pass | 402 | 928 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 911 ms | — |
| 2026-09-20 04:40 UTC | POST | pass | 402 | 910 ms | — |
| 2026-09-19 13:40 UTC | POST | pass | 402 | 828 ms | — |
| 2026-09-18 16:40 UTC | POST | pass | 402 | 1092 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 1680 ms | — |
| 2026-09-17 13:40 UTC | POST | pass | 402 | 843 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 827 ms | — |
| 2026-09-15 16:40 UTC | POST | pass | 402 | 1083 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 1032 ms | — |
| 2026-09-14 13:40 UTC | POST | pass | 402 | 671 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 661 ms | — |
| 2026-09-13 04:40 UTC | POST | pass | 402 | 736 ms | — |
| 2026-09-12 16:40 UTC | POST | pass | 402 | 699 ms | — |
| 2026-09-11 22:40 UTC | POST | pass | 402 | 2689 ms | — |
| 2026-09-11 13:40 UTC | POST | pass | 402 | 742 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 996 ms | — |
| 2026-09-10 05:40 UTC | POST | pass | 402 | 986 ms | — |
| 2026-09-09 17:40 UTC | POST | pass | 402 | 797 ms | — |
| 2026-09-09 05:40 UTC | POST | pass | 402 | 1005 ms | — |
3.L1 — real purchases
3 of 5 paid attempts settled with a receipt, and 3 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.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
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.
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).
delivered_no_receipt- the paid request answered 2xx without a settlement receipt.
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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-26 00:012026-09-26 00:01 UTC | settled (nonce-bound)tx from our index | 200 | 0x96f01e13…b452 | 3516 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-19 18:012026-09-19 18:01 UTC | settled (nonce-bound)tx from our index | 200 | 0x67444b33…75ff | 3209 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-28 12:202026-08-28 12:20 UTC | settled (amount + payee)tx from our index | 200 | 0x72410624…a912 | 2660 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-21 12:202026-08-21 12:20 UTC | delivered_no_receipt | 200 | — | 3073 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: not sorted: no charge | ||||
| 08-14 10:042026-08-14 10:04 UTC | delivered_no_receipt | 200 | — | 3208 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: not sorted: no charge | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/5 settled · 3 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/9d3d6211-40ea-4c44-9738-6a11ac571dcb)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-08-28T12:20:37Z (UTC). The form starts with that time; add what you saw instead.