01
What is Dial?
Dial is a communications layer built for AI agents. It gives software a real phone-number identity and exposes calling and messaging capabilities without requiring the agent developer to assemble carrier infrastructure from scratch.
The current official product surface includes REST, a remote MCP server, a CLI, a Node SDK and a Python SDK. Dial is therefore best understood as the communications layer in an agent stack, not as the reasoning model or workflow engine itself.
02
What can an AI agent do with Dial?
- provision and manage real phone numbers
- place outbound AI voice calls
- receive inbound calls with an inbound instruction
- send and receive SMS
- receive asynchronous call and message events
- use WhatsApp when the account has beta access
These primitives fit workflows such as appointment confirmation, lead follow-up, inbound qualification, support triage and business notifications. Availability and compliance still depend on the exact destination, channel and use case.
03
CLI, MCP, REST and SDK access
The official CLI is the fastest documented onboarding path. Dial currently requires Node.js 22 or newer and documents installation with npm install -g @getdial/cli. New accounts verify both email and a phone number before onboarding completes.
MCP is useful when an agent should discover and invoke Dial tools directly. REST and the Node/Python SDKs are better fits when a backend owns authentication, durable state, audit controls or custom business logic.
04
Dial pricing and free-account limits
Dial currently advertises a $5 signup credit with no card required and pay-as-you-go number ownership at $3 per month per phone number plus metered usage. Voice and SMS usage rates vary by destination, so there is no single universal call or message rate to hard-code.
Free accounts that have not topped up or subscribed are currently limited to 5 minutes per call and 2 concurrent calls. Dial says those restrictions lift after the first top-up or subscription.
05
WhatsApp, iMessage and channel limits
Dial currently describes WhatsApp lines as beta and account-enabled rather than universally available. Treat channel access as an account capability that should be checked before a production workflow depends on it.
Dial's number-management documentation also gives iMessage numbers separate rules: they remain pay-as-you-go rather than flat-rate subscription numbers. Country availability, carrier registration and messaging requirements can differ by number type and destination.
06
Security and production boundaries
Dial's official guidance says API keys should not be exposed client-side or written into logs, and API traffic should use HTTPS. Production systems should add destination allowlists, budgets, retry limits, audit logs and human approval around high-risk outbound actions.
A phone number being technically able to receive a verification message does not mean every third-party service permits automated or virtual-number verification. External platform rules still apply.
07
Where Dial fits in an agent stack
A typical workflow is: the agent decides a call or message is needed, invokes Dial through MCP, CLI, REST or an SDK, Dial performs the communications action, and the resulting event returns to the workflow for the next decision.
That separation is useful because teams can change their reasoning model or agent framework without rebuilding the communications layer. Before scaling, verify live rates, country availability, channel eligibility and compliance for the exact deployment.
Sources
Primary and supporting sources
Facts were rechecked against the linked sources immediately before publication. Pricing, product availability and rollout status can change.