crypto.apitoll.cloud/v1/crypto/tvl
1.Catalog declaration
| Resource URL | https://crypto.apitoll.cloud/v1/crypto/tvl |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x3da40a9ad36640a2c0f533bac368490095574664 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 4 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-17 04:40 UTC | GET | pass | 402 | 638 ms | — |
| 2026-10-15 15:40 UTC | GET | pass | 402 | 358 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 361 ms | — |
| 2026-10-13 03:40 UTC | GET | pass | 402 | 113 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 588 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 318 ms | — |
| 2026-10-09 21:40 UTC | GET | pass | 402 | 232 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 248 ms | — |
| 2026-10-07 16:40 UTC | GET | pass | 402 | 138 ms | — |
| 2026-10-06 16:40 UTC | GET | pass | 402 | 5255 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 695 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 607 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 278 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 186 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 141 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 126 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 214 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 384 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 191 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 244 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 2248 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 338 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 379 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 486 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 445 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 563 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 509 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 459 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 140 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-18 18:022026-09-18 18:02 UTC | settled (nonce-bound) | 200 | 0x7541aafa…dd42 | 1785 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-11 18:022026-09-11 18:02 UTC | settled (nonce-bound) | 200 | 0xc6f6ef36…ed63 | 1938 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-03 12:072026-09-03 12:07 UTC | settled (amount + payee) | 200 | 0xdead88fb…8010 | 1441 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/86e7778c-b7de-400e-b5b2-b35dfbfaddf3)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.