api.hyperextend.xyz/v1/outcome/100/oi
1.Catalog declaration
| Resource URL | https://api.hyperextend.xyz/v1/outcome/100/oi |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x548fc289526ab2f0391d562a723cda64bbf1abc4 |
| Declared price (base units) | 125725 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-13 01:02 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-13 10:30 UTC | GET | pass | 402 | 516 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 254 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 330 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 325 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 713 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 455 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 553 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 256 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 402 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 333 ms | — |
| 2026-09-08 17:40 UTC | GET | pass | 402 | 431 ms | — |
| 2026-09-08 05:40 UTC | GET | pass | 402 | 378 ms | — |
| 2026-09-07 17:40 UTC | GET | pass | 402 | 465 ms | — |
| 2026-09-07 05:40 UTC | GET | pass | 402 | 399 ms | — |
| 2026-09-06 17:40 UTC | GET | pass | 402 | 319 ms | — |
| 2026-09-06 05:40 UTC | GET | pass | 402 | 340 ms | — |
| 2026-09-05 14:40 UTC | GET | pass | 402 | 499 ms | — |
| 2026-09-04 23:40 UTC | GET | pass | 402 | 2230 ms | — |
| 2026-09-04 14:40 UTC | GET | pass | 402 | 437 ms | — |
| 2026-09-04 05:40 UTC | GET | pass | 402 | 442 ms | — |
| 2026-09-03 17:40 UTC | GET | pass | 402 | 391 ms | — |
| 2026-09-03 05:40 UTC | GET | pass | 402 | 453 ms | — |
| 2026-09-02 17:40 UTC | GET | pass | 402 | 370 ms | — |
| 2026-09-02 05:40 UTC | GET | pass | 402 | 675 ms | — |
| 2026-09-01 23:40 UTC | GET | pass | 402 | 199 ms | — |
| 2026-08-14 08:53 UTC | GET | pass | 402 | 95 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 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 |
|---|---|---|---|---|
| 08-14 10:092026-08-14 10:09 UTC | settled (amount + payee) | 200 | 0x2f338f94…61f4 | 1398 ms |
| 125725 units (≈ $0.13 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/4e112d0f-d150-4f79-807f-b605bb7178dd)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-12 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-14 | 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.