Telcodata

Return the authenticated TelcoData account profile for the provided API key. Use this to confirm entitlement level, API access, expiration, and identity before explaining why a query or download may be unavailable.

Look up a single NANP NPA-NXX exchange/prefix. Use when the user has an area code plus exchange such as 425-555, or when deriving the prefix from a phone number is unnecessary. Set include_blocks=true when the user needs portability/pooling detail, the responsible carrier may vary by thousands digit, or the answer should show all block-level assignments. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.

Search TelcoData's tracked source-record changes in reverse chronological order. Use this for questions about when an NPA-NXX or thousands block changed carrier, OCN, CLLI/switch, assignment status, rate center, or another tracked field. Filters are combined, and omitting all filters returns the most recent changes. Initial baseline-load events are excluded. Multi-field record changes are returned together as structured old/new JSON values rather than one unrelated result per changed field. The clli filter matches switch-related changes and accepts a 6- to 11-character CLLI or prefix. Use field for a lowercase source field name, source for the tracked source name, and limit to cap results.

Look up one thousands block within an NPA-NXX. Use when the user gives the seventh digit of a NANP number, such as 425-555-4XXX, or asks who owns/routes a specific block. If no block row exists, the tool reports whether it used the -1 aggregate/default row. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.

Normalize a dialable telephone number to E.164 and identify country metadata. Prefer this whenever the user gives a full phone number. For NANP numbers, it returns the most specific TelcoData exchange or thousands-block record and shows whether the lookup used block detail or fallback. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.

List all exchanges/prefixes in a NANP area code. Use for area-code inventory, coverage, or 'what prefixes exist in 425' questions. Set include_blocks=true only when the user asks for every thousand block or pooling-level detail, because that can return many more rows. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.

Geocode a U.S. street address with TelcoData's local TIGER/Line database. For Canadian addresses, return the direct Natural Resources Canada Geolocator URL instead of proxying the Canadian query.

Search exchanges/prefixes for a rate center within a state, province, or NANP country code. Use for local-service geography questions such as 'prefixes in the Seattle rate center' or 'which exchanges are in Hamilton, BM'. Rate-center names are telecom rate-center labels, not always postal city names. Set include_blocks=true for pooling detail. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.

List newly assigned TelcoData exchanges for a date range. Use for recent numbering activity, new prefix reports, and state-filtered change monitoring. Defaults to the last 30 days when dates are omitted; pass explicit YYYY-MM-DD dates when the user gives a period. Results are exchange-level additions, not live telephone-number assignment events.

Look up a 4-digit Carrier Identification Code (CIC/PIC) record. Use for questions about long-distance carrier selection codes, 1010 dialing, or mapping a CIC to carrier/ACNA data.

Look up CIC rows by 3-letter Access Customer Name Abbreviation (ACNA). Use when the user has an ACNA and wants associated carrier identification codes or carrier names.

Fetch carrier profile details for a 4-character Operating Company Number (OCN). Use when the user asks who an OCN belongs to, wants carrier type/country, or needs FCC FRN/RMD and Canadian registration/contact fields tied to that carrier.

List carrier profiles sharing an FCC Robocall Mitigation Database filing ID. Use to connect multiple OCNs or brands to the same RMD filing/contact when investigating carrier identity, voice providers, or robocall-mitigation relationships.

List carrier profiles sharing an FCC Registration Number (FRN). Use to group related OCNs, carrier names, and RMD records under a common FCC registration.

List NPA-NXX prefixes assigned to an Operating Company Number (OCN). Use when the user asks where a carrier operates, what prefixes belong to a carrier, or wants to pivot from an OCN profile into numbering footprint. Combine with get_ocn_profile for carrier identity fields. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.

List prefixes routed via a tandem switch CLLI. Use for routing and interconnection questions, or when the user has a tandem CLLI and wants all served prefixes. The input may be a 6- to 11-character CLLI prefix; broader prefixes can return more rows. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.

List prefixes in a Local Access and Transport Area (LATA). Use for regional telecom market/routing questions such as all prefixes in a LATA. LATAs are telecom routing/market areas and do not necessarily match states, cities, or area codes. TelcoData fields commonly include npa, exchange/NXX, thousands, state, country, ratecenter, company, ocn, lata, switch CLLI, and tandem CLLI. A thousands value of -1 represents the whole prefix/default aggregate; 0-9 are individual thousand-number pooling blocks.

List NANP area codes for a state, province, or supported NANP country/territory code. Use for quick geography-to-NPA mapping before deeper area-code or rate-center queries.

Fetch central-office/switch detail for one 11-character CLLI code. Use when the user asks about a switch, wire center, location, equipment/switch type, LATA, tandem, point code, or English name tied to a CLLI. The officetype field contains space-separated raw NECA Tariff 4 office-capability codes; it is not the equipment model in switchtype. For prefixes served by a switch, start with get_exchange or related prefix-listing tools.

List paid downloadable TelcoData datasets visible to the authenticated user, including entitlement/access flags. Use when the user asks what bulk data files, CSVs, database dumps, or paid downloads their account can access.

Fetch metadata for a specific paid download without transferring file contents. Use after list_downloads when the user asks about one dataset's suggested filename, access level, availability, file existence, or last-updated time.