AgentPhone
What is AgentPhone?
AgentPhone is a phone infrastructure platform for AI teams that routes calls and texts through one webhook so agents can handle both channels in the same event shape. It includes Get a number, One webhook, Real-time transcription, and Native MCP support, and it's shown in use by Google, LangChain, and Replit. Plans run Usage Based at $3/per number/month, Pro at $150/per number/month, and Enterprise custom.
Last verifiedHow we evaluate
At a glance
- AgentPhone is best for AI teams who need one phone number workflow for calls, texts, and agent replies.
- Usage Based $3/per number/mo; Pro $150/per number/mo; Enterprise Custom
What does AgentPhone do?
AgentPhone routes calls and texts for AI agents through a single webhook, so one handler can receive both channels in the same event shape. Its flow is built around getting a number, then letting the agent reply with text while AgentPhone handles the speech layer for voice calls. The product also exposes real-time transcription and native MCP support, which lets agentic tools provision numbers, send messages, and handle calls through tool use instead of custom telecom glue. The site says it provisions US and Canadian numbers instantly, with one API call and one API for the whole flow. It's backed by Y Combinator and shown in use by teams like Google, LangChain, Replit, and alchemy. The public docs also frame it for autonomous workflows such as receptionists, AI workers, on-call engineering, and coding agents, while keeping the integration surface centered on SDKs, REST, and MCP rather than a broad telecom stack.
Why use AgentPhone?
- One webhook format covers both voice and messaging, which reduces routing logic and keeps agent handling consistent.
- Native MCP support lets compatible agents use phone capabilities directly instead of wiring custom telecom actions.
- Real-time transcription turns incoming calls into text before your agent responds, simplifying voice workflows.
- The product is built around one API and one handler, which lowers integration overhead for agent systems.
- Instant US and Canadian number provisioning helps teams start without telecom setup delays.
Who is AgentPhone for?
- AI product teams who need a phone number layer for autonomous voice and messaging workflows.
- Developers building coding agents who want native MCP-based provisioning and message handling.
- Operations teams who need a single webhook for call and text events without separate pipelines.
- Support or receptionist automation teams who need real-time transcription and text-based replies.
- On-call engineering teams who want agents to receive and respond to phone-based alerts.
What are AgentPhone's key features?
Get a number
Provision US and Canadian numbers for AI agents, with voice calls, SMS, and auto-recharge so teams can start handling traffic without manual carrier setup.
One webhook
Route calls and messages through one unified webhook format, so your backend handles events with one handler instead of maintaining separate phone workflows.
Real-time transcription
Receive real-time transcription from live calls, giving agents and operators immediate text output for logging, routing, and follow-up actions.
Native MCP support
Connect phone workflows through native MCP support, letting agent tools and runtimes share one API call path for voice and messaging automation.
Ways to integrate
Plug AgentPhone into Claude, OpenAI, Cursor, Cline, Windsurf, Zed, Claude Code, OpenClaw, Hermes, GitHub, or Stripe for agent-driven phone actions.
Sales / lead follow-up
Use one phone number for sales and lead follow-up, with voice calls, SMS messages, and transcription to capture responses and trigger next steps.
2FA and verification inbox
Handle verification texts in a dedicated inbox, keeping 2FA codes and account checks organized alongside SMS delivery on one number.
What does AgentPhone integrate with?
- Claude
- OpenAI
- Cursor
- Cline
- Windsurf
- Zed
- Claude Code
- OpenClaw
- Hermes
- GitHub
- Stripe
What are AgentPhone's use cases?
AI product teams provision numbers
AI product teams who need a phone number layer for autonomous voice and messaging workflows use AgentPhone to get a live number fast, then route calls and texts through One webhook. They can keep agent behavior centralized while using Real-time transcription to turn conversations into actionable outputs.
Coding agents handle phone events
Developers building coding agents use AgentPhone to provision numbers through Native MCP support and connect them to Claude Code, Cursor, or Cline. That lets an agent receive phone-based events, respond programmatically, and keep provisioning inside the same workflow instead of stitching together separate telephony tools.
Support teams reply from transcripts
Support or receptionist automation teams use AgentPhone to answer incoming calls, capture the conversation with Real-time transcription, and send text-based replies from the same flow. With One webhook, they can keep call and SMS events in a single pipeline and reduce missed handoffs.
On-call alerts to phone agents
On-call engineering teams use AgentPhone to let agents receive and respond to phone-based alerts without building a separate phone stack. They can Get a number for the alert line, then use One webhook to unify call and text handling when incidents need immediate acknowledgment.
How does AgentPhone work?
- Get a number for your agent and choose the voice or messaging setup you need. Start with the first live line, then keep provisioning simple as you scale additional numbers.
- Connect One webhook so call and text events land in a single handler. Use the unified event format to route replies, status changes, and handoffs without separate pipelines.
- Turn on Real-time transcription to capture live conversations as they happen. Feed transcripts into your agent logic so support, sales, or alert workflows can react immediately.
- Use Native MCP support or Ways to integrate to connect AgentPhone with Claude, OpenAI, Cursor, GitHub, and Stripe. Keep your agent workflow inside the tools your team already uses.
- Expand into Sales / lead follow-up or 2FA and verification inbox flows as needed. Monitor activity, refine prompts, and keep one phone layer powering ongoing agent operations.
How much does AgentPhone cost?
Usage Based
$3/per number/month- Voice + Messages Enabled
- Auto-recharge with card on file
- Up to 10 numbers self-serve
- No minimum commitment
- Voice calls
- SMS messages
- Real-time transcription
- Native MCP support
- Auto-recharge with card
- Standard email support
Pro
$150/per number/month- Everything in Usage Based
- IMessage-enabled number
- No per-message costs
- RCS fallback included
- Priority support
- Voice calls
- SMS messages
- Real-time transcription
- Native MCP support
- Numbers self-serve
- Auto-recharge with card
- Standard email support
- Dedicated account manager
- Uptime SLA
Enterprise
Custom- White-glove onboarding
- Dedicated account manager
- SLA & uptime guarantees
- Custom integrations for your team
Frequently asked questions
What is AgentPhone?
AgentPhone is a phone infrastructure platform for AI teams that routes calls and texts through one webhook so agents can handle both channels in the same event shape. It includes Get a number, One webhook, Real-time transcription, and Native MCP support, and it's shown in use by Google, LangChain, and Replit. Plans run Usage Based at $3/per number/month, Pro at $150/per number/month, and Enterprise custom.
How much does AgentPhone cost? Is it free?
AgentPhone has 3 paid plans: Usage Based at $3/per number/month, Pro at $150/per number/month, Enterprise at Custom.
What is AgentPhone used for? Who is it for?
AgentPhone is used for Get a number, One webhook, and Real-time transcription. It's built for AI product teams, Developers building coding agents, and Operations teams.
Does AgentPhone have an API and what does it integrate with?
AgentPhone doesn't publish a public API. It integrates with Claude, OpenAI, Cursor, Cline, Windsurf, and 6 more.
Editor's read
Check whether your workflow needs iMessage-enabled numbers or no per-message costs, since those are included only on Pro. If you expect to stay on Usage Based, verify that the standard email support and self-serve number cap of up to 10 numbers are enough for your rollout.
