Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: withdrawnLast probed: 2026-10-05 · 20 days ago

aep-api.fly.dev/v1/citation-report/large

Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://aep-api.fly.dev/v1/citation-report/large
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0xf184b4ed26e0866417487c56acda10ddb5411e9d
Declared price (base units)3000000
Catalog statusdelisted (since 2026-10-06 01:01 UTC)
First seen / last seen2026-09-05 01:03 UTC / 2026-10-03 01:04 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-052026-10-05
Figure 1. Probe timeline, last 10 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-05 10:30 UTCPOSTfail402167 msmetadata_mismatchDeclared payTo 0xf184…1e9d on eip155:8453; the 402 offered 0x3bc7…53f5 on eip155:8453.
2026-09-29 10:30 UTCPOSTfail4022208 msmetadata_mismatchDeclared payTo 0xf184…1e9d on eip155:8453; the 402 offered 0x3bc7…53f5 on eip155:8453.
2026-09-29 07:38 UTCPOSTfail402385 msmetadata_mismatchDeclared payTo 0xf184…1e9d on eip155:8453; the 402 offered 0x3bc7…53f5 on eip155:8453.
2026-09-28 10:30 UTCPOSTfail40281 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-23 10:31 UTCPOSTfail402133 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-19 11:24 UTCPOSTfail40226 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-17 11:24 UTCPOSTfail40279 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-13 11:24 UTCPOSTfail40226 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-09 11:24 UTCPOSTpass40253 ms—
2026-09-05 11:24 UTCPOSTpass40245 ms—

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

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-10-06delisted{"status":"active"}{"status":"delisted"}

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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. 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