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

bykaranteli.com/api/x402/funding-history

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://bykaranteli.com/api/x402/funding-history
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xb4c6c903dee310e4060d8e6eb68582426be1baa9
Declared price (base units)100000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC
Catalog-reported calls / payers (30d)3 / 2

2.Probe history

2026-09-142026-10-04
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-04 22:40 UTCGETpass402327 ms—
2026-10-04 04:40 UTCGETpass402136 ms—
2026-10-03 04:40 UTCGETpass402287 ms—
2026-10-02 13:40 UTCGETfail402120 msprice_mismatchDeclared 5000 of 0x8335…2913; the 402 offered 100000 of 0x8335…2913, 100000 of EPjFWd…Dt1v.
2026-10-01 16:40 UTCGETfail402159 msprice_mismatchDeclared 5000 of 0x8335…2913; the 402 offered 100000 of 0x8335…2913, 100000 of EPjFWd…Dt1v.
2026-09-30 22:40 UTCGETfail402110 msprice_mismatchDeclared 5000 of 0x8335…2913; the 402 offered 100000 of 0x8335…2913, 100000 of EPjFWd…Dt1v.
2026-09-30 04:40 UTCGETfail402477 msprice_mismatchDeclared 5000 of 0x8335…2913; the 402 offered 100000 of 0x8335…2913, 100000 of EPjFWd…Dt1v.
2026-09-29 10:30 UTCGETfail402158 msprice_mismatchDeclared 5000 of 0x8335…2913; the 402 offered 100000 of 0x8335…2913, 100000 of EPjFWd…Dt1v.
2026-09-29 07:38 UTCGETfail402256 msprice_mismatchDeclared 5000 of 0x8335…2913; the 402 offered 100000 of 0x8335…2913, 100000 of EPjFWd…Dt1v.
2026-09-28 22:40 UTCGETfail4022344 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 UTCGETfail402442 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 UTCGETfail402492 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-26 16:40 UTCGETfail402389 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 UTCGETfail402380 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 UTCGETfail402752 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 UTCGETpass402298 ms—
2026-09-23 22:40 UTCGETpass402441 ms—
2026-09-23 04:40 UTCGETpass402700 ms—
2026-09-22 13:40 UTCGETpass402415 ms—
2026-09-21 16:40 UTCGETpass402307 ms—
2026-09-20 22:40 UTCGETpass402226 ms—
2026-09-20 04:40 UTCGETpass402504 ms—
2026-09-19 13:40 UTCGETpass402163 ms—
2026-09-18 16:40 UTCGETpass402160 ms—
2026-09-18 04:40 UTCGETpass402311 ms—
2026-09-17 13:40 UTCGETpass402214 ms—
2026-09-16 16:40 UTCGETpass402360 ms—
2026-09-15 22:40 UTCGETpass402497 ms—
2026-09-15 04:40 UTCGETpass402412 ms—
2026-09-14 13:40 UTCGETpass402222 ms—

3.L1 — real purchases

1 of 1 paid attempts settled on-chain, and 1 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 mismatch
the response lacked 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).
1/1
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
09-10 19:00settled (nonce-bound)2000xd212490c…b45d3776 ms
5000 units (≈ $0.005 USDC) · L2 mismatchWhose side: no failure (delivered)

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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: 1 of 1 paid attempts settled with an on-chain receipt, and 1 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. (bykaranteli.com · measured 2026-09-10)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/8582662b-4897-47e9-b8aa-9733f2791bde.svg)](https://vet402.com/observatory/e/8582662b-4897-47e9-b8aa-9733f2791bde)

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-09-02relisted{"status":"delisted"}{"status":"active"}
2026-08-18delisted{"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.

20–2,000 characters · 0 so far