Veriphone returns the validity status, phone type (mobile, landline, VoIP, toll-free), carrier name, country name and code, and the number formatted in E.164 international standard. The agent presents this data conversationally or stores it directly in your systems.

Yes. Veriphone supports phone number validation for countries worldwide. The agent accepts numbers in any common format including local, E.164, and country-code prefixed variants. It identifies the country and applies region-specific validation rules automatically.

The get example endpoint generates properly formatted sample phone numbers for a specified country and line type. This is useful for testing input validation, building demo flows, or providing format hints to customers who need to enter their number in a specific format.

When Veriphone returns an invalid status, the agent informs the customer that the number could not be verified and asks for a corrected number. The specific reason for failure, such as wrong digit count or non-existent area code, helps guide the correction.

No. Tars sends the phone number to Veriphone's API and returns the validation result within the conversation. Phone numbers and their associated carrier and location data are not cached or stored on Tars servers.

You provide your Veriphone API key from your account dashboard. The key is passed as a query parameter with each request. No OAuth setup or multi-step authentication is needed.

Yes. Veriphone classifies every validated number by type: mobile, landline, VoIP, or toll-free. The agent uses this classification to determine the best communication channel. For example, it can automatically route SMS only to mobile numbers and suggest voice calls for landlines.

Regex validation only checks formatting patterns. Veriphone performs carrier-level lookups, confirming the number is assigned to a real telecom provider in the correct region. It catches numbers that look valid in format but do not actually exist or belong to a different country than claimed.