Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-11-15 · 2 days ago

crypto.apitoll.cloud/v1/crypto/yields

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://crypto.apitoll.cloud/v1/crypto/yields
Sourcecdp_bazaar
Declared methodGET
Catalog networkeip155:8453
Receiving address0x3da40a9ad36640a2c0f533bac368490095574664
Declared price (base units)1000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-11-17 10:05 UTC
Catalog-reported calls / payers (30d)21 / 11

2.Probe history

2026-09-232026-11-15
Figure 1. Probe timeline, last 30 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-11-15 13:40 UTCGETpass4021492 ms—
2026-11-12 04:40 UTCGETpass402613 ms—
2026-11-09 22:40 UTCGETpass402747 ms—
2026-11-07 16:40 UTCGETpass402714 ms—
2026-11-05 13:40 UTCGETpass402377 ms—
2026-11-02 16:40 UTCGETpass402348 ms—
2026-10-31 13:40 UTCGETpass402607 ms—
2026-10-29 13:40 UTCGETpass402370 ms—
2026-10-27 16:40 UTCGETpass402382 ms—
2026-10-26 00:40 UTCGETpass402484 ms—
2026-10-23 22:40 UTCGETpass402364 ms—
2026-10-22 04:40 UTCGETpass402432 ms—
2026-10-20 22:40 UTCGETpass402544 ms—
2026-10-16 15:40 UTCGETpass402653 ms—
2026-10-15 03:40 UTCGETpass402692 ms—
2026-10-13 21:40 UTCGETpass402365 ms—
2026-10-12 15:40 UTCGETpass4022365 ms—
2026-10-11 15:40 UTCGETpass402416 ms—
2026-10-10 15:40 UTCGETpass402699 ms—
2026-10-09 15:40 UTCGETpass402401 ms—
2026-10-08 13:40 UTCGETpass402505 ms—
2026-09-28 22:40 UTCGETpass402394 ms—
2026-09-28 04:40 UTCGETpass402396 ms—
2026-09-27 16:40 UTCGETpass402836 ms—
2026-09-26 22:40 UTCGETpass402364 ms—
2026-09-26 04:40 UTCGETpass4022377 ms—
2026-09-25 13:40 UTCGETpass402555 ms—
2026-09-24 16:40 UTCGETpass402545 ms—
2026-09-23 22:40 UTCGETpass402522 ms—
2026-09-23 04:40 UTCGETpass402643 ms—

3.L1 — real purchases

3 of 3 paid attempts settled on-chain, and 3 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.

Terms in this table

settled (nonce-bound)
vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
settled (amount + payee)
vet402 re-read the transfer on-chain in that chain's pinned settlement asset: the on-chain re-read matched payer, payee, amount and asset and did not bind a one-time value (rows before 2026-09-04, and Stellar).
L2 match (no required keys)
the declaration vet402 used marks no key as required, so vet402 checked that the response parsed as a JSON object or array, not which keys it carries.
Stage delivered
vet402 re-read the payment on the chain and the paid request returned HTTP 2xx other than 202 Accepted with a body vet402 did not record as empty.
Whose side
the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
3/3
Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.
L1 purchase history, newest first
Attempted atResultHTTPOn-chain txPayment chainLatency
09-17 15:25settled (nonce-bound)2000xec26829c…f1a4Base4744 ms
1000 units (≈ $0.001 USDC) · L2 match (no required keys)Whose side: no failure (delivered)Stage: delivered
09-10 01:02settled (nonce-bound)2000xffa32a33…9bb6Base2143 ms
1000 units (≈ $0.001 USDC) · L2 match (no required keys)Whose side: no failure (delivered)Stage: delivered
09-03 07:00settled (amount + payee)2000x9754cce1…37b5Base3350 ms
1000 units (≈ $0.001 USDC) · L2 match (no required keys)Whose side: no failure (delivered)Stage: delivered

Add this badge to your docs

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.

vet402: 3 of 3 paid attempts settled with an on-chain receipt, and 3 of those also returned a deliverable HTTP 2xx response. settled is the confirmed transfer; delivered is a 2xx other than 202 with a non-empty body. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (crypto.apitoll.cloud · measured 2026-09-17)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/12ec0929-b75b-462e-b02d-1ca919f39bce.svg)](https://vet402.com/observatory/e/12ec0929-b75b-462e-b02d-1ca919f39bce)

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-10-08relisted{"status":"delisted"}{"status":"active"}
2026-09-29delisted{"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

A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.

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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.

20–2,000 characters · 0 so far