Skip to main content
vet402
MenuClose
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-11-10 · 2 days ago
vet402Back to the registerMethodology

www.taifoon.io/api/coordination/x402/class/mcp.digest

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://www.taifoon.io/api/coordination/x402/class/mcp.digest
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0x3574999dd4c96eb73bd6e11d4177010c83e14f5b
Declared price (base units)6795
Catalog statusactive
First seen / last seen2026-10-12 13:03 UTC / 2026-11-12 18:05 UTC
Catalog-reported calls / payers (30d)13 / 4

2.Probe history

2026-10-132026-11-10
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 atMethodVerdictHTTPLatencyReason
2026-11-10 22:40 UTCPOSTfail402896 msprice_mismatchDeclared 6795 of 0x8335…2913; the 402 offered 1200 of 0x8335…2913, 1200 of 0xaf88…5831, 1200 of 0x3600…0000, 1200 of 0x5fc5…d168.
2026-11-08 16:40 UTCPOSTfail402524 msprice_mismatchDeclared 6795 of 0x8335…2913; the 402 offered 1200 of 0x8335…2913, 1200 of 0xaf88…5831, 1200 of 0x3600…0000, 1200 of 0x5fc5…d168.
2026-11-06 13:40 UTCPOSTfail402273 msprice_mismatchDeclared 6795 of 0x8335…2913; the 402 offered 1200 of 0x8335…2913, 1200 of 0xaf88…5831, 1200 of 0x3600…0000, 1200 of 0x5fc5…d168.
2026-11-04 06:41 UTCPOSTfail4021178 msprice_mismatchDeclared 6795 of 0x8335…2913; the 402 offered 1200 of 0x8335…2913, 1200 of 0xaf88…5831, 1200 of 0x3600…0000, 1200 of 0x5fc5…d168.
2026-11-01 10:30 UTCPOSTpass402412 ms—
2026-10-30 13:40 UTCPOSTfail402222 msprice_mismatchDeclared 8645 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913, 5000 of 0xaf88…5831, 5000 of 0x3600…0000, 5000 of 0x5fc5…d168.
2026-10-28 13:40 UTCPOSTfail402234 msprice_mismatchDeclared 8645 of 0x8335…2913; the 402 offered 9000 of 0x8335…2913, 9000 of 0xaf88…5831, 9000 of 0x3600…0000, 9000 of 0x5fc5…d168.
2026-10-26 18:40 UTCPOSTfail4021044 msprice_mismatchDeclared 8645 of 0x8335…2913; the 402 offered 16687 of 0x8335…2913, 16687 of 0xaf88…5831, 16687 of 0x3600…0000, 16687 of 0x5fc5…d168.
2026-10-25 00:40 UTCPOSTpass402365 ms—
2026-10-22 22:40 UTCPOSTfail402952 msprice_mismatchDeclared 7358 of 0x8335…2913; the 402 offered 10000 of 0x8335…2913, 10000 of 0xaf88…5831, 10000 of 0x3600…0000, 10000 of 0x5fc5…d168.
2026-10-21 13:40 UTCPOSTpass402329 ms—
2026-10-19 22:40 UTCPOSTfail4022587 msprice_mismatchDeclared 5606 of 0x8335…2913; the 402 offered 5094 of 0x8335…2913, 5094 of 0xaf88…5831, 5094 of 0x3600…0000, 5094 of 0x5fc5…d168.
2026-10-18 13:40 UTCPOSTpass402610 ms—
2026-10-17 04:40 UTCPOSTfail402319 msprice_mismatchDeclared 6803 of 0x8335…2913; the 402 offered 5303 of 0x8335…2913, 5303 of 0xaf88…5831, 5303 of 0x3600…0000, 5303 of 0x5fc5…d168.
2026-10-15 15:40 UTCPOSTfail402575 msprice_mismatchDeclared 7415 of 0x8335…2913; the 402 offered 8000 of 0x8335…2913, 8000 of 0xaf88…5831, 8000 of 0x3600…0000, 8000 of 0x5fc5…d168.
2026-10-14 10:30 UTCPOSTfail402725 msprice_mismatchDeclared 12443 of 0x8335…2913; the 402 offered 11509 of 0x8335…2913, 11509 of 0xaf88…5831, 11509 of 0x3600…0000, 11509 of 0x5fc5…d168.
2026-10-13 10:30 UTCPOSTfail402839 msprice_mismatchDeclared 12443 of 0x8335…2913; the 402 offered 14103 of 0x8335…2913, 14103 of 0xaf88…5831, 14103 of 0x3600…0000, 14103 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

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.

About the purchase at 2026-10-26T12:00:56Z (UTC). The form starts with that time; add what you saw instead.

20–2,000 characters · 59 so far