# Japan Company Lookup | Search by Name or Corporate Number (`regbase/jp-company-lookup`) Actor

Look up Japanese companies in the official corporate registry (houjin bangou): search by company name or corporate number for the registered name, address, and status.

- **URL**: https://apify.com/regbase/jp-company-lookup.md
- **Developed by:** [regbase](https://apify.com/regbase) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Japan Company Lookup by Name or Corporate Number | Japan Corporate Registry (Official Registry Data)

Apify actor that looks up Japanese companies in the official corporate registry （法人番号， houjin bangou): search by company name or corporate number and get the registered name, address, entity type, and status — public registry data, no account or cookies required. Results come from a JSONL dataset file you point the actor at; the actor ships with a 20-record fictional sample and performs no network access. It does not contain the live registry and does not download anything.

**Cost, up front:** pay-per-event — $0.10 per actor start + $0.01 per result item. Your maximum charge for a run is fixed before you start: $0.10 + (maxResults × $0.01). The sample run below (10 results) costs $0.20. There is no rental or subscription. **If a run returns zero result items, no per-item charge applies — you pay only the $0.10 actor-start charge.**

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| query | string | (required, no default) | Company name or corporate number to search for. The console prefill is 株式会社. |
| maxResults | integer | 10 | Maximum number of results to return. Minimum 1, maximum 1000. |
| datasetPath | string | ./data/houjin_sample.jsonl | Path to the JSONL file of registry records, relative to the actor root. |

If the query is all digits after spaces and hyphens are stripped, it matches the corporate_number field exactly. Otherwise it performs a case-insensitive substring match against the record name (Japanese) or name_en (English). Matching records are sorted by corporate_number ascending and capped at maxResults. An empty result set is a valid outcome.

### Output

Each result object has exactly these 10 fields:

| Field | Meaning |
|-------|---------|
| corporate_number | The corporate number of the matched record |
| name | The registered company name in Japanese |
| name_en | The registered company name in English |
| entity_type | The raw registry entity type code |
| prefecture | The prefecture of the registered address |
| city | The city of the registered address |
| street_address | The street address line |
| postal_code | The postal code of the registered address |
| address | prefecture + city + street_address concatenated into one string |
| status | active, or closed when the record has a closing_date |

### Sample output (before the pricing section, on purpose)

Produced by running this actor (version 0.1.0) on the bundled 20-record fictional sample — the same run the Apify console test performs. Query 株式会社, maxResults 10 → 10 items. First three:

| corporate_number | name | name_en | prefecture | city | status |
|---|---|---|---|---|---|
| 1010001000001 | 株式会社あおぞら製作所 | Aozora Seisakusho Co., Ltd. | 東京都 | 渋谷区 | active |
| 1020002000002 | 山田商事株式会社 | Yamada Shoji Co., Ltd. | 大阪府 | 大阪市中央区 | active |
| 1030003000003 | 株式会社グリーンテック | Green Tech Co., Ltd. | 京都府 | 京都市中京区 | active |

The first result, in full:

```json
{
  "corporate_number": "1010001000001",
  "name": "株式会社あおぞら製作所",
  "name_en": "Aozora Seisakusho Co., Ltd.",
  "entity_type": "301",
  "prefecture": "東京都",
  "city": "渋谷区",
  "street_address": "1-2-3",
  "postal_code": "150-0002",
  "address": "東京都渋谷区1-2-3",
  "status": "active"
}
```

### Dataset format

JSONL, one JSON object per line. Fields mirror the National Tax Agency registry record in English. The actor ships with a bundled sample file of 20 fictional records at data/houjin_sample.jsonl. For real use, supply a full registry JSONL file in the same record shape and point datasetPath at it.

### Verifying the output

Every result carries the official 13-digit corporate number, so any record can be checked line by line against the National Tax Agency's public registry （法人番号公表サイト）. The data is an official public registry — no scraping, no accounts, no cookies.

### Local development

```bash
npm install
npm run test:local
```

Syntax-check the actor sources with:

```bash
node --check src/main.js
node --check src/search.js
```

### Pricing

Pay-per-event (PPE) only. Monthly rentals no longer exist on Apify. Creators keep 80% of event revenue.

| Event | Price |
|---|---|
| Actor start | $0.10 |
| Per result item | $0.01 |

Worked examples: 10 results = $0.10 + (10 × $0.01) = **$0.20**. 100 results = $0.10 + (100 × $0.01) = **$1.10**. Your spend cap is maxResults — a run can never return (or charge for) more items than you set.

### Support

Questions, or a run that does not match this description? Open the **Issues** tab on this actor's page — issues are answered within 24 hours. If an output does not match its description, we refund first.

# Actor input Schema

## `query` (type: `string`):

Company name or corporate number to search for.

## `maxResults` (type: `integer`):

Maximum number of results to return (minimum 1, maximum 1000).

## `datasetPath` (type: `string`):

Path to a JSONL file of houjin records, relative to actor root

## Actor input object example

```json
{
  "query": "株式会社",
  "maxResults": 10,
  "datasetPath": "./data/houjin_sample.jsonl"
}
```

# Actor output Schema

## `dataset` (type: `string`):

URL of the dataset containing this run's results.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "query": "株式会社"
};

// Run the Actor and wait for it to finish
const run = await client.actor("regbase/jp-company-lookup").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "query": "株式会社" }

# Run the Actor and wait for it to finish
run = client.actor("regbase/jp-company-lookup").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "query": "株式会社"
}' |
apify call regbase/jp-company-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,regbase/jp-company-lookup"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/XEQrUyiGFNFNfojkj/builds/kd8urS8qYa1QFPbaE/openapi.json