opportunity-api-production.up.railway.app/api/trending
Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.
1.Catalog declaration
| Resource URL | https://opportunity-api-production.up.railway.app/api/trending |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x5be6c12339eaf5eb18db8012f54955a2250bd3d9 |
| Declared price (base units) | 5000 |
| Catalog status | delisted (since 2026-09-17 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-09-16 01:03 UTC |
| Catalog-reported calls / payers (30d) | 7 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-16 13:40 UTC | GET | fail | 404 | 515 ms | no_402HTTP 404 instead of 402 to an unpaid GET. |
| 2026-09-15 16:40 UTC | GET | fail | 404 | 199 ms | no_402HTTP 404 instead of 402 to an unpaid GET. |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 300 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 154 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 305 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 2267 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 111 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 569 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 210 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 177 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 439 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 332 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 263 ms | — |
| 2026-09-07 23:40 UTC | GET | pass | 402 | 128 ms | — |
| 2026-09-07 14:40 UTC | GET | pass | 402 | 165 ms | — |
| 2026-09-06 23:40 UTC | GET | pass | 402 | 624 ms | — |
| 2026-09-06 05:40 UTC | GET | pass | 402 | 189 ms | — |
| 2026-09-05 17:40 UTC | GET | pass | 402 | 153 ms | — |
| 2026-09-05 05:40 UTC | GET | pass | 402 | 341 ms | — |
| 2026-09-04 17:40 UTC | GET | pass | 402 | 262 ms | — |
| 2026-09-04 05:40 UTC | GET | pass | 402 | 234 ms | — |
| 2026-09-03 23:40 UTC | GET | pass | 402 | 93 ms | — |
| 2026-09-03 14:40 UTC | GET | pass | 402 | 192 ms | — |
| 2026-09-02 23:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-09-02 14:40 UTC | GET | pass | 402 | 118 ms | — |
| 2026-08-30 11:24 UTC | GET | fail | 402 | 91 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 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 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
settled (amount + payee)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset: the on-chain re-read matched payer, payee, amount and asset and did not bind a one-time value (rows before 2026-09-04, and Stellar).
L2 no_declaration- the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 09-11 18:022026-09-11 18:02 UTC | settled (nonce-bound) | 200 | 0xe574e603…1733 | Base | 1855 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered) | |||||
| 09-03 07:012026-09-03 07:01 UTC | settled (amount + payee) | 200 | 0xe87ad101…86ba | Base | 1438 ms |
| 5000 units (≈ $0.005 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/d7e12861-45fb-48bf-a2be-834ed4c2de73)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-17 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-09 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-08 | 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
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.