api.agentstools.dev/crypto/news
1.Catalog declaration
| Resource URL | https://api.agentstools.dev/crypto/news |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xf22e558a00d91ee12a1f50c52186fecb8ddff493 |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 6 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | GET | pass | 402 | 425 ms | — |
| 2026-10-18 13:40 UTC | GET | pass | 402 | 140 ms | — |
| 2026-10-17 04:40 UTC | GET | pass | 402 | 565 ms | — |
| 2026-10-15 15:40 UTC | GET | pass | 402 | 366 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 222 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 200 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 254 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 1451 ms | — |
| 2026-10-09 21:40 UTC | GET | pass | 402 | 235 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 165 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 246 ms | — |
| 2026-10-06 16:40 UTC | GET | pass | 402 | 172 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 143 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 190 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 1005 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 181 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 285 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 196 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 336 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 656 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 536 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 272 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 260 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 2118 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 350 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 151 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 2885 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 888 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 388 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 558 ms | — |
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 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-17 00:012026-09-17 00:01 UTC | settled (nonce-bound) | 200 | 0x940e53a0…90a9 | 2161 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-10 19:012026-09-10 19:01 UTC | settled (nonce-bound) | 200 | 0xcea36bb2…3908 | 3670 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-04 12:072026-09-04 12:07 UTC | settled (nonce-bound) | 200 | 0x4d13a629…70f7 | 5198 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 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/5ee949a9-33d6-4584-b197-009212914b74)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.