api.jpverify.com/jp-company/filings
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
| Resource URL | https://api.jpverify.com/jp-company/filings |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0xe4a4e5b226be71e7b6ed523bc7a91089c770572f |
| Declared price (base units) | 10000 |
| Catalog status | delisted (since 2026-09-08 01:03 UTC) |
| First seen / last seen | 2026-08-29 01:11 UTC / 2026-09-07 01:03 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-07 23:40 UTC | GET | fail | 422 | 596 ms | no_402HTTP 422 instead of 402 to an unpaid GET. |
| 2026-09-07 14:40 UTC | GET | fail | 422 | 697 ms | no_402HTTP 422 instead of 402 to an unpaid GET. |
| 2026-09-04 11:24 UTC | GET | pass | 402 | 521 ms | — |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-08 | delisted | {"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.