Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-28 · 1 day ago

phion.systems/v1/paid/transaction-recovery

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://phion.systems/v1/paid/transaction-recovery
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0x7beca68dd9ac733d4de6b16d16b85dc391c071e2
Declared price (base units)	10000
Catalog status	active
First seen / last seen	2026-09-12 01:03 UTC / 2026-09-29 01:03 UTC
Catalog-reported calls / payers (30d)	1 / 1

2.Probe history

2026-09-122026-09-28

Figure 1. Probe timeline, last 17 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.

L0 probe history, newest first
Probed at	Method	Verdict	HTTP	Latency	Reason
2026-09-28 22:40 UTC	POST	pass	402	257 ms	—
2026-09-28 04:40 UTC	POST	pass	402	316 ms	—
2026-09-27 13:40 UTC	POST	pass	402	255 ms	—
2026-09-26 16:40 UTC	POST	pass	402	2117 ms	—
2026-09-25 22:40 UTC	POST	pass	402	217 ms	—
2026-09-25 04:40 UTC	POST	pass	402	179 ms	—
2026-09-24 13:40 UTC	POST	pass	402	208 ms	—
2026-09-23 16:40 UTC	POST	pass	402	215 ms	—
2026-09-22 22:40 UTC	POST	pass	402	199 ms	—
2026-09-22 04:40 UTC	POST	pass	402	166 ms	—
2026-09-21 13:40 UTC	POST	pass	402	301 ms	—
2026-09-20 16:40 UTC	POST	pass	402	178 ms	—
2026-09-20 04:40 UTC	POST	pass	402	655 ms	—
2026-09-19 11:24 UTC	POST	pass	402	35 ms	—
2026-09-17 11:24 UTC	POST	pass	402	145 ms	—
2026-09-13 11:24 UTC	POST	pass	402	416 ms	—
2026-09-12 11:24 UTC	POST	fail	400	228 ms	no_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.

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 = signed, and not settled on-chain.

L1 purchase history, newest first
Attempted at	Result	HTTP	Receipt (tx)	Latency
09-20 06:022026-09-20 06:02 UTC	settled (nonce-bound)	200	0x2bd480e9…115b	962 ms
10000 units (≈ $0.01 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 receipt](https://vet402.com/api/badge/endpoint/7890b858-1f4f-4b62-b4ac-d909a940d4b1.svg)](https://vet402.com/observatory/e/7890b858-1f4f-4b62-b4ac-d909a940d4b1)

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-20T06:02:19Z (UTC). The form starts with that time; add what you saw instead.