Skip to main content
vet402
MenuClose
Independent MeasurementEndpoint record (L0 · L1)Published state: withdrawnLast probed: 2026-09-15 · 39 days ago
vet402Back to the registerMethodology

api.jpverify.com/jp-company/verify

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://api.jpverify.com/jp-company/verify
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0xe4a4e5b226be71e7b6ed523bc7a91089c770572f
Declared price (base units)5000
Catalog statusdelisted (since 2026-09-16 01:03 UTC)
First seen / last seen2026-08-17 01:06 UTC / 2026-09-15 01:03 UTC
Catalog-reported calls / payers (30d)2 / 1

2.Probe history

2026-09-012026-09-15
Figure 1. Probe timeline, last 12 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-15 16:40 UTCPOSTfail422265 msno_402HTTP 422 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.
2026-09-15 04:40 UTCPOSTfail422273 msno_402HTTP 422 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.
2026-09-14 13:40 UTCPOSTfail422206 msno_402HTTP 422 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.
2026-09-13 22:40 UTCPOSTfail422465 msno_402HTTP 422 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.
2026-09-13 04:40 UTCPOSTfail422388 msno_402HTTP 422 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.
2026-09-12 16:40 UTCPOSTfail422207 msno_402HTTP 422 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.
2026-09-12 04:40 UTCPOSTfail422643 msno_402HTTP 422 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.
2026-09-11 13:40 UTCPOSTfail422189 msno_402HTTP 422 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.
2026-09-10 23:40 UTCPOSTfail4222313 msno_402HTTP 422 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.
2026-09-10 11:24 UTCPOSTfail422511 msno_402HTTP 422 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.
2026-09-07 11:24 UTCPOSTpass402210 ms—
2026-09-01 23:14 UTCPOSTpass402707 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-09-16delisted{"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