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

api.agentmercantile.com/v1/portfolio-preflight

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.agentmercantile.com/v1/portfolio-preflight
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0xdb7b2b54f80479826222749a2ea73a8acc306e1e
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-23 01:18 UTC / 2026-11-16 10:05 UTC
Catalog-reported calls / payers (30d)15 / 8

2.Probe history

2026-09-282026-11-11
Figure 1. Probe timeline, last 30 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-11-11 02:31 UTCPOSTunverified400443 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-11-02 16:40 UTCPOSTunverified400147 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-31 13:40 UTCPOSTunverified40091 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-29 13:40 UTCPOSTunverified400184 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-27 16:40 UTCPOSTunverified400120 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-26 00:40 UTCPOSTunverified400127 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-23 22:40 UTCPOSTunverified400575 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-22 13:40 UTCPOSTunverified400266 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-20 22:40 UTCPOSTunverified400204 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-19 13:40 UTCPOSTunverified400177 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-17 22:40 UTCPOSTunverified4001116 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-16 12:40 UTCPOSTunverified400413 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-14 21:40 UTCPOSTunverified400286 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-13 21:40 UTCPOSTunverified400446 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-12 12:40 UTCPOSTunverified400272 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-11 12:40 UTCPOSTunverified400484 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-10 12:40 UTCPOSTunverified400151 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-09 12:40 UTCPOSTunverified400365 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-08 04:40 UTCPOSTunverified400102 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-07 04:40 UTCPOSTunverified400128 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-06 04:41 UTCPOSTunverified400134 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-04 22:40 UTCPOSTunverified400221 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-03 22:40 UTCPOSTunverified400161 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-03 04:40 UTCPOSTunverified400140 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-02 13:40 UTCPOSTunverified400157 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-10-01 16:40 UTCPOSTunverified400246 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-09-30 16:40 UTCPOSTunverified400260 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-09-29 22:40 UTCPOSTunverified400170 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-09-29 07:38 UTCPOSTunverified400170 msrequest_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-09-28 16:40 UTCPOSTfail400364 msno_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail.

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