Endpoints from api.jpverify.com
Every service we watch, including those that do not meet our listing criteria. The same metrics for each. Agents can run the same query at /api/v1/services.
6 matching · page 1 of 1 · show all
| Service | What it does (capability tree) | Purpose tags | Latest scheduled check | Scheduled checks passed / run (30-day window) | Lowest price per call (US$) | Response time of latest check (ms) | Freshness | Added from | Provider | Payment networks | Payment-terms changes (90 days) | Registry: unique payers (30 days) | Registry: paid calls (30 days) | Type | Endpoint we check | Monitoring since |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| api.jpverify.com | Invoicing and billing Accounting |
invoicevatvies+2 | Live, payment required |
100% · 2 of 2 run 0 missed · 1 day of history |
$0.05 | 541 ms | Fresh checked daily |
Registry | api.jpverify.com 6 endpoints from jpverify.com |
eip155:8453 | 0 in 1 day tracked | 1 | 1 | API | POST api.jpverify.com/v1/invoices/counterpart… |
2026-10-17 |
| Japan Postal Lookup | Other (not placed in a branch yet) | japanpostal-codelookup+2 | Client error (4xx) |
0% · 0 of 2 run 0 missed · 2 days of history |
$0.001 | 539 ms | Fresh checked daily |
Registry | api.jpverify.com 6 endpoints from jpverify.com |
eip155:8453 | no valid payment request yet | 2 | 2 | API | POST api.jpverify.com/jp-address/postal-looku… |
2026-10-16 |
| Japan Address Geocode | Maps and geocoding | japanaddressgeocode+2 | Client error (4xx) |
0% · 0 of 2 run 0 missed · 1 day of history |
$0.005 | 524 ms | Fresh checked daily |
Registry | api.jpverify.com 6 endpoints from jpverify.com |
eip155:8453 | no valid payment request yet | 1 | 1 | API | POST api.jpverify.com/jp-address/geocode |
2026-10-16 |
| Japan Address Parse | Maps and geocoding | japanaddressparse+2 | Client error (4xx) |
0% · 0 of 2 run 0 missed · 1 day of history |
$0.005 | 486 ms | Fresh checked daily |
Registry | api.jpverify.com 6 endpoints from jpverify.com |
eip155:8453 | no valid payment request yet | 1 | 1 | API | POST api.jpverify.com/jp-address/parse |
2026-10-16 |
| Japan Address Validate | Maps and geocoding | japanaddressvalidation+2 | Client error (4xx) |
0% · 0 of 2 run 0 missed · 1 day of history |
$0.005 | 577 ms | Fresh checked daily |
Registry | api.jpverify.com 6 endpoints from jpverify.com |
eip155:8453 | no valid payment request yet | 1 | 1 | API | POST api.jpverify.com/jp-address/validate |
2026-10-16 |
| api.jpverify.com | Verification | cross-borderjapanuk+2 | Client error (4xx) |
0% · 0 of 2 run 0 missed · 1 day of history |
$0.04 | 517 ms | Fresh checked daily |
Registry | api.jpverify.com 6 endpoints from jpverify.com |
eip155:8453 | no valid payment request yet | 1 | 1 | API | POST api.jpverify.com/v1/entities/resolve-cro… |
2026-10-17 |
Scroll sideways for more columns; hover over shortened values to see them in full. Every column heading links to its exact definition in the field dictionary. Registry columns are the registry's own figures.