# RegBase Japan Company Verification | Signed Records (`regbase/jp-signed-record`) Actor

Issue and verify Ed25519-signed evidence records for Japanese companies by 13-digit corporate number. Every claim cites its source dataset and as-of date; verification is offline with the published public key (key_id 3f21f43a142d5252). Free sandbox tier for evaluating the record format.

- **URL**: https://apify.com/regbase/jp-signed-record.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

## RegBase — Japan Company Verification (Signed Records)

Issue and verify **Ed25519-signed evidence records** about Japanese
companies by 13-digit corporate number (法人番号).

- Every claim in a record cites its source dataset and as-of date.
- Verification is offline with the published public key
  (key_id `3f21f43a142d5252`).
- A signature attests issuer + integrity only, never the truth of the
  claims. Not a compliance product.

### Actions

| action | input | output |
|---|---|---|
| `health` | — | status, key_id, record counts |
| `issue` | `corporate_number` (13 digits) | the signed record, or `INVALID_CORPORATE_NUMBER` / `NOT_FOUND` |
| `verify` | `record` (the full record object) | `{valid: true, ...}` or the failure reason |

### Data

EDINET listed-company detail (3,808 companies, as of 2026-11-07) plus a
clearly labelled **fictional demo extract** (5 invented companies) that
exercises the address / unlisted-company paths. Demo records say so in
every claim's `source` field.

Free sandbox tier for evaluating the record format, endpoints and
verification flow. Signed records are included from the $99/mo tier in
the RegBase ladder — the incumbent Japan verification service reserves
signed records for its $399/mo tier.

# Actor input Schema

## `action` (type: `string`):

issue: create a signed record for a corporate number. verify: check a signed record. health: service status.

## `corporate_number` (type: `string`):

Required for action=issue.

## `record` (type: `object`):

Required for action=verify: the full signed record object.

## Actor input object example

```json
{
  "action": "issue",
  "corporate_number": "1180301018771"
}
```

# 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 = {
    "corporate_number": "1180301018771"
};

// Run the Actor and wait for it to finish
const run = await client.actor("regbase/jp-signed-record").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 = { "corporate_number": "1180301018771" }

# Run the Actor and wait for it to finish
run = client.actor("regbase/jp-signed-record").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 '{
  "corporate_number": "1180301018771"
}' |
apify call regbase/jp-signed-record --silent --output-dataset

```

## MCP server setup

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

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/gm8hQItzylmAj8yk9/builds/e7Q47rfAQ2KYM4iJ0/openapi.json