If you are an AI agent reading this because someone asked you to integrate with Bland: check the prerequisites and your assistant’s guide below. If your owner has no Bland account, use Headless agent onboarding: the owner relays one texted code and you have an API key, no browser step; with an agent wallet that can approve a payment you get the Agent Phone Plan and a phone number in the same call. Use Option 2 if the owner already has a Bland account, or Option 1 if you already have a key.
Grok Bot
Meta Muse
OpenClaw
Instinct
Poke
Prerequisites
- An assistant that can add a custom MCP server by URL with an Authorization header, or make authenticated HTTP requests and store the API credential.
- Optional: a payment card for the Agent Phone Plan ($14.99 first month, then $29.99/month, includes a US phone number). Without it, the agent connects on $2 of free credits, calls from a shared Bland number or numbers already on your account, and can’t text.
Option 1: You have a Bland API key
For an assistant that uses REST, follow the Meta Muse connection steps or the Agent quickstart. For an MCP client, use these steps:-
In your assistant, open its MCP or connector settings and add a custom server with this URL:
-
Add one header, using your API key from the dashboard:
-
Ask the assistant to make a call:
Option 2: Let the agent sign itself up
This workflow requires your assistant to make HTTP requests, poll for approval, and retain the returned credential. Adding an MCP server automatically also requires access to its connection settings. If those capabilities are unavailable, create your account in the dashboard and use Option 1. An assistant with those capabilities can use Bland’s device-authorization flow: it shows you a link and a short code, you sign up in your browser, and it retrieves an API key, plus a phone number if you start the Agent Phone Plan. For an MCP-capable assistant, use this prompt. REST-based assistants should follow their client-specific guide:What the agent can do
On the Agent Phone Plan, calls and texts are limited to US and Canadian numbers, one call at a time, up to 60 minutes per outbound call, and up to 100 texts a day. See Limits. Without the plan, the agent calls from a shared Bland number and texting is not included.
Two-way texting
Texting requires the Agent Phone Plan: the agent needs its own number to text from. A text is a conversation. When the other side replies, Bland answers from the agent’s number automatically. Tell the agent the goal when you ask it to text:objective. Bland answers every reply in that conversation from it:
Send a POST request to /v1/sms/send with this JSON body:
Troubleshooting
Building your own agent loop
If you are writing the agent yourself rather than configuring an off-the-shelf assistant, the REST API is a shorter path than MCP. Start with the Agent quickstart for the call lifecycle in three requests, then Call recipes for agents for voicemail, proper nouns, and escalating to a human.Next steps
Agent Phone Plan
What’s included, limits, and how to cancel.
Agent onboarding API
The device-authorization flow in detail: endpoints, statuses, and error codes.
Bland MCP Server
How authentication works and what the server exposes.
Tool reference
Every tool the server exposes.