Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: unverifiedLast probed: 2026-10-21 · 26 days ago

test.agentify.ad/x402/item_98989ba7dd664150afae9b20301ec450/purchase

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://test.agentify.ad/x402/item_98989ba7dd664150afae9b20301ec450/purchase
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:84532
Receiving address0xbea58ebf815dad2bb9d256645a9ce7fa269d21a0
Declared price (base units)20000
Catalog statusdelisted (since 2026-10-21 13:01 UTC)
First seen / last seen2026-10-20 13:01 UTC / 2026-10-21 01:01 UTC
Catalog-reported calls / payers (30d)13 / 2

2.Probe history

2026-10-21
Figure 1. Probe timeline, last 1 probe for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-21 10:30 UTCPOSTfail4091270 msno_402HTTP 409 instead of 402 to an unpaid POST.

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-21delisted{"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