# Phone Validation & Routing Intelligence (`tryva/phone-validation-routing-intelligence`) Actor

Validate and normalize phone numbers, identify country and line type, and apply deterministic routing policy with ACCEPT, REVIEW, or REJECT decisions.

- **URL**: https://apify.com/tryva/phone-validation-routing-intelligence.md
- **Developed by:** [smile flow](https://apify.com/tryva) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 phone routing decisions

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Phone Validation & Routing Intelligence

Turn raw phone numbers into deterministic routing decisions using libphonenumber.

### Output

Each supplied phone number returns a dataset row containing:

- `ACCEPT / REVIEW / REJECT`;
- reason codes;
- E.164 normalization;
- validity and possibility;
- ISO country and calling code;
- line type;
- carrier metadata when available;
- location and timezone metadata;
- explicit `deliverable: null` and `ported: null` boundaries.

No LLM is used. This Actor does not claim live reachability, current carrier after portability, or porting status.

### Inputs

Use exactly one of:

- `phone` for one number;
- `phones` for a JSON batch;
- `csv` for CSV text containing a phone column.

Optional policy fields:

- `default_region`;
- `expected_country`;
- `allowed_line_types`;
- `phone_column` for CSV.

### Decision contract

- **REJECT** — unparsable, impossible/invalid, or excluded line type.
- **REVIEW** — valid but inconsistent with `expected_country`.
- **ACCEPT** — valid and all supplied routing policies pass.

### Pricing

Pay per event: **$0.001 per phone routing decision**.

The decision itself is the product, so valid and rejected numbers are both billable when processed.

### Integrity boundary

`deliverable` and `ported` intentionally remain `null`. Carrier metadata comes from numbering-plan metadata and is not guaranteed to represent the current carrier after number portability.

# Actor input Schema

## `phone` (type: `string`):

Single phone number in E.164 or national format. Use this OR phones OR csv.

## `phones` (type: `array`):

Batch JSON input. Use this OR phone OR csv.

## `csv` (type: `string`):

CSV content containing a phone column. Use this OR phone OR phones.

## `phone_column` (type: `string`):

Column containing phone numbers when csv input is used.

## `default_region` (type: `string`):

ISO 3166-1 alpha-2 region used when a number has no country code. Example: US.

## `expected_country` (type: `string`):

Optional ISO alpha-2 policy country. A valid number from another country returns REVIEW.

## `allowed_line_types` (type: `array`):

Optional routing policy. A valid number with another line type returns REJECT.

## Actor input object example

```json
{
  "phone_column": "phone"
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("tryva/phone-validation-routing-intelligence").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("tryva/phone-validation-routing-intelligence").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 '{}' |
apify call tryva/phone-validation-routing-intelligence --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tryva/phone-validation-routing-intelligence"
        }
    }
}

```

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/XtFCQuaJM6cMHa2Th/builds/Fci5ttLWG4cqljtN8/openapi.json