Live Phone Validator & Carrier Intelligence — Portability + Reachability

Stop treating “valid” as “reachable.”

Know if a phone number is structurally valid, which network serves it now, whether it has been ported, and whether the mobile network is currently reachable — then get an explainable ACCEPT / REVIEW / REJECT decision.

No upstream telecom API key is required from marketplace users.

One request

{
  "phone": "+14155552671",
  "expected_country": "US",
  "live": true,
  "require_reachable": true
}

One decision-ready response

{
  "static": {
    "valid": true,
    "possible": true,
    "e164": "+14155552671",
    "country": "US",
    "line_type": "fixed_or_mobile"
  },
  "live": {
    "evidence_status": "ok",
    "current_carrier": "Example Mobile",
    "current_network_code": "310260",
    "ported": false,
    "network_reachability": "reachable",
    "reachability_scope": "mobile_network",
    "observed_at": "2026-09-06T16:03:10.000Z"
  },
  "decision": "ACCEPT",
  "reason_codes": ["VALID_POLICY_MATCH"]
}

Carrier/network values above are illustrative.

Why not a normal phone validator?

Offline validators such as libphonenumber are excellent for:

• parsing
• E.164 formatting
• possible/valid checks
• country
• line type
• numbering-plan metadata

But numbering-plan carrier metadata is not the same thing as the carrier serving a ported number today.

This product adds live HLR/MNP evidence after the static precheck:

phone
  ↓
libphonenumber
  ↓
valid + normalized + line type
  ↓
live telecom evidence
  ↓
current network + ported + reachability
  ↓
policy
  ↓
ACCEPT / REVIEW / REJECT

What you get

Signal	Meaning
e164	Normalized international number
valid	Numbering-plan validity
possible	Length/structure plausibility
country	Parsed country/region
line_type	Mobile, landline, VoIP, etc. when detectable
carrier_metadata	Offline numbering-plan carrier metadata
current_carrier	Current serving carrier/network when live evidence is available
current_network_code	MCC/MNC-style network identifier when available
ported	Explicit portability status when available
network_reachability	Reachable / unreachable / unknown
observed_at	Timestamp for live evidence
evidence_status	Whether live evidence was successfully obtained
decision	ACCEPT / REVIEW / REJECT
reason_codes	Explainable reasons behind the decision

Built for real workflows

Lead validation & CRM hygiene

Normalize incoming numbers, reject structurally bad data, and flag records whose live telecom evidence requires review.

SMS / voice routing

Use current network and reachability evidence before spending on downstream messaging or calling.

Signup & onboarding

Apply country, line-type, portability, and reachability policies without inventing your own telecom logic.

Automation & AI agents

Give workflows a structured result plus a deterministic decision instead of asking an agent to interpret raw HLR/MNP payloads.

Batch enrichment

Analyze up to 100 numbers per request using the same response contract as single-number lookups.

Static vs live

Static preflight

live: false

Uses libphonenumber only.

Best for:

• normalization;
• format/validity checks;
• country;
• line type;
• inexpensive pre-filtering.

On Apify, static requests do not trigger the custom live-phone-intelligence event.

Live intelligence

live: true

Adds:

• current carrier/network;
• portability evidence;
• network reachability;
• observation timestamp.

Use live mode only when the workflow actually needs current telecom evidence.

Optional decision policies

Require a country

{
  "phone": "+33612345678",
  "expected_country": "US"
}

Result: REVIEW with COUNTRY_MISMATCH.

Require network reachability

{
  "phone": "+14155552671",
  "live": true,
  "require_reachable": true
}

• reachable → policy can remain ACCEPT
• unreachable → REVIEW
• unknown → REVIEW

Review ported numbers

{
  "phone": "+14155552671",
  "live": true,
  "review_if_ported": true
}

A confirmed ported number becomes REVIEW with a reason code.

Important semantics

This API deliberately keeps these concepts separate:

valid
≠ active subscriber
≠ network reachable
≠ SMS deliverable
≠ call answered
≠ identity verified

We return unknown when the evidence does not support a definitive answer.

We do not claim that a reachable network guarantees SMS delivery, call answer, ownership, identity, or absence of fraud.

API

GET  /health

POST /v2/phone/intelligence

POST /v2/phone/intelligence/batch

FastAPI also exposes interactive OpenAPI documentation at /docs.

Pricing candidate

$0.05 per successful live phone-intelligence decision

The live event includes the premium telecom lookup and decision layer.

Static preflight remains a separate low-cost path and does not trigger the live custom event.

This is the validated launch price for the live intelligence event.

Release status

Private preview.

Verified today:

• deterministic V1/static layer;
• live HLR lookup;
• live MNP lookup;
• current-carrier/network evidence;
• explicit ported boolean;
• network reachability;
• full CI;
• private Apify build.

Marketplace publication remains blocked until upstream redistribution/resale rights for our normalized derived outputs are confirmed.