How to Use Dial with AI Agents: CLI, MCP and API Setup

01

Before you start

For the current CLI flow you need Node.js 22 or newer. Dial also requires a new account to verify an email address and a phone number the user controls before onboarding is complete.

Install the official CLI with npm install -g @getdial/cli, then confirm it is available with dial --version. Keep the resulting credentials out of browser code and logs.

02

1. Authenticate the account

Dial documents an OTP-based CLI flow. Start with dial auth login you@example.com, verify the emailed code, then register and verify a non-Dial phone number you control for a new account.

03

2. Choose CLI, MCP, REST or an SDK

Use the CLI when a coding agent or terminal workflow is directly driving Dial. Use MCP when an MCP-capable agent should discover structured Dial actions without constructing raw HTTP requests.

Use REST when your backend owns orchestration, authorization and persistence. Dial also publishes Node and Python SDKs for application-level integration without manually implementing every request.

04

3. Configure a number and make a controlled call

Configure one number for a narrow first workflow and define an inbound instruction with explicit boundaries. For example, a receptionist can qualify a request and collect a callback while escalating payments, legal commitments or sensitive account actions.

For outbound calls, keep the instruction task-specific and restrict what the agent may disclose or agree to. Calling, recording, disclosure and marketing rules vary by jurisdiction, so production automation needs a country-specific compliance review.

05

4. Handle messaging and events

Dial supports SMS and currently offers WhatsApp through beta, account-enabled access. Do not assume every channel is immediately available on every account or number.

Build event-driven handling instead of assuming a successful request means the communication completed. Number and channel capabilities can settle asynchronously, so production code should inspect current status and error information.

06

5. Add credential and spending controls

Dial currently starts pay-as-you-go number ownership at $3 per month per phone number plus metered usage, with a $5 signup credit. Voice and SMS rates vary by destination, so verify the live billing view for the destinations you actually use.

• store credentials server-side
• allowlist destinations where practical
• set workflow-level budgets
• require approval for high-risk actions
• log prompts, destinations and outcomes
• stop retry loops on policy or carrier errors

07

6. Production checklist

Before launch, verify the exact countries and number types you need, current channel eligibility, destination rates, carrier-registration requirements, error handling, human escalation and recipient-consent rules.

Start with one narrow workflow and one controlled number. Expand only after real call and message events confirm that the channel, cost and operational behavior match the assumptions made during development.