Let an AI agent set up Wabery

Your AI agent can create your Wabery account, build and test your WhatsApp setup, and take it live for you. You don’t need to work in the dashboard. You stay in control: the agent asks you to approve its access, sends you a link for each step only you can do, and publishes to Live only after you confirm.

This works with any agent that can make HTTP requests or use MCP, such as Claude Code, Codex, or Cursor. Ask it to set up WhatsApp with Wabery, or point it to wabery.com/auth.md.

Who does what

Step	Your agent	You
Create your account	Asks for your email and sends you a link with a 6-digit code	Sign in or create your account, check the code, choose a project, and approve
Build the setup	Sets your webhook or builds the hosted agent’s Draft	Nothing
Test on the sandbox	Sends you a WhatsApp link	Open it on your phone and send the prefilled code
Connect your number	Sends you a connection link	Sign in to Facebook and connect your number with Meta
Publish the hosted agent	Shows you the changes and asks you to confirm	Confirm, or ask for changes
Go live	Tells you anything Meta still needs	Finish it in your Meta account

1. Approve your agent’s access

Your agent asks for the email you use for Wabery, or want to use. It then sends you a link like https://app.wabery.com/authorize-agent?code=123456 and a 6-digit code.

1. Open the link. Sign in with that email, or create your account with it. Wabery emails you a sign-in code. If the account is new, Wabery creates your workspace and a first project, then returns you to the request.
2. Check that the page shows the same code as your agent.
3. Choose the project the agent can work on, then select Approve access.

Your agent then receives an API key for that project. It can manage channels, flows, contacts, and functions, send messages from the project, and publish your agent to Live after you confirm the changes. It cannot erase contacts or create other API keys.

The link expires after 15 minutes. If it expires, ask your agent to start again. Only workspace owners and admins can approve. If the page says you’re signed in with a different email, sign in with the email your agent asked for.

Only approve requests you started

Approve only when you asked your own agent to connect to Wabery. Wabery never asks you to approve a request someone else sent you.

wabery login --email you@example.com uses the same approval flow, so the CLI no longer asks you to copy and paste a key.

2. Your agent follows the setup checklist

After you approve, your agent reads a checklist of the remaining steps. For each step, Wabery tells the agent whether it can do the step itself through the API, or whether it needs you, and gives it any link to send you. You’ll hear from your agent only when there’s something for you to do.

The steps depend on who answers your customers:

• Your own app or agent answers: your agent sets the HTTPS webhook that receives inbound messages. See external automations.
• Wabery’s hosted agent answers: your agent builds the hosted agent’s Draft and assigns your channel to it. See hosted agent.

If your number already answers through your own app, your agent asks before switching to the hosted agent. It keeps your number on your app while you test the hosted agent on the sandbox, and moves the number over only when you confirm the publish.

3. Test on the sandbox

Your agent sends you a WhatsApp link. Open it on your phone and send the prefilled message. It contains your project’s join code, and your next messages to the shared Wabery number reach your project. Your agent can then check the replies with you. See Wabery sandbox.

4. Connect your WhatsApp number

When you’re ready for real customers, your agent sends you a connection link. It asks first whether you use the WhatsApp Business app on that number, so you can keep using the app if you do.

Open the link, sign in to Facebook, and connect your number with Meta. You don’t need to sign in to Wabery. The link works once and expires after 7 days. Anyone with the link can finish this setup, so don’t forward it.

Your agent can create links for a new number or a number that uses the Business app. To move a number from another WhatsApp API provider, use Connect WhatsApp in the dashboard.

Meta charges you directly for WhatsApp conversations on your own number. See WhatsApp pricing.

5. Confirm each publish

This step applies when Wabery’s hosted agent answers your customers. Your agent edits only the Draft. Your customers keep getting the Live version until you confirm a publish.

Before publishing, your agent shows you what changed and which channels it affects. Reply to confirm, or ask for changes. Your agent publishes only after you confirm, and every later change needs your confirmation again. Publishing runs the same checks as Agent → Review and publish in the dashboard.

Your agent may also ask you to approve:

• moving a channel from your webhook to the hosted agent
• applying the Draft to every channel that is already live
• going live with automations only while AI replies are unavailable, for example before you add wallet credit

You decide what goes live

Wabery relies on your agent to show you the changes and ask before it publishes. It can’t see your conversation with your agent, so you are responsible for what you confirm. Apps connected through the hosted MCP server, such as Claude, must also show you an approval prompt before they publish. Wabery refuses the publish if the app can’t ask you.

You can still review and publish yourself on Agent at any time.

6. Go live

After your number connects, Meta may still need something from you before real customers can message it, such as a payment method on your WhatsApp Business Account. Your agent tells you exactly what’s missing. Finish it in your Meta account, and your agent confirms when you’re live.

Remove your agent’s access

Open Access → API keys and revoke the key named after your agent and project. Your agent loses access immediately. Apps connected through the hosted MCP server are listed under Access → Connections.

For AI agents

• Registration, claim, and the full onboarding walkthrough: auth.md
• Checklist: GET https://api.wabery.com/v1/onboarding
• Customer connection links: POST /v1/onboarding/handoffs, then poll GET /v1/onboarding/handoffs/{id}
• Publishing: GET /v1/agent/publish-review, then POST /v1/agent/publish with customer_confirmed: true after the customer confirms
• MCP tools: wabery_get_onboarding, wabery_create_onboarding_handoff, wabery_get_onboarding_handoff, wabery_get_agent_publish_review, wabery_publish_agent
• CLI: wabery login --email, wabery onboard, wabery onboard connect-whatsapp, wabery onboard publish-review, wabery onboard publish
• OpenAPI spec