Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-19 · 1 day ago
vet402Back to the registerMethodology

toolrail.dev/vat/rates

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://toolrail.dev/vat/rates
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xc6e6138daac78cec93d491b4581afa1a61b98a17
Declared price (base units)2000
Catalog statusactive
First seen / last seen2026-09-02 01:03 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)7 / 5

2.Probe history

2026-09-212026-10-19
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-10-19 16:40 UTCGETpass402372 ms—
2026-10-18 04:40 UTCGETpass402462 ms—
2026-10-16 15:40 UTCGETpass402308 ms—
2026-10-15 03:40 UTCGETpass402295 ms—
2026-10-13 21:40 UTCGETpass402286 ms—
2026-10-12 15:40 UTCGETpass402215 ms—
2026-10-11 15:40 UTCGETpass402181 ms—
2026-10-10 15:40 UTCGETpass402318 ms—
2026-10-09 15:40 UTCGETpass402359 ms—
2026-10-08 13:40 UTCGETpass402330 ms—
2026-10-04 22:40 UTCGETfail402278 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913, 2000 of EPjFWd…Dt1v.
2026-10-04 04:40 UTCGETfail402180 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913, 2000 of EPjFWd…Dt1v.
2026-10-03 04:40 UTCGETfail402133 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913, 2000 of EPjFWd…Dt1v.
2026-10-02 13:40 UTCGETfail402290 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913, 2000 of EPjFWd…Dt1v.
2026-10-01 16:40 UTCGETfail402335 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913, 2000 of EPjFWd…Dt1v.
2026-09-30 22:40 UTCGETfail402356 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913, 2000 of EPjFWd…Dt1v.
2026-09-30 04:40 UTCGETfail402370 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913, 2000 of EPjFWd…Dt1v.
2026-09-29 10:30 UTCGETfail4022236 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913, 2000 of EPjFWd…Dt1v.
2026-09-29 07:38 UTCGETfail402188 msprice_mismatchDeclared 7000 of 0x8335…2913; the 402 offered 2000 of 0x8335…2913, 2000 of EPjFWd…Dt1v.
2026-09-28 22:40 UTCGETfail402294 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-28 04:40 UTCGETfail402644 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-27 13:40 UTCGETfail402355 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-26 22:40 UTCGETfail402242 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-26 04:40 UTCGETfail402358 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-25 13:40 UTCGETfail402238 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-24 16:40 UTCGETfail402243 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-23 22:40 UTCGETfail402460 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-23 04:40 UTCGETfail402428 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-22 13:40 UTCGETfail402330 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-21 16:40 UTCGETfail402406 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).

3.L1 — real purchases

2 of 2 paid attempts settled on-chain, and 2 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.
L2 no_declaration
the listing declares no output schema to check the response against.
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).
2/2
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 txLatency
10-12 17:01settled (nonce-bound)2000xf97e228d…477a2445 ms
2000 units (≈ $0.002 USDC) · L2 matchWhose side: no failure (delivered)
09-06 19:01settled (nonce-bound)2000x5f0979d1…a90f1523 ms
7000 units (≈ $0.007 USDC) · L2 no_declarationWhose side: no failure (delivered)

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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: 2 of 2 paid attempts settled with an on-chain receipt, and 2 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (toolrail.dev · measured 2026-10-12)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/05c669b3-b9c0-4a02-bb36-9d755448aea3.svg)](https://vet402.com/observatory/e/05c669b3-b9c0-4a02-bb36-9d755448aea3)

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

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.

20–2,000 characters · 0 so far