passlisted in Coinbase#3 by calls of 6 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% / 91%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-09 07:13 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.005 USDC
- Networks
- 1
How has the volume on this endpoint moved?
TOLL files jp address geocode under search: a POST endpoint on api.jpverify.com, listed in the Coinbase registry.
A call to jp address geocode costs 0.005 USDC on Base, as declared.
Callers of jp address geocode supply a json body with the fields address and max_candidates.
jp address geocode returns json; the example shows status, matched, warnings, candidates, verified_level, candidate_count and 2 others.
jp address geocode answered the sweep of 2026-10-29 with a valid 402, passing 32 of 35 sweeps since 2026-09-11.
jp address geocode is one of 6 listed endpoints on api.jpverify.com, tied 3rd by calls with 3 others among them.
jp address geocode takes 13% of the calls counted across api.jpverify.com.
In the trailing 30 days: one call, one payer.
jp address geocode was last called 4 days before the snapshot.
Closest in price to jp address geocode within search: web search at search.agent.s.brave.app and search at twitter.use.x402atlas.com.
jp address geocode is priced above 24% of comparable listings in search.
Its payee wallet receives for 18 listed endpoints on one host.
The seller's tags on jp address geocode are japan, address, geocode and forward-geocoding.
Exactly this price appears on 365 other listings in search.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.005 USDC | exact | 0xe4A4E5…70572F |
the checks, as of 2026-10-29 11:37 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-10-29 11:37 UTC | pass | 0 | daily-2026-10-29 |
| 2026-10-28 12:04 UTC | pass | 0 | daily-2026-10-28 |
| 2026-10-27 11:41 UTC | pass | 0 | daily-2026-10-27 |
| 2026-10-23 12:11 UTC | pass | 0 | daily-2026-10-23 |
| 2026-10-21 21:36 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-19 11:53 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-16 09:39 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 11:38 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 09:30 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 14:48 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 11:47 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 10:26 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 18:37 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 12:04 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 13:55 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 12:57 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 13:37 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 11:55 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 14:33 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 07:49 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 16:56 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 09:37 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 09:05 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 21:10 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-23 08:04 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 08:18 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 08:40 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-19 06:38 UTC | fail | 1 | daily-2026-09-19 |
| 2026-09-17 06:28 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 06:27 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 06:43 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 06:12 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 06:03 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 08:20 UTC | fail | 1 | daily-2026-09-12 |
| 2026-09-11 13:29 UTC | fail | 1 | 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-10-09 07:13 UTC · method · live
The input and output block
{
"input": {
"body": {
"address": "東京都千代田区千代田1丁目1番1号",
"max_candidates": 3
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"status": "matched",
"matched": "東京都千代田区千代田一丁目一番一号",
"warnings": [],
"candidates": [
{
"source": "Jageocoder local dictionary",
"reasons": [
"all_requested_components_matched"
],
"latitude": 35.6852,
"longitude": 139.7528,
"address_id": 123,
"confidence": 0.98,
"normalized": "東京都千代田区千代田1丁目1番1号",
"granularity": "building",
"match_level": 8,
"unmatched_tail": null,
"match_completeness": "exact"
}
],
"verified_level": 8,
"candidate_count": 1,
"geocoder_status": "ready",
"upstream_matched": [
"東京都千代田区千代田一丁目一番一号"
],
"dictionary_version": null,
"precision_satisfied": true,
"minimum_acceptable_level": 8
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-13 14:08 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 geocode on api.jpverify.com", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/api-jpverify-com-jp-address-geocode-daa1f6/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-api-jpverify-com-jp-address-geocode-daa1f6-2026-10-13T14-08Z,
author = {TOLL},
title = {jp address geocode on api.jpverify.com},
howpublished = {\url{https://tollindex.com/e/api-jpverify-com-jp-address-geocode-daa1f6/at/2026-10-13T14-08Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.