Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-11-20 · 2 days ago

toll402.dev/v1/t/orgnr_se_validate

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://toll402.dev/v1/t/orgnr_se_validate
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0x318d34fa0bd69eff17fac648d2df8cf7a88b3dbe
Declared price (base units)1000
Catalog statusactive
First seen / last seen2026-09-10 01:03 UTC / 2026-11-22 14:05 UTC
Catalog-reported calls / payers (30d)10 / 4

2.Probe history

2026-09-212026-11-20
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-11-20 16:40 UTCPOSTpass402361 ms—
2026-11-18 13:40 UTCPOSTpass402224 ms—
2026-11-15 16:40 UTCPOSTpass402171 ms—
2026-11-12 13:40 UTCPOSTpass402192 ms—
2026-11-10 04:41 UTCPOSTpass402255 ms—
2026-11-07 22:40 UTCPOSTpass40238 ms—
2026-11-05 22:40 UTCPOSTpass402132 ms—
2026-10-10 12:40 UTCPOSTpass40280 ms—
2026-10-09 12:40 UTCPOSTpass402269 ms—
2026-10-08 04:40 UTCPOSTpass402231 ms—
2026-10-07 04:40 UTCPOSTpass40288 ms—
2026-10-06 04:41 UTCPOSTpass402126 ms—
2026-10-04 22:40 UTCPOSTpass402263 ms—
2026-10-03 22:40 UTCPOSTpass402301 ms—
2026-10-03 04:40 UTCPOSTpass402277 ms—
2026-10-02 13:40 UTCPOSTpass402435 ms—
2026-10-01 13:40 UTCPOSTpass402231 ms—
2026-09-30 16:40 UTCPOSTpass40267 ms—
2026-09-29 22:40 UTCPOSTpass40249 ms—
2026-09-29 04:40 UTCPOSTpass402125 ms—
2026-09-28 13:40 UTCPOSTpass402133 ms—
2026-09-27 16:40 UTCPOSTpass40239 ms—
2026-09-27 04:40 UTCPOSTpass402106 ms—
2026-09-26 13:40 UTCPOSTpass402115 ms—
2026-09-25 16:40 UTCPOSTpass40288 ms—
2026-09-24 22:40 UTCPOSTpass402140 ms—
2026-09-24 04:40 UTCPOSTpass40273 ms—
2026-09-23 13:40 UTCPOSTpass402362 ms—
2026-09-22 16:40 UTCPOSTpass40256 ms—
2026-09-21 22:40 UTCPOSTpass4022080 ms—

3.L1 — real purchases

0 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 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

settle_failed
vet402 signed a payment and got no settlement receipt back.
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 signed
vet402 signed a paid request. vet402 has not settled it on chain yet, or settlement failed, or the seller returned goods without a receipt.
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).
0/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-10 07:01settle_failed502—Base657 ms
1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: not sorted: vet402 unprovenStage: signed

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

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.

About the purchase at 2026-09-10T07:01:18Z (UTC). The form starts with that time; add what you saw instead.

20–2,000 characters · 59 so far