Area code & phone number API

A free, no-key JSON API for North American (NANP) area codes and phone numbers — region, cities, time zone, carrier, overlays, and scam/spoofing context. Sourced from the official NANPA database; built for developers and AI agents.

Quick start

Base URL https://areacode.fyi/api/v1 — no key, CORS-enabled.

curl https://areacode.fyi/api/v1/area-code/702

Endpoints

  • GET /api/v1/area-code/{npa} — region, cities, time zone, overlays, carrier summary. example
  • GET /api/v1/phone/{number} — parse & validate a NANP number. example
  • GET /api/v1/carrier/{number} — assigned carrier & line type (block allocation, not live). example
  • GET /api/v1/area-codes?city= or ?state= — codes for a city or state. example
  • GET /api/v1/scam/{npa}, /explain/{topic}, /reputation/{number}

Every response includes source, canonical_url, and data_date. Area-code-level reference only — not caller identity or live carrier.

MCP server for AI agents

Frequently asked questions

Is the areacode.fyi API free?

It's free with no API key for low-volume use. It serves North American (NANP) area-code and phone-number reference data — area code, region, cities, time zone, overlays, carrier/line type, and scam/spoofing context. For high-volume or commercial use, get in touch.

Do I need an API key?

No key is needed for normal, low-volume use, and the API is CORS-enabled. If you're planning high-volume traffic, contact us first — heavy use may move to a keyed, metered tier.

Where does the data come from and how fresh is it?

Directly from the official North American Numbering Plan Administrator (NANPA) database, refreshed monthly. Every response includes a source label, a canonical areacode.fyi URL, and the data_date so you can cite and verify it.

I want to use it at scale — what should I do?

Get in touch before sending high-volume traffic. Low-volume use is free; we host and maintain the API, so heavy or commercial integrations may need a metered plan. A link back via the canonical_url is appreciated. The API must not be used for FCRA-covered decisions (employment, tenant, credit) or to assert a specific number's identity.

Does the API return a caller's identity, location, or live carrier?

No. It's area-code-level reference and education. Carrier/line type comes from public NPA-NXX block allocations (not a live, porting-aware lookup), and caller ID can be spoofed, so a number never proves who is calling.

Sourced from the official NANPA (North American Numbering Plan Administrator) numbering database, current as of August 2, 2026. Refreshed monthly.