# Japan Address Parse

> Japan Address Parse is a paid API for AI agents from api.jpverify.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Parses a Japanese address string into structured components (chome, block, lot, house number, etc.) without geocoding or postal validation.

## Facts

- Endpoint: POST https://api.jpverify.com/jp-address/parse
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/japan-address-parse-a6ec74f7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wLWc4IF2BOMXtjV9r3CKt

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability japan-address-parse-a6ec74f7 -d '<json body>'
```

Example prompt: Can you parse this Japanese address into its components — prefecture, city, town, chome, ban, and go? The address is '東京都新宿区西新宿２丁目８番１号', and use standard parser mode with output in Japanese.

## When to prefer this

Choose this endpoint when you need only structural parsing of a Japanese address into its hierarchical components (prefecture, city, ward, town, chome, ban, go) without needing geocoordinates or postal-code validation output. It is the right choice for data normalization pipelines, CRM imports, or form processing where you want machine-readable address fields. Use the sibling Japan Address Geocode endpoint if you also need latitude/longitude, or Japan Address Validate if you need a quality/deliverability decision.

## Known failure modes

- Address string is empty or exceeds 500 characters — validation error returned
- Postal code format doesn't match pattern (###-####) — rejected with format error
- Address is too ambiguous to resolve to a unique town even with postal code evidence — ambiguity flag set in response
- Non-Japanese or romanized address input may result in failed or partial parsing
- Strict parser profile rejects addresses with irregular formatting that standard mode would accept
- Network or service unavailability returns HTTP 5xx error

## Output

Returns a structured breakdown of the input Japanese address into components such as prefecture (都道府県), city/municipality (市区町村), town (町域), chome (丁目), block number (番地), and house number (号). May also include an ambiguity flag if the town cannot be uniquely resolved, and localized field labels in Japanese or both languages depending on the response_language setting.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/japan-address-parse-a6ec74f7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.jpverify.com](https://www.zero.xyz/host/api.jpverify.com/llms.txt)