Skip to main content
vet402
MenuClose
Independent MeasurementEndpoint record (L0 · L1)Published state: unverifiedLast probed: 2026-11-11 · 3 days ago
vet402Back to the registerMethodology

app.difficat.com/api/v1/discover

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://app.difficat.com/api/v1/discover
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0x91805ccdcb0af529ffa510efc494786f19d4c257
Declared price (base units)50000
Catalog statusactive
First seen / last seen2026-09-26 01:02 UTC / 2026-11-13 16:05 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-262026-11-11
Figure 1. Probe timeline, last 11 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-11 00:32 UTCPOSTunverified4001928 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-23 22:40 UTCPOSTunverified400498 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-22 13:40 UTCPOSTunverified400482 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-20 22:40 UTCPOSTunverified400475 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-19 13:40 UTCPOSTunverified4001035 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-17 22:40 UTCPOSTunverified4001304 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-16 15:40 UTCPOSTunverified400592 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-15 03:40 UTCPOSTunverified400417 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-09-27 16:40 UTCPOSTfail400427 msno_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail.
2026-09-26 22:40 UTCPOSTpass402671 ms—
2026-09-26 10:30 UTCPOSTpass402381 ms—

3.L1 — real purchases

1 of 1 paid attempts settled on-chain, and 0 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.
L2 not_checked
not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
Stage not_delivered
vet402 re-read the payment on the chain. The paid request returned 5xx, or another HTTP status outside 2xx that vet402 does not leave in settled. vet402 counts HTTP 4xx as inconclusive. vet402 leaves 202 Accepted, HTTP 2xx with a body vet402 recorded as empty, and no HTTP status on record in settled. This stage does not say whose side the failure is on. See Whose side.
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).
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 txPayment chainLatency
09-26 12:00settled (nonce-bound)5020x6c236bec…41c9Base1700 ms
50000 units (≈ $0.05 USDC) · L2 not_checkedWhose side: not sorted: vet402 unprovenStage: not_delivered

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 0 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 0 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. (app.difficat.com · measured 2026-09-26)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/6d4afed4-97e1-41c9-bc6e-c20dc5f1d938.svg)](https://vet402.com/observatory/e/6d4afed4-97e1-41c9-bc6e-c20dc5f1d938)

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-15relisted{"status":"delisted"}{"status":"active"}
2026-09-28delisted{"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