# ja-normalize

> ja-normalize is a paid API for AI agents from x402-ja-api.onrender.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Normalizes Japanese business text into structured data, extracting and standardizing dates, phone numbers, postal codes, and addresses from raw Japanese input including OCR and form text.

## Facts

- Endpoint: POST https://x402-ja-api.onrender.com/v1/text/normalize
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ja-normalize-417fd6a5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fAXYCtBeVBpQ1GAKh1zKd

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 ja-normalize-417fd6a5 -d '<json body>'
```

Example prompt: Take this Japanese business letter text and normalize it — extract any dates (converting 令和 or 昭和 era formats to ISO), phone numbers (in E.164 format), postal codes, and return a cleaned normalized version: '令和5年4月1日 TEL:03-1234-5678 〒100-0001 東京都千代田区'.

## When to prefer this

Choose this endpoint when you need to process Japanese-language business documents, forms, or OCR output and extract structured data like dates in Japanese era format, Japanese phone numbers, postal codes, or addresses. It is purpose-built for Japanese locale specifics (e.g. 令和/平成/昭和 era conversion, Japanese phone formatting) that generic text parsers or Western NLP pipelines will not handle correctly.

## Known failure modes

- Input text exceeds 20,000 character limit — request rejected
- Non-Japanese or empty text may return empty arrays with no extracted entities
- OCR artifacts or severely corrupted text may result in missed or malformed extractions
- Ambiguous era dates (e.g. overlapping Heisei/Reiwa boundaries) may be resolved incorrectly
- Payment failure (402) if USDC balance is insufficient or x402 payment header is missing

## How this service works

Calendar and Japan data APIs for AI agents: worldwide holidays and business days (200+ countries), plus Japanese text-to-structure (address, name, bank, company normalization). Pay per call in USDC via x402, no API key.

## Output

Returns a JSON object with: a normalized text string with standardized formatting, an array of dates each with original Japanese text and ISO 8601 equivalent, an array of phone numbers with original, national, and E.164 formats, an array of postal code strings, and an array of email addresses extracted from the input.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "maxLength": 20000,
   "description": "Japanese business text (letters, forms, OCR output)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "dates": [
   {
    "iso": "2023-04-01",
    "original": "令和5年4月1日"
   }
  ],
  "emails": [],
  "phones": [
   {
    "e164": "+81312345678",
    "national": "0312345678",
    "original": "03-1234-5678"
   }
  ],
  "normalized": "2023-04-01 TEL:03-1234-5678 〒100-0001",
  "postalCodes": [
   "1000001"
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ja-normalize-417fd6a5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-ja-api.onrender.com](https://www.zero.xyz/host/x402-ja-api.onrender.com/llms.txt)