Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+21 moreClaude CodeCursorCodex CLIMuseDots
Manus
Grok
Grok Bot+18 agentsJapanese Address Normalization & Validation
This skill lets your agent turn them into consistent, structured records and tells you how far an address was actually confirmed, instead of silently guessing.
Free
Japanese Address Normalization & Validation
Example session with this skill installed
Our customer typed this delivery address: "東京都千代田区丸の内１丁目９−１", postal code 100-0005. Clean it up for our shipping system and tell me whether the postal code and address actually match.
- Read your context and instructions
- Compiled the japanese address normalization
Summary
The address normalizes to
東京都千代田区丸の内1丁目9-1, and postal code
100-0005 belongs to the same town (東京都千代田区丸の内), so the postal code and address are consistent. The address is confirmed down to block 9 (丸の内1丁目9番); house number 1 is not in the address dictionary, so the result is partial, not matched. Cost: 2 calls, $0.006.
Step 1: postal code
POST /jp-address/postal-lookup with postal_code 100-0005 ($0.001) → matched, Japan Post data dated 2026-10-30.
| Field | Value |
|---|---|
| Prefecture | 東京都 |
| City | 千代田区 |
| Town | 丸の内 |
| Reading | トウキョウト チヨダク マルノウチ |
Step 2: normalize and parse
POST /jp-address/normalize ($0.005) → match_status: partial, confidence 0.82.
| Component | Value |
|---|---|
| Normalized | 東京都千代田区丸の内1丁目9-1 |
| Prefecture / city / town | 東京都 / 千代田区 / 丸の内 |
| 丁目 / block / house | 1丁目 / 9番 / 1号 |
| Confirmed to | Block level (丸の内1丁目9番) |
| Coordinates | 35.681252, 139.767235 |
| Changes made | Full-width digits and the dash normalized |
| Warnings | Dictionary match is one level below the parsed house number |
Comparison
| Check | Result |
|---|---|
| Postal code town vs. address town | Both 丸の内, 千代田区 — consistent |
| Address exists | Yes, to block 9 |
| House number 1 | Not confirmed by the dictionary (normal for many buildings) |
Next steps
- Save the normalized address and its components in your shipping system, with postal code 100-0005.
- Delivery to block level is safe; if you need house-level certainty (for example, for KYB), ask the customer for the building name.
- For many addresses at once, call the same endpoints per row; postal lookup costs $0.001 each.
Connects securely to your tools. The creator never sees your data.
About this skill
## What it does Japanese addresses are written many ways: full-width or half-width digits, 丁目/番/号 or hyphens, old and new place names, missing postal codes. This skill lets your agent turn them into consistent, structured records and tells you how far an address was actually confirmed, instead of silently guessing. - **Normalize** an address into one canonical form and a parsed hierarchy (prefecture, city, ward, town, 丁目, block, house, building, floor, room) — `POST /jp-address/normalize`. - **Parse** without validation when you only need the components — `POST /jp-address/parse`. - **Postal lookup** from a 7-digit postal code, or the postal code for a prefecture/city/town — `POST /jp-address/postal-lookup` (Japan Post data). - **Geocode** to coordinates with the matched level and reasons — `POST /jp-address/geocode`. - **Validate** with parser, postal and geocoder evidence and get exact / partial / ambiguous / conflict / unverified — `POST /jp-address/validate`. ## Why it is safe to automate Every result says which level matched (for example, block but not house number) and why. A lower-level match is reported as `partial`, never as `matched`, so an agent will not mark an incomplete address as verified. Data sources: Japan Post postal data and the Jageocoder address dictionary, both run locally by JPVerify; no third-party geocoding service sees your addresses. ## Pricing The skill is free. The JPVerify API is paid per successful call: postal lookup $0.001; normalize, parse, geocode and validate $0.005 each. Pay with a JPVerify API key (prepaid credits, free starter credits for new accounts) or x402 USDC on Base. Invalid input is never charged. Docs: https://api.jpverify.com/docs/api-key · Source: https://github.com/japanverify/jpverify-skills
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Requires a JPVerify API key or x402 wallet. Normalization does not infer a missing postal code (use postal lookup). Confirmation depth depends on the address dictionary: many addresses are confirmed to block (番) level, and house numbers or building names are often not covered. Japanese addresses only.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 1 day ago
- Free with an Agensi account
- Accounts
Jpverify
Permissions
Allowed Hosts
Network access to api.jpverify.com only, to send the addresses and postal codes the user provides. The API key is read from the JPVERIFY_API_KEY environment variable and sent only to api.jpverify.com. No files are read or written.