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

api.cardhedger.com/v1/agent/cards/card-match

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.cardhedger.com/v1/agent/cards/card-match
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0x2a5a489b56345f8320375c11e1f61411b73ac32d
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-10-24 13:02 UTC / 2026-11-15 08:05 UTC
Catalog-reported calls / payers (30d)43 / 1

2.Probe history

2026-10-262026-11-15
Figure 1. Probe timeline, last 12 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-11-15 04:40 UTCPOSTfail402690 msmetadata_mismatchDeclared payTo 0x2a5a…c32d on eip155:8453; the 402 offered 0x3818…db39 on eip155:8453.
2026-11-14 04:40 UTCPOSTfail402781 msmetadata_mismatchDeclared payTo 0xec65…1a65 on eip155:8453; the 402 offered 0x0f83…8b2b on eip155:8453.
2026-11-13 10:30 UTCPOSTfail402680 msmetadata_mismatchDeclared payTo 0x6e6e…a906 on eip155:8453; the 402 offered 0x0479…4716 on eip155:8453.
2026-11-07 22:40 UTCPOSTfail402656 msmetadata_mismatchDeclared payTo 0x4911…a06f on eip155:8453; the 402 offered 0x53f8…36e1 on eip155:8453.
2026-11-07 04:40 UTCPOSTfail402868 msmetadata_mismatchDeclared payTo 0xe3ac…e9f7 on eip155:8453; the 402 offered 0x9907…25bb on eip155:8453.
2026-11-06 10:30 UTCPOSTfail4021825 msmetadata_mismatchDeclared payTo 0x4e7d…3bd3 on eip155:8453; the 402 offered 0xff8a…2b42 on eip155:8453.
2026-11-01 22:40 UTCPOSTfail402792 msmetadata_mismatchDeclared payTo 0x4f96…f842 on eip155:8453; the 402 offered 0xa390…61ec on eip155:8453.
2026-10-31 22:40 UTCPOSTfail4021654 msmetadata_mismatchDeclared payTo 0x4422…63bc on eip155:8453; the 402 offered 0xcd12…b519 on eip155:8453.
2026-10-31 04:40 UTCPOSTfail402836 msmetadata_mismatchDeclared payTo 0x1d4f…dce6 on eip155:8453; the 402 offered 0x2bcd…3378 on eip155:8453.
2026-10-29 13:40 UTCPOSTfail402754 msmetadata_mismatchDeclared payTo 0x8967…512f on eip155:8453; the 402 offered 0x8a10…2a5c on eip155:8453.
2026-10-27 10:30 UTCPOSTfail402836 msmetadata_mismatchDeclared payTo 0x1bd9…e83e on eip155:8453; the 402 offered 0xcbc6…5f47 on eip155:8453.
2026-10-26 10:31 UTCPOSTfail402977 msmetadata_mismatchDeclared payTo 0x1bd9…e83e on eip155:8453; the 402 offered 0x5b16…0f6a on eip155:8453.

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.

20–2,000 characters · 0 so far