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

767-2676.com/v1/receipt

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://767-2676.com/v1/receipt
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x5f5a631e975183d084f60d7121e967b30ec83cb8
Declared price (base units)1000
Catalog statusactive
First seen / last seen2026-09-01 01:03 UTC / 2026-09-27 01:02 UTC
Catalog-reported calls / payers (30d)95 / 6

2.Probe history

2026-09-052026-09-26
Figure 1. Probe timeline, last 27 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-26 22:40 UTCPOSTpass402120 ms—
2026-09-26 04:40 UTCPOSTpass402147 ms—
2026-09-25 13:40 UTCPOSTpass402122 ms—
2026-09-24 16:40 UTCPOSTpass402233 ms—
2026-09-23 22:40 UTCPOSTpass402349 ms—
2026-09-23 04:40 UTCPOSTpass4022284 ms—
2026-09-22 13:40 UTCPOSTfail422278 msno_402
2026-09-21 16:40 UTCPOSTfail422145 msno_402
2026-09-20 22:40 UTCPOSTfail422153 msno_402
2026-09-20 13:40 UTCPOSTfail422371 msno_402
2026-09-19 16:40 UTCPOSTfail422263 msno_402
2026-09-18 22:40 UTCPOSTfail422229 msno_402
2026-09-18 04:40 UTCPOSTfail42266 msno_402
2026-09-17 13:40 UTCPOSTfail422202 msno_402
2026-09-16 22:40 UTCPOSTfail422316 msno_402
2026-09-15 22:40 UTCPOSTfail4222107 msno_402
2026-09-15 13:40 UTCPOSTfail422443 msno_402
2026-09-14 16:40 UTCPOSTfail4222108 msno_402
2026-09-13 22:40 UTCPOSTfail422128 msno_402
2026-09-13 13:40 UTCPOSTfail4222257 msno_402
2026-09-12 22:40 UTCPOSTfail422337 msno_402
2026-09-12 04:40 UTCPOSTfail422124 msno_402
2026-09-11 16:40 UTCPOSTfail4221970 msno_402
2026-09-11 04:40 UTCPOSTfail422605 msno_402
2026-09-09 11:24 UTCPOSTfail42296 msno_402
2026-09-06 11:24 UTCPOSTfail42298 msno_402
2026-09-05 11:24 UTCPOSTfail422122 msno_402

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.

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-23 06:00settled (nonce-bound)2000x8e90c003…321f904 ms
1000 units (≈ $0.001 USDC) · L2 no_declaration

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. (767-2676.com · measured 2026-09-23)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/52e64b92-78d6-4e83-a456-d3985c740134.svg)](https://vet402.com/observatory/e/52e64b92-78d6-4e83-a456-d3985c740134)

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint.

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.