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

phion.systems/v1/paid/trust/company-enrichment-evidence

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://phion.systems/v1/paid/trust/company-enrichment-evidence
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x7beca68dd9ac733d4de6b16d16b85dc391c071e2
Declared price (base units)5000
Catalog statusactive
First seen / last seen2026-09-16 01:03 UTC / 2026-09-29 01:03 UTC
Catalog-reported calls / payers (30d)4 / 2

2.Probe history

2026-09-162026-09-29
Figure 1. Probe timeline, last 19 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-29 04:40 UTCPOSTfail422327 msno_402HTTP 422 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.
2026-09-28 13:40 UTCPOSTfail422158 msno_402HTTP 422 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.
2026-09-27 16:40 UTCPOSTfail422139 msno_402HTTP 422 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.
2026-09-26 22:40 UTCPOSTfail422178 msno_402HTTP 422 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.
2026-09-26 04:40 UTCPOSTfail422135 msno_402HTTP 422 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.
2026-09-25 13:40 UTCPOSTfail42244 msno_402HTTP 422 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.
2026-09-24 16:40 UTCPOSTfail422105 msno_402HTTP 422 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.
2026-09-23 22:40 UTCPOSTfail42247 msno_402HTTP 422 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.
2026-09-23 04:40 UTCPOSTfail42237 msno_402HTTP 422 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.
2026-09-22 16:40 UTCPOSTfail422107 msno_402HTTP 422 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.
2026-09-21 22:40 UTCPOSTfail422188 msno_402HTTP 422 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.
2026-09-21 04:40 UTCPOSTfail422199 msno_402HTTP 422 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.
2026-09-20 13:40 UTCPOSTfail4221940 msno_402HTTP 422 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.
2026-09-19 16:40 UTCPOSTpass402112 ms—
2026-09-18 22:40 UTCPOSTpass402160 ms—
2026-09-18 04:40 UTCPOSTpass40244 ms—
2026-09-17 16:40 UTCPOSTpass40266 ms—
2026-09-16 22:40 UTCPOSTpass40246 ms—
2026-09-16 11:24 UTCPOSTpass402365 ms—

3.L1 — real purchases

0 of 1 paid attempts settled with a receipt, and 0 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 of those paid attempts are held as inconclusive rather than counted against this seller (0 settled and answered 4xx, 1 answered 4xx with no settlement receipt, 0 answered 402 or 5xx while our own payer wallet was out of USDC, 2026-09-13 00:00 to 2026-09-15 23:49 UTC). A 4xx says the request was not one the server would accept, and we cannot rule out that the request was ours to get wrong: vet402 buys with no API key of the seller's, and sends a POST body only when the seller declares one. This is the same principle the methodology already applied to path_template URLs, applied to the body and the authentication header as well. The rows are not deleted and not hidden — they are below, with their status and HTTP code, and they are out of the denominator for delivered (corrections).

Terms in this table

settle_failed
vet402 signed a payment and got no settlement receipt back.
unsettled_4xx
held_reason in the export: the paid request got a 4xx with no settlement receipt and no transaction.
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.
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).
0/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 atResultHTTPReceipt (tx)Latency
09-16 12:08settle_failed422—244 ms
5000 units (≈ $0.005 USDC) · L2 not_checkedWhose side: not sorted: no charge

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

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-16T12:08:04Z (UTC). The form starts with that time; add what you saw instead.

20–2,000 characters · 59 so far