api.hyperextend.xyz/v1/outcome_ctx/%231000/latest
1.Catalog declaration
| Resource URL | https://api.hyperextend.xyz/v1/outcome_ctx/%231000/latest |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x548fc289526ab2f0391d562a723cda64bbf1abc4 |
| Declared price (base units) | 3475 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-02 01:04 UTC |
| Catalog-reported calls / payers (30d) | 6 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-02 04:40 UTC | GET | pass | 402 | 302 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 379 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 669 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 359 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 460 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 548 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 486 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 2678 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 602 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 707 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 330 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 241 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 358 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 282 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 243 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 397 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 275 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 477 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 444 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 458 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 2371 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 820 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 451 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 418 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 281 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 305 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 344 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 265 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 763 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 469 ms | — |
3.L1 — real purchases
5 of 5 paid attempts settled on-chain, and 5 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.
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 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 | On-chain tx | Latency |
|---|---|---|---|---|
| 09-16 12:092026-09-16 12:09 UTC | settled (nonce-bound) | 200 | 0xc179f5b5…a083 | 1724 ms |
| 3475 units (≈ $0.0035 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-10 01:002026-09-10 01:00 UTC | settled (nonce-bound) | 200 | 0x128aa1b3…2be6 | 1599 ms |
| 3475 units (≈ $0.0035 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-28 12:182026-08-28 12:18 UTC | settled (amount + payee) | 200 | 0xcbef592b…d042 | 1828 ms |
| 3475 units (≈ $0.0035 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-21 12:212026-08-21 12:21 UTC | settled (amount + payee) | 200 | 0x5d4fb1b6…3ff3 | 1459 ms |
| 3475 units (≈ $0.0035 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-14 10:082026-08-14 10:08 UTC | settled (amount + payee) | 200 | 0xea487558…cb06 | 1242 ms |
| 3475 units (≈ $0.0035 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 5/5 settled · 5 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/db0a61b9-8b7b-4989-b09c-aaa409fedfff)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.