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

api.loyalspark.online/x402-gateway/recipient-api/cancel-offer

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.loyalspark.online/x402-gateway/recipient-api/cancel-offer
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x40a8cdd6a10ec1a8cb3dfb2834675e7a2cf4ad8b
Declared price (base units)5000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC
Catalog-reported calls / payers (30d)95 / 13

2.Probe history

2026-08-142026-09-25
Figure 1. Probe timeline, last 8 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-25 10:30 UTCPOSTpass402162 ms—
2026-09-21 11:24 UTCPOSTpass402179 ms—
2026-09-17 12:35 UTCPOSTpass402144 ms—
2026-09-14 11:24 UTCPOSTpass402115 ms—
2026-09-10 11:24 UTCPOSTpass402210 ms—
2026-09-07 11:24 UTCPOSTpass402235 ms—
2026-09-02 11:24 UTCPOSTpass402159 ms—
2026-08-14 08:52 UTCPOSTfail402101 msaccepts_invalid

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

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.