crypto.apitoll.cloud/v1/crypto/yields
1.Catalog declaration
| Resource URL | https://crypto.apitoll.cloud/v1/crypto/yields |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x3da40a9ad36640a2c0f533bac368490095574664 |
| Declared price (base units) | 1000 |
| Catalog status | delisted (since 2026-09-29 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-28 22:59 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | GET | pass | 402 | 394 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 396 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 836 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 364 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 2377 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 555 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 545 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 522 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 643 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 324 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 370 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 371 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 704 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 303 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 519 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 520 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 293 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 390 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 351 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 391 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 411 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 592 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 591 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 300 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 528 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 458 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 323 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 312 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 320 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 314 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 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 |
|---|---|---|---|---|
| 09-17 15:252026-09-17 15:25 UTC | settled (nonce-bound) | 200 | 0xec26829c…f1a4 | 4744 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-10 01:022026-09-10 01:02 UTC | settled (nonce-bound) | 200 | 0xffa32a33…9bb6 | 2143 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-03 07:002026-09-03 07:00 UTC | settled (amount + payee) | 200 | 0x9754cce1…37b5 | 3350 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/12ec0929-b75b-462e-b02d-1ca919f39bce)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-29 | 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
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.