Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: withdrawnLast probed: 2026-09-30 · 53 days ago

safetyincidents.org/api/x402/severe-injuries

Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://safetyincidents.org/api/x402/severe-injuries
Sourcecdp_bazaar
Declared methodGET
Catalog networkeip155:8453
Receiving address0x9f6c07e3f772ec49435579ec34e13141a94b9958
Declared price (base units)10000
Catalog statusdelisted (since 2026-10-01 01:03 UTC)
First seen / last seen2026-08-14 08:39 UTC / 2026-09-30 01:03 UTC
Catalog-reported calls / payers (30d)6 / 6

2.Probe history

2026-08-142026-09-30
Figure 1. Probe timeline, last 18 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-30 13:40 UTCGETfail200170 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-29 16:40 UTCGETfail200225 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-28 22:40 UTCGETpass402117 ms—
2026-09-28 04:40 UTCGETpass402170 ms—
2026-09-27 13:40 UTCGETpass40271 ms—
2026-09-26 16:40 UTCGETpass402101 ms—
2026-09-25 22:40 UTCGETpass402168 ms—
2026-09-25 04:40 UTCGETpass402247 ms—
2026-09-24 13:40 UTCGETpass402128 ms—
2026-09-23 16:40 UTCGETpass402130 ms—
2026-09-23 04:40 UTCGETpass402463 ms—
2026-09-21 11:24 UTCGETpass402103 ms—
2026-09-17 16:19 UTCGETpass402221 ms—
2026-09-14 11:24 UTCGETpass4022001 ms—
2026-09-11 11:24 UTCGETpass402106 ms—
2026-09-07 11:24 UTCGETpass402217 ms—
2026-09-02 11:24 UTCGETpass402210 ms—
2026-08-14 08:53 UTCGETfail40252 msaccepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change).

3.L1 — real purchases

1 of 1 paid attempts settled on-chain, and 1 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 vet402's 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 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).
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-23 06:00settled (nonce-bound)2000x29fe9672…bbd4Base1136 ms
10000 units (≈ $0.01 USDC) · L2 not_checked (recorded mismatch)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 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 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. (safetyincidents.org · measured 2026-09-23)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/ee9f6965-e71e-477b-983d-3d92be14f04c.svg)](https://vet402.com/observatory/e/ee9f6965-e71e-477b-983d-3d92be14f04c)

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-01delisted{"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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. 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