Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-15 · today

www.taifoon.io/api/coordination/x402/class/risk.address

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://www.taifoon.io/api/coordination/x402/class/risk.address
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x3574999dd4c96eb73bd6e11d4177010c83e14f5b
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-10-12 13:03 UTC / 2026-10-15 13:03 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-10-132026-10-15
Figure 1. Probe timeline, last 3 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-15 15:40 UTCPOSTpass402378 ms—
2026-10-14 10:30 UTCPOSTfail4021175 msprice_mismatchDeclared 11667 of 0x8335…2913; the 402 offered 11936 of 0x8335…2913, 11936 of 0xaf88…5831, 11936 of 0x3600…0000, 11936 of 0x5fc5…d168.
2026-10-13 10:30 UTCPOSTfail402722 msprice_mismatchDeclared 11667 of 0x8335…2913; the 402 offered 12323 of 0x8335…2913, 12323 of 0xaf88…5831, 12323 of 0x3600…0000, 12323 of 0x5fc5…d168.

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.

20–2,000 characters · 0 so far