api.tickersfeed.net/calendar/earnings
1.Catalog declaration
| Resource URL | https://api.tickersfeed.net/calendar/earnings |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xe82ebef57fa5af958b8ecb6843d4327d314f59e3 |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 32 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | GET | pass | 402 | 323 ms | — |
| 2026-10-18 13:40 UTC | GET | pass | 402 | 138 ms | — |
| 2026-10-17 04:40 UTC | GET | pass | 402 | 114 ms | — |
| 2026-10-15 15:40 UTC | GET | pass | 402 | 398 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 457 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 159 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 75 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 43 ms | — |
| 2026-10-09 21:40 UTC | GET | pass | 402 | 347 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 4053 ms | — |
| 2026-10-07 16:40 UTC | GET | pass | 402 | 73 ms | — |
| 2026-10-06 16:40 UTC | GET | pass | 402 | 119 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 69 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 111 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 123 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 115 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 153 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 344 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 151 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 64 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 59 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 128 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 173 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 153 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 372 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 123 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 2156 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 162 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 138 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 211 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'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 “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 10-09 23:012026-10-09 23:01 UTC | settled (nonce-bound) | 200 | 0x1d2b6a60…518e | 1402 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 10-02 18:022026-10-02 18:02 UTC | settled (nonce-bound) | 200 | 0x4221004e…871d | 1007 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-18 06:012026-09-18 06:01 UTC | settled (nonce-bound) | 200 | 0xb9d9bac4…7ac5 | 1565 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/89a2f4ba-2000-427c-b4f1-2fbade745e91)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.