# JP Data Enrich API — Company Lookup by Houjin Number

> JP Data Enrich API — Company Lookup by Houjin Number is a paid API for AI agents from jp-data-enrich.kasanegi123.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Enriches a Japanese company record using its corporate registration number (houjin number) by aggregating data from gBizINFO, Kanpou, and EDINET

## Facts

- Endpoint: GET https://jp-data-enrich.kasanegi123.workers.dev/api/enrich/company-by-houjin-number
- 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/jp-data-enrich-api-company-lookup-by-houjin-number-a09ce6bb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0eZW4elWvhB2uPUeCqzXv

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 jp-data-enrich-api-company-lookup-by-houjin-number-a09ce6bb
```

Example prompt: Can you pull all available corporate info for the Japanese company with houjin number 1234567890123 — I need their registration details, any official gazette entries, and EDINET filings for a supplier due diligence check?

## When to prefer this

Use this endpoint when you need to enrich or verify a Japanese corporate entity and already have its 13-digit houjin (corporate registration) number. It is the right choice for KYB workflows, supplier vetting, B2B prospecting targeting Japanese companies, or any task requiring aggregated Japanese government data from gBizINFO, Kanpou, and EDINET in a single call. Prefer this over manual database lookups or general web search when structured, machine-readable Japanese corporate data is needed without requiring an API key.

## Known failure modes

- Invalid or non-existent houjin number returns a 404 or empty result
- Malformed houjin number (not 13 digits) causes a 400 validation error
- Company not found in any of the three source databases returns partial or null data
- Payment failure via x402/USDC micropayment results in 402 Payment Required
- Upstream government API downtime causes 503 or timeout errors

## How this service works

Japanese corporate enrichment API for AI agents / B2B sales / supplier research / KYB support. gBizINFO + Kanpou + EDINET aggregation. x402 micropayments on Base. No API key.

## Output

A JSON object containing enriched corporate data for the specified Japanese company, aggregated from gBizINFO (basic registration and business info), Kanpou (official gazette announcements), and EDINET (securities/financial disclosures), covering fields such as company name, address, industry, registration status, and available filings.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "mimeType": "application/json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/jp-data-enrich-api-company-lookup-by-houjin-number-a09ce6bb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from jp-data-enrich.kasanegi123.workers.dev](https://www.zero.xyz/host/jp-data-enrich.kasanegi123.workers.dev/llms.txt)