api.aitrailblazer.net/v1/alpha-opportunities
1.Catalog declaration
| Resource URL | https://api.aitrailblazer.net/v1/alpha-opportunities |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x6d91adf2c545047cbbc5b37a5f457cce081b48d3 |
| Declared price (base units) | 50000 |
| Catalog status | delisted (since 2026-09-20 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-19 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-19 13:40 UTC | GET | pass | 402 | 122 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 427 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 2210 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 75 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 164 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 2148 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 293 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 126 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 133 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 140 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 117 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 99 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 186 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 349 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 84 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 47 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 366 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 42 ms | — |
| 2026-09-02 11:25 UTC | GET | pass | 402 | 32 ms | — |
| 2026-08-20 10:50 UTC | GET | fail | 402 | 6 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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.
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 | On-chain tx | Latency |
|---|---|---|---|---|
| 09-15 23:512026-09-15 23:51 UTC | settled (nonce-bound) | 200 | 0x49427c40…5336 | 5835 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-09 12:072026-09-09 12:07 UTC | settled (nonce-bound) | 200 | 0xa39fd5cc…070c | 4400 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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/a96e47ff-ea1f-4a69-8a2e-e9437613ccb9)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-20 | 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.