
CallerAPI
When a customer provides a phone number, your AI agent instantly verifies it through CallerAPI. Spam scores, carrier details, FTC complaint history, and HLR network status are all retrieved in seconds. Fraudulent numbers get flagged before a single callback is made. Your sales team only calls verified, real leads.




Your AI agent taps into CallerAPI's phone number database to verify callers, detect fraud, and enrich contact records, all during live conversations with your customers.
CallerAPI
See how AI agents protect your team from spam, verify leads before callbacks, and keep contact databases clean using real-time phone intelligence.
A demo request comes in at midnight from an unfamiliar area code. Your AI Agent takes the submitted phone number, runs it through CallerAPI with HLR enabled, and discovers it has a high spam score with multiple FTC complaints. Instead of wasting a rep's morning on a fraudulent lead, the agent flags it and moves to the next qualified prospect. Your team calls real buyers first.
A caller requests an account password reset and provides a phone number for verification. Your AI Agent queries CallerAPI before sending any codes, finds the number is classified as VoIP with recent spam reports, and escalates to your fraud team instead of completing the reset. Account takeover prevented. Customer data stays safe.
Your marketing team is about to send 10,000 promotional texts. Your AI Agent processes each number through CallerAPI with HLR lookup, identifies 1,200 disconnected or ported numbers, and removes them from the campaign list automatically. Bounce rates drop. Carrier reputation stays intact. Campaign delivery improves across the board.

CallerAPI
FAQs
The agent calls CallerAPI's Get Phone Number Information endpoint and receives reputation score, entity type (business or personal), carrier name, line type (mobile, landline, VoIP), spam status, and FTC complaint count. With HLR enabled, it also returns real-time network status showing whether the line is active or disconnected.
Standard lookups return in under a second. With HLR enabled for real-time network status, the response takes 1-3 additional seconds. Both are fast enough that your customer will not notice any delay while the agent verifies their number in the background.
Yes. CallerAPI requires E.164 format, which includes the country code prefix (for example, +16502530000 for a US number). Your AI agent can automatically convert common phone number formats to E.164 before making the lookup call.
Absolutely. Configure your agent with rules like 'if spam score exceeds 7, flag the lead for review' or 'if FTC complaints exceed 3, block the callback request.' The agent applies these rules in real time as CallerAPI returns data during conversations.
CallerAPI pricing starts at $0.0039 per lookup, with plans ranging from 5,000 lookups at $25 to 250,000 lookups at $997. The agent can check your remaining credit balance by calling the Get User Information endpoint so you are never surprised by usage.
No. Tars queries CallerAPI in real time during conversations. Reputation scores, carrier details, and complaint records are used only to process the current request. No phone intelligence data is retained in Tars after the conversation ends.
Manual lookups require you to visit the CallerAPI dashboard and enter each number one at a time. With Tars, verification happens automatically as customers provide numbers during conversations. Batch processing, automatic fraud flagging, and instant lead scoring all run without human intervention.
Yes. Regardless of the channel, whenever a customer provides a phone number, the agent can verify it through CallerAPI. Website chat, WhatsApp, SMS, or any other Tars-supported channel, the same phone intelligence is available everywhere your agent operates.
Don't limit your AI Agent to basic conversations. Watch how to configure and add powerful tools making your agent smarter and more functional.

Privacy & Security
At Tars, we take privacy and security very seriously. We are compliant with GDPR, ISO, SOC 2, and HIPAA.