Jp Address Validate
by Japan Address Validate in Documents & files
Japanese address validation and quality decision. Keywords: Japanese address validation, address conflict, address quality, partial match, 日本住所検証. Validate parser, postal, and geocoder evidence using one address policy, returning exact, partial, ambiguous, conflict, or unverified status with the accepted hierarchy and reasons. / 使用统一规则合并解析、邮编和地理编码证据,并返回完全一致、部分一致、歧义、冲突或未验证状态。
https://api.jpverify.com/jp-address/validate- Price
- $0.005
- per call in USDC
- Uptime
- 96.2%
- last 30 days
- Response time
- 890 ms
- 1.1 s slowest 5%
- Last check
- Passed
- 23 min ago, next in 8 min
Reliability
How to call it
POST https://api.jpverify.com/jp-address/validate
Each call costs $0.005 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://api.jpverify.com/jp-address/validate
content-type: application/json
{
"address": "東京都千代田区千代田1丁目1番1号",
"required_level": 8,
"strict": false
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string or null | No | Original Japanese address. / 元の日本住所。 |
geocode_evidence | object or null | No | Optional prior output from /jp-address/geocode; candidates and statuses are advisory and recomputed locally. / 任意のgeocode出力。候補とstatusは補助情報で、ローカルで再計算されます。 |
parsed | object or null | No | Output from /jp-address/parse or normalize containing at least one non-empty address component. / parseまたはnormalizeの出力。空でない住所構成要素を1つ以上含めます。 |
postal_evidence | object or null | No | Optional prior output from /jp-address/postal-lookup; status/confidence are recomputed and not trusted. / 任意のpostal-lookup出力。statusとconfidenceは再計算され、無条件には信頼されません。 |
required_level | integer or null | No | Required hierarchy level; Jageocoder 5/6=oaza/aza, 7=block, 8=building/house node. / 必須階層。Jageocoderの5/6=大字・字、7=街区、8=建物・号ノード。 |
strict | boolean | No | Require all supplied evidence to agree. / 入力された根拠の完全一致を要求。 Default: false. |
Example response
The provider's example. We can't check it without paying.
{
"address_validated": false,
"confidence": 0.79,
"geographic_match_confidence": 0.8,
"granularity": "block",
"match_level": 7,
"match_status": "partial",
"parse_confidence": 0.99,
"parsed_level": 8,
"postal_code_match": null,
"postal_confidence": null,
"precision_satisfied": false,
"reasons": [
"provider_level_below_requested_level"
],
"requested_level": 8,
"validation_scope": "hierarchy_and_evidence_consistency",
"validation_source": "parser + Jageocoder local dictionary",
"verified_level": 7,
"warnings": []
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.005.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://api.jpverify.com/jp-address/validate' \
-H 'content-type: application/json' \
--data-raw '{"address":"\u6771\u4eac\u90fd\u5343\u4ee3\u7530\u533a\u5343\u4ee3\u75301\u4e01\u76ee1\u756a1\u53f7","required_level":8,"strict":false}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://api.jpverify.com/jp-address/validate' \
-H 'content-type: application/json' \
--data-raw '{"address":"\u6771\u4eac\u90fd\u5343\u4ee3\u7530\u533a\u5343\u4ee3\u75301\u4e01\u76ee1\u756a1\u53f7","required_level":8,"strict":false}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.005 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.005" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.005 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.jpverify.com%2Fjp-address%2Fvalidate&method=POST
const res = await pay("https://api.jpverify.com/jp-address/validate", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"address": "\u6771\u4eac\u90fd\u5343\u4ee3\u7530\u533a\u5343\u4ee3\u75301\u4e01\u76ee1\u756a1\u53f7",
"required_level": 8,
"strict": false
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.005 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.005"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://api.jpverify.com/jp-address/validate",
json={
"address": "\u6771\u4eac\u90fd\u5343\u4ee3\u7530\u533a\u5343\u4ee3\u75301\u4e01\u76ee1\u756a1\u53f7",
"required_level": 8,
"strict": False,
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 23 min ago | Passed | 402 | 1.0 s | $0.005 |
| 5 h ago | Passed | 402 | 923 ms | $0.005 |
| 9 h ago | Passed | 402 | 859 ms | $0.005 |
| 13 h ago | Passed | 402 | 440 ms | $0.005 |
| 18 h ago | Passed | 402 | 883 ms | $0.005 |
Show 10 older checks
| 22 h ago | Passed | 402 | 921 ms | $0.005 |
| 26 h ago | Passed | 402 | 949 ms | $0.005 |
| 30 h ago | Passed | 402 | 885 ms | $0.005 |
| 34 h ago | Passed | 402 | 1.1 s | $0.005 |
| 38 h ago | Passed | 402 | 868 ms | $0.005 |
| 41 h ago | Passed | 402 | 1.1 s | $0.005 |
| 45 h ago | Expected HTTP 402, got 502 | 502 | 914 ms | - |
| 2 days ago | Passed | 402 | 991 ms | $0.005 |
| 2 days ago | Passed | 402 | 960 ms | $0.005 |
| 2 days ago | Passed | 402 | 890 ms | $0.005 |