agent402.tools/api/crypto-trending
1.Catalog declaration
| Resource URL | https://agent402.tools/api/crypto-trending |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xabf4fabd7c416fb67202e5f9002389fc75e2a9d0 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-27 01:15 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 10 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | GET | pass | 402 | 275 ms | — |
| 2026-10-18 13:40 UTC | GET | pass | 402 | 318 ms | — |
| 2026-10-16 21:40 UTC | GET | pass | 402 | 270 ms | — |
| 2026-10-15 12:40 UTC | GET | pass | 402 | 176 ms | — |
| 2026-10-14 03:40 UTC | GET | pass | 402 | 134 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 120 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 168 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 161 ms | — |
| 2026-10-09 15:40 UTC | GET | pass | 402 | 127 ms | — |
| 2026-10-08 13:40 UTC | GET | pass | 402 | 99 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 193 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 106 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 1923 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 297 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 112 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 133 ms | — |
| 2026-10-01 22:40 UTC | GET | fail | 502 | 471 ms | no_402HTTP 502 instead of 402 to an unpaid GET. |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 136 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 320 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 114 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 163 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 113 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 336 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 257 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 170 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 298 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 375 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 389 ms | — |
| 2026-09-22 22:40 UTC | GET | fail | 402 | 222 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
| 2026-09-22 04:40 UTC | GET | fail | 402 | 337 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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 match- the response had the 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 |
|---|---|---|---|---|
| 10-08 21:322026-10-08 21:32 UTC | settled (nonce-bound) | 200 | 0x01401ecf…22d7 | 1703 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 10-01 15:322026-10-01 15:32 UTC | settled (nonce-bound) | 200 | 0xc26a51fd…3cc0 | 2034 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-24 00:002026-09-24 00:00 UTC | settled (nonce-bound) | 200 | 0x25c06fee…0c2a | 1344 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 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/153e1fdd-0a4d-4607-a837-c698a3ed526a)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-20 | relisted | {"status":"delisted"} | {"status":"active"} |
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.