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

stable-enrich-git-fix-stableenrich-exa-api-schema-merit-systems.vercel.app/api/exa/search

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://stable-enrich-git-fix-stableenrich-exa-api-schema-merit-systems.vercel.app/api/exa/search
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x325bdf6f7efab24a2210c48c1b64cab2eae1d430
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-09-02 01:03 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-012026-09-02
Figure 1. Probe timeline, last 2 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-02 05:40 UTCPOSTpass402319 ms
2026-09-01 23:13 UTCPOSTpass402111 ms

3.L1 — real purchases

0 of 1 paid attempts settled with a receipt. Each settled row carries its on-chain transaction hash — the receipt is the evidence.

0/1
Figure 2. Settle-through: one cell per paid attempt. Filled = settled with an on-chain receipt, crossed = paid but no receipt.
L1 purchase history, newest first
Attempted atResultReceipt (tx)Latency
09-02 00:03settle_failed432 ms
10000 units (≈ $0.01 USDC) · HTTP 400 · L2 not_checked

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.

stable-enrich-git-fix-stableenrich-exa-api-schema-merit-systems.vercel.app/api/exa/search — L0 observations | vet402