api.jpverify.com/jp-address/parse
1.Catalog declaration
| Resource URL | https://api.jpverify.com/jp-address/parse |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0xe4a4e5b226be71e7b6ed523bc7a91089c770572f |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-20 01:30 UTC / 2026-11-11 14:05 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-11-11 14:32 UTC | POST | pass | 402 | 616 ms | — |
| 2026-10-05 10:30 UTC | POST | unverified | 422 | 596 ms | request_shapeUnpaid POST with an empty JSON body answered 422 before any payment challenge; not measured (vet402 does not guess the input). |
| 2026-09-29 07:38 UTC | POST | unverified | 422 | 263 ms | request_shapeUnpaid POST with an empty JSON body answered 422 before any payment challenge; not measured (vet402 does not guess the input). |
| 2026-09-24 16:40 UTC | POST | fail | 422 | 626 ms | no_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-23 22:40 UTC | POST | fail | 422 | 947 ms | no_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-23 04:40 UTC | POST | fail | 422 | 762 ms | no_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-22 13:40 UTC | POST | fail | 422 | 757 ms | no_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-21 16:40 UTC | POST | fail | 422 | 869 ms | no_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-20 22:40 UTC | POST | fail | 422 | 866 ms | no_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-20 04:40 UTC | POST | fail | 422 | 610 ms | no_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-19 13:40 UTC | POST | fail | 422 | 2537 ms | no_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-18 16:40 UTC | POST | fail | 422 | 575 ms | no_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-18 04:40 UTC | POST | fail | 422 | 782 ms | no_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-17 13:40 UTC | POST | fail | 422 | 701 ms | no_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-16 16:40 UTC | POST | fail | 422 | 605 ms | no_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 16:40 UTC | POST | fail | 422 | 850 ms | no_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 UTC | POST | fail | 422 | 972 ms | no_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 UTC | POST | fail | 422 | 632 ms | no_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 UTC | POST | fail | 422 | 627 ms | no_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 UTC | POST | fail | 422 | 681 ms | no_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 UTC | POST | fail | 422 | 955 ms | no_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 22:40 UTC | POST | fail | 530 | 96 ms | no_402HTTP 530 instead of 402 to an unpaid POST. |
| 2026-09-11 13:40 UTC | POST | fail | 422 | 586 ms | no_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 UTC | POST | fail | 422 | 637 ms | no_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 05:40 UTC | POST | fail | 422 | 622 ms | no_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-09 17:40 UTC | POST | fail | 422 | 724 ms | no_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-09 05:40 UTC | POST | fail | 422 | 603 ms | no_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-08 17:40 UTC | POST | fail | 422 | 722 ms | no_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 23:40 UTC | POST | fail | 422 | 955 ms | no_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 14:40 UTC | POST | fail | 422 | 760 ms | no_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. |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
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.