crypto.apitoll.cloud/v1/crypto/global
1.Catalog declaration
| Resource URL | https://crypto.apitoll.cloud/v1/crypto/global |
| 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-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 12 / 8 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 04:40 UTC | GET | pass | 402 | 359 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 708 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 371 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 339 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 338 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 537 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 298 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 384 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 311 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 312 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 291 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 321 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 318 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 365 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 342 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 313 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 351 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 471 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 293 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 450 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 298 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 380 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 416 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 358 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 311 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 2051 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 517 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 119 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 261 ms | — |
| 2026-08-14 08:52 UTC | GET | fail | 402 | 102 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
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 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-23 18:012026-09-23 18:01 UTC | settled (nonce-bound) | 200 | 0x07b6be4d…5fb5 | 1907 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-17 12:522026-09-17 12:52 UTC | settled (nonce-bound) | 200 | 0xd56c39d7…2332 | 1903 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-11 06:002026-09-11 06:00 UTC | settled (nonce-bound) | 200 | 0x457677bb…b685 | 11275 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/a4b94c29-0c34-4e45-9f75-e4974dee4dbc)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.