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

phion.systems/v1/paid/transaction-assurance

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://phion.systems/v1/paid/transaction-assurance
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0x7beca68dd9ac733d4de6b16d16b85dc391c071e2
Declared price (base units)15000
Catalog statusactive
First seen / last seen2026-09-21 01:03 UTC / 2026-11-22 14:06 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-212026-11-19
Figure 1. Probe timeline, last 24 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-19 06:30 UTCPOSTpass402280 ms—
2026-10-18 22:40 UTCPOSTpass402153 ms—
2026-10-17 16:40 UTCPOSTpass402476 ms—
2026-10-15 21:40 UTCPOSTpass402208 ms—
2026-10-14 15:40 UTCPOSTpass402415 ms—
2026-10-13 15:40 UTCPOSTpass402797 ms—
2026-10-12 03:40 UTCPOSTpass40248 ms—
2026-10-11 03:40 UTCPOSTfail—10000 mstimeoutNo response headers arrived within 10 seconds.
2026-10-10 03:40 UTCPOSTpass402130 ms—
2026-10-08 22:40 UTCPOSTpass402169 ms—
2026-10-07 16:40 UTCPOSTpass402360 ms—
2026-10-06 22:40 UTCPOSTpass402387 ms—
2026-10-05 22:40 UTCPOSTpass402140 ms—
2026-10-04 16:40 UTCPOSTpass402231 ms—
2026-10-03 16:40 UTCPOSTpass402345 ms—
2026-10-02 22:40 UTCPOSTpass402159 ms—
2026-10-02 04:40 UTCPOSTpass4022345 ms—
2026-10-01 13:40 UTCPOSTpass402220 ms—
2026-09-30 13:40 UTCPOSTpass402131 ms—
2026-09-29 16:40 UTCPOSTpass402191 ms—
2026-09-28 22:40 UTCPOSTpass402264 ms—
2026-09-28 13:40 UTCPOSTpass402561 ms—
2026-09-25 10:30 UTCPOSTpass402153 ms—
2026-09-21 11:24 UTCPOSTpass402162 ms—

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

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-11-19relisted{"status":"delisted"}{"status":"active"}
2026-10-20delisted{"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