# CHAPPY Japan Address Preflight

> CHAPPY Japan Address Preflight is a paid API for AI agents from chappy-japan-address-preflight.pre23964wb.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Validates a Japanese address at the town level against Japan Post data, returning a match status (MATCHED, AMBIGUOUS, CONFLICT, or NOT_FOUND) with ordered candidates and safe next-action guidance.

## Facts

- Endpoint: POST https://chappy-japan-address-preflight.pre23964wb.workers.dev/v1/jp/address/preflight
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/chappy-japan-address-preflight-8c3c2507
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__LW5WlfAgxGlqrNAXCHUk

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 chappy-japan-address-preflight-8c3c2507 -d '<json body>'
```

Example prompt: Before we ship this order to 〒150-0001 Tokyo, Shibuya-ku, Jingumae 1-chome, can you do a delivery preflight check on that Japanese address to make sure the postal code and town actually match?

## When to prefer this

Choose this endpoint when you need town-level Japan Post evidence for a Japanese address before committing to a delivery, payment, form save, or vendor record — especially when you need a structured status (MATCHED/AMBIGUOUS/CONFLICT/NOT_FOUND) plus actionable next-step guidance rather than a simple boolean. It is particularly suited for agentic workflows that need provenance and candidate lists to handle ambiguity gracefully. Prefer it over generic geocoding APIs when Japan-specific postal data fidelity and use-case-aware recommendations are required.

## Known failure modes

- NOT_FOUND returned when postal code or address text does not correspond to any Japan Post record
- AMBIGUOUS returned when multiple town-level candidates exist and cannot be resolved from the input alone
- CONFLICT returned when the postal code and address text disagree at the town level
- Malformed postal code (wrong digit count or unsupported characters) may result in a validation error
- raw_address below minimum length or exceeding 512 characters will be rejected
- Missing required fields (postal_code or raw_address) return a 400-level error

## How this service works

Town-level Japan Post evidence for buyer agents. Returns MATCHED, AMBIGUOUS, CONFLICT, or NOT_FOUND with ordered candidates, provenance, limitations, and the next safe input action.

## Output

Returns a status of MATCHED, AMBIGUOUS, CONFLICT, or NOT_FOUND along with an ordered list of candidate addresses sourced from Japan Post evidence, provenance details, any known limitations, and a recommended next safe input action for the calling agent to take.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "use_case": {
   "enum": [
    "delivery",
    "visit",
    "vendor_onboarding",
    "form_submission"
   ],
   "type": "string"
  },
  "postal_code": {
   "type": "string",
   "description": "Japanese seven-digit postal code; full-width digits and common hyphens are accepted"
  },
  "raw_address": {
   "type": "string",
   "maxLength": 512,
   "minLength": 2,
   "description": "Japanese address text to compare at the town level"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/chappy-japan-address-preflight-8c3c2507/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chappy-japan-address-preflight.pre23964wb.workers.dev](https://www.zero.xyz/host/chappy-japan-address-preflight.pre23964wb.workers.dev/llms.txt)