# PARRY Japan Phone & Domain Observation Records ($0.004/lookup) (`andque/parry-jp-number-domain-records`) Actor

Look up observation records for Japanese phone numbers (03/050/0120/0800) and domains with source attribution, confirmed dates, observed roles, and counts. Returns neutral facts and source citations without evaluative scores or labels.

- **URL**: https://apify.com/andque/parry-jp-number-domain-records.md
- **Developed by:** [Masatoshi Mori](https://apify.com/andque) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 phone number or domain record lookups

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

## PARRY — Japanese Phone Number & Domain Observation Records

Look up observation records for Japanese phone numbers (`03`, `050`, `0120`, `0800`, etc.) and domain names at **$0.004 USD per valid lookup**.

PARRY returns **neutral facts and source citations** (which source recorded the identifier, when it was confirmed, what role it appeared in, and observation counts). It does **not** return evaluative scores, grades, or labels.

***

### English

#### 1. What You Can Look Up

PARRY returns observation records for a given phone number or domain:

- **Source & Evidence URL**: Which source contains the record (`source_id`, `source_class`, `source_kind`, `evidence_url`, `attribution`).
- **Confirmed Date**: When the record was observed or confirmed (`first_observed_at`, `last_observed_at`, `last_checked_at`).
- **Observed Role (`subject_role`)**: How the identifier appeared — e.g., as a listed subject in a public source (`listed_subject`), or as an authenticated sender (`authenticated_sender`). Unauthenticated sender claims (`claimed_sender`) and body-only mentions (`body_mention`) are excluded row-by-row by default unless explicitly requested via input flags.
- **Counts**: Separate counts for external public listings (`external_listing`) and first-party gate observations (`direct_observation`), plus expired checkout session counts (`expired_checkout_sessions`).
- **Nuisance Review Counts (Phone Numbers)**: `nuisance_reported` is `true` when 1 or more reviews listed in the source stated that the phone call was a nuisance, and `false` when no reviews stated it was a nuisance and 1 or more reviews can be read as not stating it. When only reviews that cannot be determined from the text exist, this field is not returned. The counts are `nuisance_report_count` (stated), `nuisance_not_reported_count` (not stated), and `nuisance_unclear_count` (cannot be determined from text), and their sum is `reviews_classified`. This is not an evaluation by andq.

**No Evaluative Labels or Scores:**
PARRY never returns scores, ratings, or labels judging whether a phone number or domain is good or bad. It returns only the recorded facts and their sources; any decision-making belongs to the calling AI agent and its operator.

**Meaning of `no_record`:**
When no record is found in the published scope, PARRY returns `status: "no_record"`. This means only that no record exists within PARRY's current published scope; it is **not** a clearance, endorsement, or determination that the identifier is problem-free.

#### 2. Pricing (Pay-Per-Event)

| Item | Price (USD) |
|---|---|
| Lookup per valid in-scope phone number or domain (`record-lookup`) | **$0.004** |
| 100 valid lookups | **$0.40** |
| Actor start (`apify-actor-start`, billed automatically by Apify) | **$0.001** |

- **Charged (`$0.004`)**: `record_found` and `no_record`. The lookup fee applies whether or not a record is found.
- **Not Charged (`$0.000`)**:
  - `invalid_input` (input cannot be parsed as a phone number or domain)
  - `out_of_scope` (e.g., personal mobile numbers `070/080/090`, free email provider domains)
  - `error` (service-side error)
  - `not_charged_budget_reached` (items skipped because the run reached the user's maximum spend limit)

#### 3. Example Use Case: Giving an AI Assistant a Small Lookup Budget

1. An operator gives their AI receptionist or email assistant a small budget for record lookups.
2. A call or message arrives from an unfamiliar phone number or domain.
3. The AI assistant spends **$0.004** from its budget to query PARRY for that 1 identifier.
4. PARRY returns which sources recorded that identifier and on what confirmed dates (or `no_record` if none).
5. Using the returned facts and the operator's own policy, the AI assistant decides whether to connect, call back, or ask the operator for confirmation.

You can set a maximum spend limit (`maxTotalChargeUsd`) per Apify run. Lookups beyond the remaining budget are not billed and return `status: "not_charged_budget_reached"` without content.

#### 4. Current Published Scope

| Target | Record Scope | Count |
|---|---|---|
| **Phone Numbers** | Public directory listing facts for fixed-line, `050`, and toll-free (`0120`/`0800`) numbers. Includes review count, posting period, breakdown of call purposes, count of reviews stating the call was a nuisance, confirmed date, and source URL. Business names are returned only when publication of the number on the business's own official web page has been confirmed. | 316 (as of 2026-11-22, updated daily) |
| **Domains** | Domains recorded with confirmed dates in public listings, and direct observation records at first-party intake gates operated by andQ Inc. | 22,449 (as of 2026-11-22, updated daily) |

- Domain records derived from public listings cover the most recent 12 published monthly batches from the source (October 2025 – September 2026 confirmed records). Shared hosting, dynamic DNS, and URL shortener domains where many unrelated users share subdomains or paths are excluded from the lookup scope (`out_of_scope`).
- Public listing records represent the historical or point-in-time fact that the identifier was listed in that source on the confirmed date. They do not represent current activity or the domain owner's conduct.
- External listing records (`external_listing`) and first-party direct observations (`direct_observation`) are counted separately.
- Personal mobile phone numbers (`070`/`080`/`090`) are outside the published lookup scope (`out_of_scope`).
- At launch, lookups are available via Apify Actor runs (including API invocations). Incremental change feeds (`feed`), per-subject time-series history (`history`), and Standby / MCP server endpoints are **planned for future release** after inspection.

***

### 日本語（Japanese）

#### 1. 何を照合できるか

PARRYが返すのは、指定された電話番号・ドメインについての観測記録です。

- **どの出典に記録があるか**（出典名と参照URL：`source_id`、`source_class`、`source_kind`、`evidence_url`、`attribution`）
- **いつ確認された記録か**（確認日：`first_observed_at`、`last_observed_at`、`last_checked_at`）
- **どういう現れ方をしたか**（出典の掲載対象 `listed_subject` なのか、確認できた送信元 `authenticated_sender` なのか等。自己申告の送信元 `claimed_sender` と本文中の登場 `body_mention` は既定で行単位に除外され、入力フラグで明示指定したときだけ返ります）
- **記録の件数**（外部掲載 `external_listing` と直接観測 `direct_observation` を分けて集計）
- **`nuisance_reported` / `nuisance_report_count` / `nuisance_not_reported_count` / `nuisance_unclear_count` / `reviews_classified`**: `nuisance_reported` は、出典に掲載された口コミのうち、その電話を迷惑だと述べたものが1件以上あるとき `true`、迷惑だと述べたものが無く、述べていないと読めるものが1件以上あるとき `false` です。本文から読み取れない口コミしか無い場合、この項目は返しません。件数は `nuisance_report_count`（述べている）、`nuisance_not_reported_count`（述べていない）、`nuisance_unclear_count`（読み取れない）です。andqによる評価ではありません。

**評価は返しません：**
PARRYは、その番号やドメインが良いか悪いかの評価、点数、ラベルを返しません。返すのは事実と出典だけで、判断は照合したAIとその運用者が行います。

**`no_record`（該当する記録なし）の意味：**
記録が見つからない場合は `status: "no_record"` を返します。これは「PARRYの公開範囲に記録が無い」という意味であり、問題がないという判定や保証ではありません。

#### 2. 料金（Pay per event）

| 項目 | 料金 |
|---|---|
| 照合（有効な電話番号1件、またはドメイン1件：`record-lookup`） | **0.004米ドル** |
| 100件を照合した場合の照合料 | **0.40米ドル** |
| 起動料（`apify-actor-start`、Apifyにより自動計上） | **0.001米ドル** |

- **照合料がかかるもの（$0.004）**: `record_found`（記録あり）および `no_record`（記録なし）。記録が見つかった場合も、見つからなかった場合も同じ照合料がかかります。
- **照合料がかからないもの（$0.000）**:
  - `invalid_input`（番号・ドメインとして解釈できない入力）
  - `out_of_scope`（個人の携帯電話番号 `070/080/090`、フリーメールのドメイン等の公開範囲外）
  - `error`（サービス側の障害）
  - `not_charged_budget_reached`（利用者の実行予算上限に達して課金されなかった分）

#### 3. 使い方の例：AIに予算を持たせる

1. 運用者が、自分のAI秘書に「照合に使ってよい予算」を与えます。
2. 知らない番号からの着信や、初めて見るドメインからの連絡が届きます。
3. AI秘書は、与えられた予算のうち0.004ドルを使って、その番号またはドメインを1件照合します。
4. PARRYは、その対象がどの出典に、いつの確認日で記録されているかを返します。記録が無ければ、無い（`no_record`）と返します。
5. AI秘書は、その結果を材料に、取り次ぐか、折り返すか、運用者に確認するかを、運用者が決めた基準で判断します。

Apifyの実行には利用上限（最大課金額）を指定でき、上限を超える分は課金されず、内容は返されません（`status: "not_charged_budget_reached"` として件数のみ返ります）。

#### 4. 公開時点で照合できる範囲

| 対象 | 記録の内容 | 件数 |
|---|---|---|
| **電話番号** | 公開情報に掲載されている事実（固定電話・050・フリーダイヤル）。口コミの掲載件数、掲載の期間、用件の内訳、迷惑だと述べた口コミの件数、確認日、出典。事業者名を返すのは、事業者自身のページでその番号の公表を確認できた場合だけ | 316件（2026年11月22日時点。毎日更新） |
| **ドメイン** | 公開情報で、確認日付きで記録されているドメイン。および、株式会社andq自身の問い合わせ窓口で直接観測した記録 | 22,449件（2026年11月22日時点。毎日更新） |

- 公開情報に由来するドメインの記録は、出典が公開している直近12か月分（2025年10月〜2026年9月確認分）です。多数の利用者が配下に入る共用のホスティングや短縮URLのドメインは、照合の対象から外しています（`out_of_scope`）。
- 公開情報に由来する記録は「その出典に、その確認日時点で掲載されていた」という事実です。現在の状態や、持ち主の行為を示すものではありません。
- 公開情報に由来する記録と、株式会社andqが直接観測した記録は、分けて返します。
- 個人の携帯電話番号は、公開時点の照合対象に含めていません。
- 公開時点では、Apifyの実行（APIからの呼び出しを含む）で照合できます。新着・訂正の差分取得（`feed`）、1件ごとの履歴取得（`history`）、および Standby／MCP（Model Context Protocol）経由での呼び出しは、提供を予定しています。

# Actor input Schema

## `identifiers` (type: `array`):

List of 1 to 1,000 identifiers (Japanese phone numbers in domestic or E.164 format, domain names, or URLs).

## `include_sender_claims` (type: `boolean`):

By default (false), self-declared sender domains without mail authentication alignment are excluded row-by-row. Set to true to include them.

## `include_body_mentions` (type: `boolean`):

By default (false), phone numbers and link domains that only appeared inside message bodies are excluded row-by-row. Set to true to include them.

## Actor input object example

```json
{
  "identifiers": [
    "03-1234-5678",
    "example.co.jp"
  ],
  "include_sender_claims": false,
  "include_body_mentions": false
}
```

# Actor output Schema

## `results` (type: `string`):

One dataset item per input identifier.

## `summary` (type: `string`):

Run summary and Pay-Per-Event charge counts.

# 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 = {
    "identifiers": [
        "03-1234-5678",
        "example.co.jp"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("andque/parry-jp-number-domain-records").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 = { "identifiers": [
        "03-1234-5678",
        "example.co.jp",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("andque/parry-jp-number-domain-records").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 '{
  "identifiers": [
    "03-1234-5678",
    "example.co.jp"
  ]
}' |
apify call andque/parry-jp-number-domain-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,andque/parry-jp-number-domain-records"
        }
    }
}
```

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/c4Fa1cxqp4KkJ0Nk9/builds/HjXpqLiD7FvRn8LKZ/openapi.json
