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

intent-api-matchmaker-mainnet-production.up.railway.app/v1/match

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://intent-api-matchmaker-mainnet-production.up.railway.app/v1/match
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xbf11e11ab3607ae7f1c51b79fd0e585c0cca4b82
Declared price (base units)3000
Catalog statusactive
First seen / last seen2026-08-21 01:57 UTC / 2026-09-09 01:03 UTC
Catalog-reported calls / payers (30d)6 / 6

2.Probe history

2026-09-042026-09-09
Figure 1. Probe timeline, last 11 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-09 14:40 UTCPOSTpass402112 ms—
2026-09-08 23:40 UTCPOSTfail4021971 msprice_mismatch
2026-09-08 14:40 UTCPOSTfail402251 msprice_mismatch
2026-09-07 23:40 UTCPOSTfail402231 msprice_mismatch
2026-09-07 14:40 UTCPOSTfail4022181 msprice_mismatch
2026-09-06 23:40 UTCPOSTfail402337 msprice_mismatch
2026-09-06 14:40 UTCPOSTfail402514 msprice_mismatch
2026-09-05 17:40 UTCPOSTfail402211 msprice_mismatch
2026-09-05 05:40 UTCPOSTfail402726 msprice_mismatch
2026-09-04 17:40 UTCPOSTfail402123 msprice_mismatch
2026-09-04 11:24 UTCPOSTfail402169 msprice_mismatch

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.

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.