Phone OSINT Lookup API — Carrier & Public Footprint

Operations teams, support teams, and AI agents can turn exact phone inputs into one structured dataset record per number. Each result provides E.164 formatting, country and line metadata, optional carrier data, public-web search links, source labels, warnings, and collection time for consented phone-data workflows.

Best fit and focused standalone workflow

This Actor is designed as a focused standalone workflow for teams that already hold authorized phone numbers. It works well for CRM cleanup, telecom routing research, and support-case preparation where the next decision needs a normalized number, numbering-plan metadata, carrier context, and manual public-web search starting points.

For business, profile, review, or location discovery, start with a dedicated source Actor that collects authorized public records, then pass the exact phone field to this Actor for phone metadata. The result remains a focused standalone workflow when a CRM or support queue already supplies the phone field.

Workflow story

A support-operations analyst starts with a customer phone field, runs this Actor to standardize it to E.164, confirms the country and line type, and checks the carrier source when available. Next, the analyst opens the supplied public-web links for a manual, context-aware review and exports the dataset row back to the authorized support record.

Input

{
  "phoneNumbers": ["+12025551234", "(202) 555-1234"],
  "defaultCountry": "US",
  "maxLookups": 10,
  "includeCarrierLookup": true,
  "includeFootprintLinks": true
}

Use E.164 where possible. Local numbers use defaultCountry; duplicate input values are processed once. maxLookups accepts 1 through 100 and provides the run's event-charge cap.

Output

Each dataset row uses stable typed fields:

Field	Meaning
e164	Normalized E.164 phone value for consistent downstream matching.
countryCode, countryName, region, city	Numbering-plan geography when supplied by the metadata source.
lineType, carrier, carrierSource	Number-plan line category and optional carrier provenance.
footprintSearchUrls	Manual public-web search starting points; linked pages remain user-reviewed.
sources, warnings, lookedUpAt	Provenance, data-quality context, and collection time.

{
  "inputNumber": "+12025551234",
  "valid": true,
  "possible": true,
  "e164": "+12025551234",
  "international": "+1 202 555 1234",
  "countryCode": "US",
  "countryName": "United States",
  "region": "DC",
  "city": "Washington",
  "lineType": "fixed_or_mobile",
  "carrier": null,
  "carrierSource": null,
  "footprintSearchUrls": {
    "exactNumberWebSearch": "https://www.google.com/search?q=%22%2B12025551234%22",
    "callerReputationSearch": "https://www.google.com/search?q=%22%2B12025551234%22+caller+reputation",
    "businessDirectorySearch": "https://www.google.com/search?q=12025551234+business+directory"
  },
  "footprintScope": "manual_public_web_search_links",
  "sources": ["libphonenumber", "manual_public_web_search_links"],
  "warnings": [],
  "lookedUpAt": "2026-08-30T00:00:00.000Z"
}

Pricing

The Actor uses Pay per event + platform usage. Actor start costs $0.00005, and each valid complete phone-metadata record costs $0.025; Apify reports platform usage separately. For a 10-phone maximum, event charges are capped at $0.250 plus platform usage. Open the live Pricing tab for the current Actor pricing and platform-usage details.

API and agent use

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('khadinakbar/phone-osint-lookup-api').call({
  phoneNumbers: ['+12025551234'],
  includeCarrierLookup: true,
  includeFootprintLinks: true
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

As an AI agent, normalize these exact authorized phone numbers, return country and line metadata, include carrier provenance when available, and provide manual public-footprint links. Read the output dataset in pages, retain sources and lookedUpAt as provenance, and report the terminal OUTPUT.outcome with the scoped event cost.

OUTPUT supplies the terminal outcome and charge counts. RUN_SUMMARY supplies input totals, deduplication, provider status, warnings, and final record counts. Read the default dataset in pages for large batches.

Best results and practical guidance

Provide exact authorized phone values and select the country that matches local-format inputs. Confirm carrierSource before making a routing decision, and treat carrier values as point-in-time telecom metadata. Public-footprint links support an authorized human review with the relevant customer, business, or support context.

Builder's note

I designed this Actor around one reliable record contract: offline number-plan metadata always remains available, optional carrier enrichment is labeled with its provider, and public-footprint links stay manual. My goal was a predictable AI-agent surface that preserves useful telecom context alongside clear source and collection-time fields.

Responsible use

Submit phone numbers you are authorized to process and use the public-web links in accordance with applicable laws, privacy duties, telecom rules, and site terms. Carrier and numbering-plan signals support context-aware operations decisions.