passlisted in Coinbase#2 by calls of 18 on this host
0.005 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 2
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-09-14 20:06 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.005 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 28 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
With 18 endpoints listed on api.jpverify.com, jp address parse is tied 2nd by calls with 3 others.
The request to jp address parse is a json body with the fields address and response_language.
jp address parse returns json; the example shows city, town, block, chome, house, original and 2 others.
The registry's counters give jp address parse 2 calls and 2 unique payers over 30 days, every call from a different payer.
jp address parse was last called 1 day before the snapshot.
Per call, jp address parse declares 0.005 USDC on Base.
It accounts for 8% of the calls counted across the host.
jp address parse, a POST endpoint on api.jpverify.com, appears in the Coinbase registry; TOLL's taxonomy puts it in scraping.
jp address parse answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to jp address parse within scraping: web extract at x402.ottoai.services and research at sh-origin.walls.sh.
Among comparable prices in scraping, jp address parse sits above 22% of them.
The wallet paid by jp address parse is the payee of 18 endpoints on one host.
The seller's own tags are japan, address, parse and components.
The price of jp address parse is declared by 39 other listings in scraping too.
the payment options, as of 2026-09-15 16:57 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.005 USDC | exact | 0xe4A4E5…70572F |
the checks, as of 2026-09-15 05:47 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-15 05:47 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 05:20 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 05:15 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 07:32 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 11:18 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-14 20:06 UTC · method · live
The input and output block
{
"input": {
"body": {
"address": "東京都千代田区千代田1丁目1番1号",
"response_language": "ja"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"city": "千代田区",
"town": "千代田",
"block": "1番",
"chome": "1丁目",
"house": "1号",
"original": "東京都千代田区千代田1丁目1番1号",
"normalized": "東京都千代田区千代田1丁目1番1号",
"prefecture": "東京都",
"parse_status": "parsed",
"parsed_level": 8,
"verified_level": null,
"parse_confidence": 0.95,
"precision_satisfied": false
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 16:57 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "jp address parse on api.jpverify.com", snapshot of 2026-09-15 16:57 UTC. https://tollindex.com/e/api-jpverify-com-jp-address-parse-8bb45a/at/2026-09-15T16-57Z. Accessed [access date].
BibTeX
@misc{toll-e-api-jpverify-com-jp-address-parse-8bb45a-2026-09-15T16-57Z,
author = {TOLL},
title = {jp address parse on api.jpverify.com},
howpublished = {\url{https://tollindex.com/e/api-jpverify-com-jp-address-parse-8bb45a/at/2026-09-15T16-57Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 16:57 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.