AgentTech 360 is now generally available for FMOs and IMOs. Read the announcement

AgentTech MCP

Give your AI bots a real phone line

AgentTech MCP is available now. Insurance agencies connect Grok, Claude, ChatGPT, or a custom agent to the same carrier-grade, compliance-gated phone system their licensed agents already use. MCP or REST. One gateway.

Schedule demoSee the tools

Built on the phone platform 100+ agencies use every day.

Animated product demo of an AI bot connecting over MCP, listing tools, answering an inbound call, screening a Medicare caller, and warm-transferring to a licensed agent.

MCP tools/list

  • answer_call calls
  • say / listen screening
  • transfer warm

Logged to the agency call log

Works with the AI you already use

Any MCP client. No new bot platform.

Connect the agent your agency already runs. AgentTech MCP speaks the MCP streamable HTTP protocol dated 2025-11-25, and the same gateway accepts REST on /v1. Names below are client types, not endorsements.

  • Grok
  • Claude
  • ChatGPT
  • Custom agents
  • Any MCP client

How it works

From Agency Settings to a live number

  1. Step 1

    Enable it

    Turn on AgentTech MCP in Agency Settings. It uses the phone system the agency already runs.

  2. Step 2

    Mint a scoped key

    Create an atk_live_ or atk_test_ key. It is shown once, stored hashed, and you can revoke it. Scopes are account, billing, numbers, calls, and recordings.

  3. Step 3

    Connect the bot

    Point an MCP client at the streamable HTTP gateway, or call the same gateway over REST /v1. Both use a Bearer key.

  4. Step 4

    Take calls

    Buy or assign a number, set who answers, and let the bot place or receive calls inside the guardrails.

Capabilities

The tools a bot can call

Each card opens the tool list. Paid actions refuse to run until the bot sends confirm: true.

Same call, two interfaces

place_call over MCP or REST

Paid calls do not leave the gateway unless confirm is true. Outbound also needs a purpose and a consent_ref. The host below is a placeholder. Do not treat the path as a published hostname.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "place_call",
    "arguments": {
      "to": "+16025550100",
      "confirm": true,
      "purpose": "Appointment reminder",
      "consent_ref": "consent_example"
    }
  }
}
curl -s https://YOUR-AGENTTECH-HOST/v1/place_call \
  -H "Authorization: Bearer atk_test_..." \
  -H "Content-Type: application/json" \
  -d '{"to":"+16025550100","confirm":true,"purpose":"Appointment reminder","consent_ref":"consent_example"}'

Sample only. Authorization is Bearer atk_test_... or atk_live_.... The key is shown once in Agency Settings. This page does not call a live gateway.

Insurance use cases

What an agency bot can do on a real line

Inbound

An AI receptionist on the agency's numbers

Point a number at a live agent, a webhook, voicemail, a Dialer AI agent, a relay, or a forward with set_inbound_handler. The bot can answer_call, say, and listen, then hand the caller to a person.

set_inbound_handlerDialer AI agent
answer_callLive
say / listenScreen

Transfer

A qualifier that warm-transfers to a licensed agent

The bot can ask the screening questions your agency already uses, then transfer the call warm or blind. conference_add_human brings a person onto the call. The bot does not enroll, quote, or bind a plan.

listenAge, ZIP, coverage
transferWarm
conference_add_humanLicensed agent

Coverage

After-hours answering without a new phone system

When the floor is closed, set_inbound_handler can send the number to voicemail, a webhook, or a Dialer AI agent. The bot can take a message and the call still lands in the agency call log.

set_inbound_handlerVoicemail
sayAfter-hours greeting
get_callCall log

Outbound

Consented callbacks inside calling hours

place_call requires confirm: true, a purpose, and a consent_ref. The gateway checks Dialer contact policy for AI voice: prior express written consent, seller match, jurisdiction, and federal calling hours. If a check fails, the call does not go out.

purposeRequired
consent_refRequired
confirmtrue

Security and compliance

The bot inherits the agency's phone rules

Keys are Bearer tokens minted in Agency Settings. atk_live_ and atk_test_ are shown once, stored hashed, and revocable. Scopes are account, billing, numbers, calls, and recordings. This is not an OAuth sign-in, and the API does not add credits.

Security overviewCompliance for carriers
Paid actions need confirm: truebuy_number, release_number, and place_call refuse to run without it.
Limits on the keyPer-key rate limit, max concurrent calls, daily spend cap, and a number cap. The page does not publish the cap amounts.
Outbound consent, or no callpurpose and consent_ref are required. Dialer contact policy checks prior express written consent, seller match, jurisdiction, and federal calling hours. A failed check stops the call.
Blocked destinations911 and N11, 900 and 976, short codes, and international numbers are blocked. There is no international calling on this gateway.
Spoken disclosureOutbound AI says: This is an AI assistant calling on behalf of {business}. This call is recorded.
Every call is loggedThe call is written to the agency call log and attributed to the key that placed or answered it.

FAQ

Auth, scopes, and how this sits next to the Dialer

How does a bot authenticate?

With a Bearer API key minted in Agency Settings. Keys use the prefixes atk_live_ and atk_test_. The full key is shown once, stored hashed, and can be revoked. AgentTech MCP does not use OAuth sign-in for this gateway.

What scopes can a key have?

account, billing, numbers, calls, and recordings. Give the bot only the scopes that job needs. Billing scope does not add credits through the API.

What does confirm: true do?

buy_number, release_number, and place_call are paid actions. They do not run unless the request includes confirm: true. Other tools in the list do not use that flag.

What will the gateway refuse?

Calls to 911 and N11, 900 and 976 numbers, short codes, and international destinations. Outbound calls without a purpose and a consent_ref are refused. So are calls that fail Dialer contact policy for AI voice: prior express written consent, seller match, jurisdiction, or federal calling hours. Those checks fail closed.

How does AgentTech MCP relate to the Dialer?

It is the agency's phone infrastructure, opened to the agency's own AI bots over MCP or REST /v1. Numbers, handlers, consent, and the call log stay in the Dialer. A licensed agent still takes the warm transfer. The public marketing discovery endpoint at /mcp is a different service and is not this gateway.

See it on your numbers

Put your AI bot on a real AgentTech line

Schedule demoSee the tools

Numbers

Search, buy, list, and release numbers on the agency account, then decide what answers each one.

search_numbers
Look for numbers the agency can buy.
buy_number
A paid action. It runs only when confirm is true.
release_number
A paid action. It also requires confirm: true.
list_numbers
Read the numbers already on the account.
set_inbound_handler
Send inbound calls to a live agent, a webhook, voicemail, a Dialer AI agent, a relay, or a forward.
Schedule demo

Outbound calls

place_call is a paid action. The gateway will not dial unless confirm is true, and the request includes a purpose and a consent_ref.

place_call
Start an outbound call from a number the agency owns.
confirm
Must be true or the paid call does not run.
purpose
Required. Say why the bot is calling.
consent_ref
Required. Points at the consent record the Dialer policy will check.
Schedule demo

Inbound calls

A number can ring a bot, a person, or a handler you set. The bot accepts or declines the live call.

answer_call
Pick up an inbound call that is ringing the bot.
decline_call
Refuse the ringing call.
set_inbound_handler
Choose a live agent, webhook, voicemail, Dialer AI agent, relay, or forward.
Schedule demo

Speak and listen

Once the call is up, the bot can talk, hear the caller, and send keypad tones. This is not a raw audio stream.

say
Speak a prompt on the live call.
listen
Capture what the caller says so the bot can respond.
send_dtmf
Send touch tones, for an IVR or a carrier menu.
Schedule demo

Call control

Hold the line, bring a licensed person in, or end the call. Warm and blind transfers are both available.

hold
Place the caller on hold.
resume
Take the caller off hold.
transfer
Blind or warm transfer to another party.
conference_add_human
Add a person to the live call.
hangup
End the call.
get_call
Read the current call.
Schedule demo

Transcripts and recordings

Read the transcript and fetch the recording after the conversation. The gateway does not offer raw audio streaming.

get_transcript
Read what was said on the call.
get_recording
Fetch the stored recording for that call.
get_call
Read call details, including how the key was attributed in the agency call log.
Schedule demo

Events and webhooks

The bot can hear call progress three ways. All three come from the same gateway.

GET /v1/events
A server-sent event stream of gateway events.
MCP listen
Listen for events on the MCP session.
HTTPS webhooks
Deliver events to your URL. The webhook uses an HMAC secret.
Schedule demo

Guardrails

The bot does not get a quieter set of rules than a person on the Dialer. Failed checks stop the action.

confirm: true
Required for buy_number, release_number, and place_call.
Key limits
Per-key rate limit, max concurrent calls, daily spend cap, and a number cap.
Consent
Outbound needs purpose and consent_ref, then Dialer contact policy: prior express written consent, seller match, jurisdiction, and federal calling hours.
Blocked destinations
911 and N11, 900 and 976, short codes, and international.
Disclosure
Outbound AI says: This is an AI assistant calling on behalf of {business}. This call is recorded.
Call log
Every call is stored on the agency call log and attributed to the key.
Schedule demo Learn more