Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-29 · today
vet402Back to the registerMethodology

402.com.tr/api/x402/b20-guard

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://402.com.tr/api/x402/b20-guard
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x973a31858f4d2125f48c880542da11a2796f12d6
Declared price (base units)50000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC
Catalog-reported calls / payers (30d)2 / 1

2.Probe history

2026-08-202026-09-29
Figure 1. Probe timeline, last 20 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-09-29 04:40 UTCGETpass402422 ms—
2026-09-28 13:40 UTCGETpass402369 ms—
2026-09-27 16:40 UTCGETpass402423 ms—
2026-09-26 22:40 UTCGETpass402342 ms—
2026-09-26 04:40 UTCGETpass402697 ms—
2026-09-25 13:40 UTCGETpass4021285 ms—
2026-09-24 16:40 UTCGETpass402551 ms—
2026-09-23 22:40 UTCGETpass402589 ms—
2026-09-23 04:40 UTCGETpass402660 ms—
2026-09-22 13:40 UTCGETpass402371 ms—
2026-09-21 16:40 UTCGETpass402458 ms—
2026-09-20 22:40 UTCGETpass402537 ms—
2026-09-20 04:40 UTCGETpass402403 ms—
2026-09-19 16:40 UTCGETpass402920 ms—
2026-09-17 16:19 UTCGETpass402468 ms—
2026-09-15 11:24 UTCGETpass402372 ms—
2026-09-11 11:24 UTCGETpass402459 ms—
2026-09-07 11:24 UTCGETpass402493 ms—
2026-09-02 11:25 UTCGETpass402467 ms—
2026-08-20 10:50 UTCGETfail402541 msaccepts_invalid

3.L1 — real purchases

1 of 1 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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 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).
1/1
Figure 2. Settle-through: one cell per paid attempt. Filled = settled with an on-chain receipt, crossed = paid but no receipt.
L1 purchase history, newest first
Attempted atResultHTTPReceipt (tx)Latency
09-20 00:02settled (nonce-bound)2000x2fce83a2…5f872041 ms
50000 units (≈ $0.05 USDC) · L2 no_declarationWhose 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. (402.com.tr · measured 2026-09-20)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/a6cc52b4-f42c-4ca6-8af4-0e181034f6af.svg)](https://vet402.com/observatory/e/a6cc52b4-f42c-4ca6-8af4-0e181034f6af)

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.

About the purchase at 2026-09-20T00:02:12Z (UTC). The form starts with that time; add what you saw instead.