Carrier Lookup API

What does the Carrier Lookup API return for a phone number?

The /lookup endpoint returns the carrier name (Verizon, AT&T, T-Mobile, etc.), the line type (mobile, landline, VoIP), a validity flag indicating whether the number is well-formed, and an active flag indicating whether the line is in service. This combination supports both routing and fraud-screening use cases.

Does Carrier Lookup work for non-US phone numbers?

The API is documented as a US phone number lookup service. Coverage outside the US is not part of the OpenAPI surface; for international validation pair Carrier Lookup with another provider that covers your target geographies.

Can I use Carrier Lookup to detect VoIP numbers?

Yes. The line_type field returned by GET /lookup will indicate `voip` for VoIP numbers, `mobile` for cellular, and `landline` for fixed lines. This is the standard signal used by signup-fraud screens to filter out disposable or virtual numbers.

What are the rate limits for the Carrier Lookup API?

The OpenAPI specification does not declare numeric rate limits. Limits are tied to the plan associated with your API key - keep concurrent requests modest and back off on 429 responses. Refer to https://www.carrierlookup.com/carrier-lookup-api-integration/ for plan tiers and quotas.

How do I look up a number through Jentic?

Run `pip install jentic`, then use Jentic's search to find the lookup operation with the query "look up phone carrier", load the schema, and execute with `{"number": "4155551234"}`. Jentic calls GET /lookup with your API key from the vault and returns carrier, line_type, valid, and active fields.

Can I batch-process a list of phone numbers?

The API exposes a single GET /lookup endpoint that takes one number per call. To process a list, iterate sequentially or in modest concurrency from your application; the API does not provide a built-in bulk endpoint, so batching is the caller's responsibility.

Can I limit what my agent is allowed to do with the Carrier Lookup API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. The Carrier Lookup API exposes a single operation, GET /lookup, so you scope by operation: grant the agent only the carrier lookup it needs, and it can do nothing beyond that one call. Your API key stays with your Jentic One instance and is injected into the request at execution time rather than exposed to the agent.