Create a pairing session
Generate a QR code or phone-number sync flow for the WhatsApp account you want to connect.
$ curl https://api.staging.whatsapp-use.com/v1/me
Connect your agentto WhatsApp.
Pair an existing WhatsApp account and give full access to your agent. Use REST, WhatsApp MCP, or the hosted agent harness through one platform API key and a hidden runtime we manage.
PROMPTPaste into your agent
Create a WhatsApp-Use API key.
Base URL: https://api.whatsapp-use.com
Key: wuse_live_...
Then request WhatsApp pairing.Pair via QR or phone
Connect an existing WhatsApp account. Same flow as adding a WhatsApp Web session.
Drop-in MCP
Remote WhatsApp MCP and Agent MCP endpoints connect through OAuth and route to the same hidden runtime.
Hidden runtime
One WhatsApp connection maps to one hidden runtime. Developers rotate keys or OAuth grants without managing ECS services.
how it works
Pair once. Call it from your agent.
We host the WhatsApp client and the pairing flow. You authorize the account, then your agent talks to it over MCP.
Pair the account
The account owner scans the QR or completes phone sync. We host the WhatsApp client behind the scenes.
Add the MCP server
Use REST with an API key, or connect the remote WhatsApp MCP and Agent MCP endpoints through OAuth.
Receive webhook events
The hidden runtimes emit signed events to whatsapp-use-backend, which delivers signed webhooks to you.
use cases
Any kind of agent.
Personal assistants, coding agents, MCP-aware tools, or anything custom you build.
AI assistants
Hand your WhatsApp to Claude, ChatGPT, or any custom assistant. Daily briefs, on-the-go replies, full search.
Coding agents
Get pinged when a build finishes or a PR is ready. Reply to deploy from your phone.
MCP-aware tools
Use WhatsApp MCP or Agent MCP from clients that support remote Streamable HTTP MCP with OAuth.
Calendar agents
Auto-respond to scheduling requests, confirm meetings, and send reminders.
Research agents
Let an agent search your WhatsApp for context — past conversations, files, decisions.
Custom agents
Call REST directly with an API key or connect through remote MCP with OAuth.
deployment
WhatsApp Use control plane. Hidden connection runtimes.
Developers see stable WhatsApp connections, rotatable credentials, and one WhatsApp Use URL. We manage auth, routing, WhatsApp sockets, harness execution, memory boundaries, and runtime lifecycle behind that interface.
Hosted platform
WhatsApp Use backend owns auth, API keys, routing, dashboard state, usage, and webhook delivery.
WorkOS-ready authAPI-key routingSigned webhooks
Connection runtime
Each active WhatsApp connection gets a hidden runtime for WhatsApp service and the hosted agent harness.
Runtime isolationManaged WhatsApp socketHarness memory boundary
faq
Common questions.
Mostly about how this is built and what happens to your data.
Is this the official WhatsApp Business API?
No. WhatsApp-Use runs on the same protocol WhatsApp Web uses (a whatsmeow-style client). That's how we keep pairing instant and skip the Business API onboarding queue.
What about WhatsApp's terms of service?
WhatsApp lets users connect their account to web sessions, which is what we do under the hood. Heavy automation can still trigger rate limits or bans — respect limits and don't message people who didn't ask to hear from you.
How does pairing work?
QR code or phone-number sync — the same flow as adding a new WhatsApp Web session. The account owner stays in control and can revoke at any time.
Where does message data live?
In the hidden runtime storage for the WhatsApp connection. Credentials can rotate without replacing the paired runtime.
Can I use this with Claude, Cursor, or my own agent?
Yes, if the client supports remote MCP over HTTP with OAuth. Custom agents can also call the REST API directly with bearer API-key auth.
What happens to my data if I cancel?
Sessions disconnect immediately. Stored messages and webhook logs are purged within 30 days.
pricing
Free developer access now.Paid packaging later.
Stripe is paused for the MVP. Creating a free key provisions the hidden runtime; the $20 and $40 packages are future product targets.
Developer Platform
Free for now
Create a key and try WhatsApp REST, WhatsApp MCP, hosted agent turns, and webhooks.
Free API keyHidden connection runtimeWhatsApp REST and MCPHosted agent capability
WhatsApp API
$20 / month later
Future packaging for developers that only need WhatsApp access through REST or MCP.
WhatsApp runtimeREST APIWhatsApp MCPWebhook delivery
WhatsApp MCP
$40 / month later
Future packaging for teams that primarily install the remote MCP connection in AI clients.
OAuth remote MCPWhatsApp toolsOptional hosted agent toolsSame connection runtime
start
Connect WhatsApp to your agent without running the client yourself.
Free developer access while the provisioning, WhatsApp, and hosted agent-loop platform comes online. No payment method required.