# Japan New Companies Monitor: Daily Incorporations (`jp_registry_data/japan-new-company-monitor`) Actor

Get new companies in Japan every day from the official corporate number registry. Filter by date, prefecture and entity type. English labels, same-address counts, no NTA API key needed, no personal data. Pay per company ($3 per 1,000).

- **URL**: https://apify.com/jp_registry_data/japan-new-company-monitor.md
- **Developed by:** [JP Registry Data](https://apify.com/jp_registry_data) (community)
- **Stats:** 2 total users, 1 monthly users, 92.3% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 new companies

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 New Companies Monitor — Daily List of New Companies in Japan

Get a clean, English-labelled list of **new companies in Japan**, straight from the official corporate number registry (法人番号, run by the National Tax Agency). Pick a date range, prefectures and legal entity types, and the Actor returns one structured row per newly incorporated company.

**No API key, no registration in Japan.** Other registry tools require you to apply for your own application ID with the National Tax Agency (NTA), which is hard to do from outside Japan. This Actor reads a daily, pre-processed copy of the registry, so you can start with one click.

### What can you use it for?

- **Lead generation**: new companies need banks, accountants, insurance, office space, software and recruiting.
- **KYB / onboarding checks**: confirm that a counterparty really exists and when it was registered.
- **Market research**: count new incorporations by prefecture, city or entity type over time.
- **Monitoring**: schedule a daily run and push new companies to your CRM, spreadsheet or Slack with an integration.

### What data does it return?

Each dataset item is one newly incorporated company:

| Field | Description |
|---|---|
| `corporateNumber` | 13-digit Japanese corporate number (法人番号) |
| `name` | Registered company name, in Japanese |
| `nameKana` | Reading of the name in katakana (when available) |
| `nameEn` | English name registered with the NTA (rarely available) |
| `entityTypeCode` | NTA entity type code (`301` Kabushiki Kaisha, `305` Godo Kaisha, ...) |
| `entityType` / `entityTypeEn` | Entity type in Japanese and in English |
| `prefecture` / `prefectureEn` | Prefecture of the registered head office, in Japanese and in English |
| `city` / `street` | City or ward, and the rest of the registered address |
| `address` | Full address (prefecture + city + street) |
| `prefectureCode` / `cityCode` | JIS municipality codes (2 + 3 digits) |
| `postalCode` | Postal code (`NNN-NNNN`) |
| `assignmentDate` | Date the corporate number was assigned — a close approximation of the incorporation date |
| `sameAddressCompanyCount` | Number of other companies registered on the same block (chome / banchi). A high number often means a shared or virtual office address. Buildings are not distinguished |
| `sameNameCompanyCount` | Number of other companies with exactly the same name |
| `sourceUrl` | The company's page on the NTA Corporate Number Publication Site |
| `collectedAt` | When that page was fetched |

Empty values are `null`, never empty strings.

**No personal data and no contact details** (representative names, email, phone) are included — only public registry facts.

#### Which companies are included?

Companies whose corporate number was newly assigned on the selected dates and that are still active. Closed registrations and records withheld from publication are excluded.

### How to use it

1. Click **Try for free**.
2. Leave **Date from** and **Date to** empty to get the last 7 days (Japan time), or pick a range of up to 366 days.
3. Optionally pick **Prefectures** (empty = all of Japan) and **Entity types** (empty = all).
4. Optionally set **Max items** to cap the output (and your cost).
5. Run the Actor and download the results as JSON, CSV, Excel or via the API.

**Tip — daily monitoring:** schedule the Actor every morning with empty dates. Each run returns the last 7 days, so de-duplicate on `corporateNumber`, or set **Date from** and **Date to** to yesterday.

#### When is the data updated?

The registry is published with a delay of about one business day, and the copy is refreshed daily. When your range includes days that are not published yet, the run finishes normally and its status message lists those days. There are no new incorporations on weekends and public holidays.

### Input example

```json
{
  "dateFrom": "2026-09-01",
  "dateTo": "2026-09-30",
  "prefectures": ["13", "27"],
  "entityTypes": ["301", "305"],
  "maxItems": 5000
}
```

Prefectures use the JIS X 0401 code (`"01"` Hokkaido … `"13"` Tokyo … `"27"` Osaka … `"47"` Okinawa). The input form shows the English names.

### Output example

```json
{
  "corporateNumber": "1010001000001",
  "name": "株式会社サンプル",
  "nameKana": "サンプル",
  "nameEn": null,
  "entityTypeCode": "301",
  "entityType": "株式会社",
  "entityTypeEn": "Kabushiki Kaisha (stock company)",
  "prefecture": "東京都",
  "prefectureEn": "Tokyo",
  "city": "千代田区",
  "street": "神田神保町2-20-6",
  "address": "東京都千代田区神田神保町2-20-6",
  "prefectureCode": "13",
  "cityCode": "101",
  "postalCode": "101-0051",
  "assignmentDate": "2026-09-01",
  "sameAddressCompanyCount": 2,
  "sameNameCompanyCount": 0,
  "sourceUrl": "https://www.houjin-bangou.nta.go.jp/henkorireki-johoto.html?selHouzinNo=1010001000001",
  "collectedAt": "2026-09-02T10:00:00+09:00"
}
```

(The company above is fictitious.)

### How much does it cost?

This Actor uses **pay-per-event** pricing:

| Event | When it is charged | Price |
|---|---|---|
| Actor start | Once per run | $0.00005 per GB of memory (a default 256 MB run is charged one event) |
| `new-company` | Once per company written to the dataset | $3.00 per 1,000 companies ($0.003 each) |

Examples: 100 companies cost $0.30, 5,000 companies cost $15.00. A run that finds no companies costs only the start event. Use **Max items** or the maximum total charge of a run to cap your spending.

### FAQ

**How is this different from "Japan Corporate Registry Diff"?**
That Actor covers five kinds of registry changes (new incorporations, name changes, relocations, closures, mergers) and needs your own NTA application ID. This Actor covers new incorporations only, needs no ID, and adds the same-address and same-name counts.

**Is the assignment date the incorporation date?**
Almost. A corporate number is assigned when the company is registered, so the dates match in most cases, but the registry does not publish the incorporation date itself.

**Is this data legal to use commercially?**
The data is public information released by the National Tax Agency. Its terms of use follow the Public Data License (公共データ利用規約 第1.0版), which requires attribution and a note when data is processed. Please review the terms for your own use case, and follow the laws that apply to your use (for example anti-spam laws for marketing). See the attribution below.

### Limitations

- **New incorporations only.** Name changes, relocations, closures and mergers are not included.
- **Date range:** up to 366 days per run, no future dates.
- **Japanese text:** names and addresses are returned as registered, in Japanese. Field names and the entity type / prefecture labels are in English.
- **No industry, phone, website or representative data.**
- **`sameAddressCompanyCount` / `sameNameCompanyCount`** may be `null` when the reference snapshot of the whole registry is not fresh enough to count reliably.

### Data source and attribution

出典：国税庁法人番号公表サイト（加工して作成）

Source: National Tax Agency Corporate Number Publication Site (国税庁法人番号公表サイト), https://www.houjin-bangou.nta.go.jp/

This Actor processes the data (selection of active new companies, field mapping, English labels, and the same-address / same-name counts). The output is not the original NTA data as published. 国税庁法人番号公表サイト（国税庁）（<https://www.houjin-bangou.nta.go.jp/>）を加工して作成

This service uses the NTA Corporate Number System Web-API, but the content of the service is not guaranteed by the National Tax Agency. (このサービスは、国税庁法人番号システムWeb-API 機能を利用して取得した情報をもとに作成しているが、サービスの内容は国税庁によって保証されたものではない)

Terms: [Corporate Number Publication Site terms of use](https://www.houjin-bangou.nta.go.jp/riyokiyaku/) (based on the [Public Data License v1.0](https://www.digital.go.jp/resources/open_data/public_data_license_v1.0)) and [Web-API terms of use](https://www.houjin-bangou.nta.go.jp/webapi/riyokiyaku.html).

### Support

Found a bug or need another field or filter? Open an issue on the Actor's **Issues** tab.

# Actor input Schema

## `dateFrom` (type: `string`):

First corporate-number assignment date to include (YYYY-MM-DD, Asia/Tokyo). The assignment date approximates the incorporation date. Defaults to 7 days before Date to. The period is at most 366 days. Dates before 2015-10-05 (start of the corporate number system) are rejected.

## `dateTo` (type: `string`):

Last assignment date to include (YYYY-MM-DD, Asia/Tokyo). Defaults to yesterday in Asia/Tokyo, or to Date from if that is later. Must not be in the future. The period is at most 366 days.

## `prefectures` (type: `array`):

Limit to new companies registered in these prefectures (JIS X 0401 codes, shown with English names). Leave empty for all of Japan.

## `entityTypes` (type: `array`):

Limit to these legal entity types (NTA entity type codes). Leave empty for all types.

## `maxItems` (type: `integer`):

Maximum number of companies to output (also caps the pay-per-event cost). Results are in order of assignment date, so the earliest companies are kept.

## Actor input object example

```json
{
  "prefectures": [
    "13"
  ],
  "maxItems": 100
}
```

# Actor output Schema

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

No description

# 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 = {
    "prefectures": [
        "13"
    ],
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("jp_registry_data/japan-new-company-monitor").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 = {
    "prefectures": ["13"],
    "maxItems": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("jp_registry_data/japan-new-company-monitor").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 '{
  "prefectures": [
    "13"
  ],
  "maxItems": 100
}' |
apify call jp_registry_data/japan-new-company-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jp_registry_data/japan-new-company-monitor"
        }
    }
}
```

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/sX54Y6J7yuYGFPyb1/builds/0LLmeqW0NOSysc9KW/openapi.json