AgentPhone
AgentPhone is the telephony infrastructure layer for AI agents. A single REST API provisions real US/Canada phone numbers for agents with voice calling, SMS, MMS, and iMessage built in, plus unified webhooks, automatic conversation threading, real-time call transcription, hosted-LLM or webhook voice modes, and 10DLC/A2P compliance handled for you. Official Python and TypeScript SDKs and a published MCP server let agents buy numbers, place calls, and send messages through natural language. Founded 2026 (Y Combinator), used by teams at Google ADK, Replit, LangChain, Sim AI, and Alchemy.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles AgentPhone the way a machine reads it — 19 machine-readable artifacts across 13 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — AgentPhone scores 50.9/100 (developing), with a separate agent-readiness read of 90/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile AgentPhone
Each block below is one kind of artifact we hold for AgentPhone. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 13
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
AgentPhone agent-webhooks API
The agent-webhooks API from AgentPhone — 3 operation(s) for agent-webhooks.
AgentPhone agents API
The agents API from AgentPhone — 7 operation(s) for agents.
AgentPhone calls API
The calls API from AgentPhone — 8 operation(s) for calls.
AgentPhone contactCards API
The contactCards API from AgentPhone — 1 operation(s) for contactcards.
AgentPhone contacts API
The contacts API from AgentPhone — 3 operation(s) for contacts.
AgentPhone conversations API
The conversations API from AgentPhone — 5 operation(s) for conversations.
AgentPhone location API
The location API from AgentPhone — 2 operation(s) for location.
AgentPhone messages API
The messages API from AgentPhone — 2 operation(s) for messages.
AgentPhone numbers API
The numbers API from AgentPhone — 3 operation(s) for numbers.
AgentPhone registration API
The registration API from AgentPhone — 2 operation(s) for registration.
AgentPhone sub-accounts API
The sub-accounts API from AgentPhone — 2 operation(s) for sub-accounts.
AgentPhone usage API
The usage API from AgentPhone — 5 operation(s) for usage.
AgentPhone webhooks API
The webhooks API from AgentPhone — 5 operation(s) for webhooks.
Scroll within the panel for all 13 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
agentphone-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Agentphone Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
AgentPhone Webhooks
Event surface AgentPhone delivers to a project-level or per-agent webhook URL. Generated by the API Evangelist enrichment pipeline from the published webhook documentation (http...
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for AgentPhone — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/agentphone · machine-readable index on apis.io