api.tickersfeed.net/crypto/sentiment
1.Catalog declaration
| Resource URL | https://api.tickersfeed.net/crypto/sentiment |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xe82ebef57fa5af958b8ecb6843d4327d314f59e3 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 48 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 22:40 UTC | GET | pass | 402 | 308 ms | — |
| 2026-10-18 13:40 UTC | GET | pass | 402 | 944 ms | — |
| 2026-10-16 21:40 UTC | GET | pass | 402 | 241 ms | — |
| 2026-10-15 12:40 UTC | GET | pass | 402 | 474 ms | — |
| 2026-10-14 03:40 UTC | GET | pass | 402 | 126 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 123 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 178 ms | — |
| 2026-10-10 15:40 UTC | GET | pass | 402 | 230 ms | — |
| 2026-10-09 15:40 UTC | GET | pass | 402 | 132 ms | — |
| 2026-10-08 13:40 UTC | GET | pass | 402 | 105 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 235 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 100 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 129 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 794 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 142 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 170 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 457 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 486 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 317 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 260 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 86 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 190 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 119 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 339 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 80 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 109 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 133 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 219 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 247 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 85 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.
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 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-20 18:002026-09-20 18:00 UTC | settled (nonce-bound) | 200 | 0xb788f6ed…f8a1 | 1850 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-12 18:002026-09-12 18:00 UTC | settled (nonce-bound) | 200 | 0xdd2b3ce6…17a0 | 1537 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-04 09:232026-09-04 09:23 UTC | settled (amount + payee) | 200 | 0x5c3bb149…f5db | 1351 ms |
| 1000 units (≈ $0.001 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/7c1220e9-94cf-4232-ac41-6bc91f318ba5)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.