Skip to content

Give AI voice agents live data checks before and during calls

Screen numbers before the agent dials, look up facts mid-call and transcribe the result. Connect the MCP server or call the REST API from your tool layer.

What you end up with
  • The agent dials fewer dead or excluded numbers, so call time goes to real conversations.
  • Spoken details such as emails get validated while the caller is still on the line.
  • Each call leaves a transcript and a record of the lookups behind the agent's answers for review.
[01/Pipeline]

The steps, in order

  1. 1

    Connect your agent to the data

    Add the MCP server at https://mcp.1lookup.dev/mcp to MCP clients such as Claude, ChatGPT and Cursor. It exposes eight tools, including run_lookup, which runs any product by slug. A voice platform that lacks MCP support can call POST https://api.1lookup.dev/v1/{product-slug} from its tool or webhook layer.

    Your system
  2. 2

    Screen the number before dialing

    Have the orchestration layer send each number to DNC Scrub for registry status, the known-litigator flag and line type before the agent places the call. Skip anything your rules exclude.

    DNC Scrub10 cr
  3. 3

    Confirm line type and reachability

    Send the number to Phone Validation to confirm it is valid and note the line type. For mobiles, add HLR Lookup so the agent does not spend a call on a dead line.

    Phone Validation1 cr
  4. 4

    Look up facts during the call

    Give the agent a tool for mid-call questions. A caller who names their business can be checked with Business Lookup for address, hours and category, and a spoken email can be tested with Email Validation before the agent reads it back.

    Business Lookup10 cr
  5. 5

    Transcribe and review

    Send the call recording URL to Audio Transcription with speaker labels on. Store the transcript with the lookup results used during the call, so reviewers can see what the agent knew and when.

    Audio Transcription6 cr / minute
[03/FAQ]

AI voice agents: common questions

What does the MCP server give an AI voice agent?

It exposes eight tools at https://mcp.1lookup.dev/mcp, including run_lookup, which runs any product by slug. An agent platform that supports MCP can call lookups without custom glue code, and the REST API covers platforms that do not.

Do AI voice calls follow the same calling rules?

Often more strictly. The FCC has said calls that use AI-generated voices fall under the TCPA's artificial or prerecorded voice rules, so consent matters even more. Registry and line-type checks are inputs only. This is not legal advice.

Can a lookup run fast enough for a live call?

Single lookups are synchronous API calls, and results cached within 7 days return without a new charge. Run screening checks before dialing and keep mid-call lookups to a small number of fields the agent really needs.

How is usage billed?

Each product has its own price in credits, drawn from one balance whether the call arrives through MCP or REST. Requests that fail on our side are never charged. Every account is on a monthly plan that includes credits, starting at $29 a month for 6,000 credits, with pay as you go beyond the plan.

[ Validate ][ Enrich ]
[Get started]

Run your first lookup in two minutes

Create a key, pick a plan and call any product in the catalog. Plans start at $29 a month.

[ Screen ][ Scrape ]