API de WhatsApp
para agentes que puedes lanzar hoyCrea
para tus clientes
Empieza en Sandbox y después pasa a Live en un número real. REST, SDK de TypeScript, CLI y MCP.Plan gratuito, sin tarjeta.Crea un agente útil, pruébalo en Sandbox y adáptalo a cada cliente. Tú gestionas la relación; Wabery proporciona las herramientas.
¿Ya construiste el agente? Conéctalo a WhatsApp →
$ curl https://api.wabery.com/v1/messages \
-H "Authorization: Bearer $WABERY_API_KEY"Usa una clave de API limitada al proyecto.
$ npm i -g @wabery/cli
$ wabery loginMismas claves en Sandbox y Live.
¿Ya construiste el agente? Conéctalo a su WhatsApp →
Construye en Wabery o usa Claude, ChatGPT, n8n, Make o tu propio código.Para creadores independientes, agencias y desarrolladores. No somos una agencia que lo hace por ti.
Sin tarjeta. Primer cliente gratis. Los siguientes desde 5 USD al mes.
Everything between send and a live WhatsApp number.
Channel setup, Meta delivery, inbox, Flows, hosted functions, and signed events. You bring the agent.
Everything between “we’ll build it” and “it’s on their number.”
Wabery handles the infrastructure that puts your agent on a client’s real WhatsApp number. That includes channel setup, Meta delivery, inbox, flows, custom logic, and signed events.
WhatsApp channels
Send and receive on WhatsApp Business through one clean API. Wabery handles channel setup, routing, webhooks, and Meta API details.
WhatsApp Flows
Build native, in-chat forms and get back clean, validated submissions. Wabery handles the Flow JSON, encryption, and data exchange.
Signed event webhooks
Every inbound message, delivery status, and Flow submission arrives as a typed, signed event, with retries, delivery history, and endpoint health tracking.
Inbox & contacts
Threads, contacts, and conversation state are managed for you. Query them over the API, or let your team work them in the shared inbox.
Hosted functions
Run custom TypeScript for tool calls, routing, replies, and contact state, without operating your own worker fleet.
CLI & MCP server
Manage flows and automations from your terminal, or drop the Wabery MCP server into Claude and ship features by describing them.
Wabery developer resources
Hook the agent you already have to WhatsApp.
Same API, CLI, and MCP in Sandbox and Live. Claude, n8n, Make, or your own backend.
Wabery developer resources
Hook the agent you already have to their number.
Same API, CLI and MCP in Sandbox and Live. Claude, n8n, Make or your own backend, then publish it to the client.
# install and log in
$ npm i -g @wabery/cli
$ wabery login
# list channels and check routing
$ wabery channels list
# push a flow as config
$ wabery flows apply lead-intake.flow.ts
# deploy a hosted function
$ wabery functions deploy checkout-helperimport { Wabery } from "@wabery/sdk";
const wabery = new Wabery(process.env.WABERY_API_KEY);
await wabery.messages.send({
channel: "whatsapp",
to: "+14155550100",
text: "Your order just shipped",
});{
"type": "message.received",
"channel": "whatsapp",
"contact": { "id": "ct_8fa12c", "name": "Alex" },
"message": {
"text": "do you ship internationally?",
"timestamp": "2026-06-20T14:21:09Z"
},
"signature": "v1=3a7f…" // verify with your signing secret
}export const leadIntake = flow({
name: "lead-intake",
screens: [
screen("Tell us about your project", [
text("name", { label: "Your name" }),
number("budget", { label: "Budget (USD)" }),
select("timeline", { options: ["ASAP", "This month"] }),
]),
],
onSubmit: "https://api.acme.com/leads", // your webhook
});import type { Ctx } from "@wabery/functions";
export default async function checkoutHelper(ctx: Ctx) {
const cartId = await ctx.data.get<string>("cart_id");
const status = await ctx.fetch("https://api.acme.com/cart/" + cartId);
const cart = await status.json();
await ctx.send.text("Your cart is " + cart.state);
return { output: { cart_state: cart.state } };
}# already have the CLI? print an MCP server config for your agent
$ wabery mcp-config claude --raw
$ wabery mcp-config codex --raw
$ wabery mcp-config opencode --raw
# → now ask: "create a lead-intake flow and route it to
# our /leads webhook". The agent calls Wabery for you.▸ Manage channels, flows, and functions straight from your terminal.
Sandbox today. Live on a real number.
Have something to send the client before end of day.
Open a project
One project, one number. Start in Sandbox. No Meta setup.
Get the agent answering
API, CLI, or MCP, or connect Claude, n8n, or your code. Test on the sandbox number.
Go live
Connect the WhatsApp Business number. Same project, same keys, same webhooks.
Open their project
One project per client. Start in Sandbox so you can show them something working before you touch their number.
Get the business agent answering
Build the WhatsApp business agent with Wabery's API, or connect the stack your agency already sells. Test replies and handoff on a sandbox number, not theirs.
Put it on their number
Connect their WhatsApp, hit Live, send the walkthrough. Repeat for the next client without rebuilding the stack.
Sandbox → Live
Test in the WhatsApp sandbox, then go live on a real number
Every project starts on a shared WhatsApp sandbox number. Send the join code from your phone, get replies right, then connect a real WhatsApp Business number. Same project, same code, same webhooks.
- No Meta Business Manager, no display-name review, no card to start.
- Same API keys, CLI, and MCP server in Sandbox and Live.
- You connect your own WhatsApp Business account and pay Meta directly.
- A project uses no paid Live-project capacity until a real channel connects.
Sandbox, for the test
A shared Wabery test number. Join from your phone, send a message, and verify the agent before connecting Meta.
Live, on the real WhatsApp number
Connect the WhatsApp Business number and switch the same project to Live. Keep the same keys, code, and webhooks.
Sandbox → Live
Test in the WhatsApp sandbox, then go live on their number
Every project starts on a shared WhatsApp sandbox number. Send the join code from your own phone, get the replies right, and put a working chat in front of the client the same afternoon. When they say yes, connect their real WhatsApp Business number and hit Live. Same project, same code, same webhooks.
- No Meta Business Manager, no display-name review, no card to start.
- Same API keys, CLI, and MCP server in Sandbox and Live.
- The client keeps their own WhatsApp Business account and pays Meta directly.
- A project uses no paid Live-project capacity until a real client channel connects.
Sandbox, for the demo
A shared Wabery test number. Your phone joins with a code, the agent answers, and you record the walkthrough. Nothing touches the client's Meta assets yet.
Live, on the client's WhatsApp
They connect their own WhatsApp Business number through Meta's embedded signup. You flip the project to Live. The bot you demoed is the bot their customers message.
Build
Ship from the terminal, or call the API.
Point Claude, Cursor, or Codex at the Wabery MCP server, or call REST from n8n, Make, or your own code. The WhatsApp side is the part you stop building.
- CLI and REST
- Ship from the terminal, or call the API from n8n, Make, or your own code.
- Your AI coding agent (MCP)
- Point Claude, Cursor, or Codex at the Wabery MCP server.
Where we fit
This is not a team inbox.
If you want seats, tags, and agents working a queue, that is a different product. Wabery is the WhatsApp API, sandbox, and agent infrastructure under the agent you already have.
Honest comparisons, including where the other tool wins:
Build
Describe the agent. It's live on WhatsApp.
Write what the client's agent should do in plain English and Wabery turns it into a WhatsApp agent you can message in Sandbox in minutes. Or bring the stack your agency already sells. The WhatsApp side is the part you stop building.
- Wabery builder
- Describe the client job. Get a working agent you can message.
- Your AI coding agent
- Point Claude, ChatGPT, Cursor, or Codex at the Wabery MCP server.
- CLI and REST
- Ship from the terminal, or call the API from n8n, Make, or your own code.
Where we fit
This is not a white-label team inbox
If the client wants seats, tags, and agents working a queue, buy them a team inbox. Wabery is for the other job: the chatbot runs in Sandbox for the demo, then on the client's WhatsApp. That's the whole product.
Honest comparisons, including where the other tool wins:
Plan the cost of a client outcome.
Use your own task-cost assumptions. Include model calls, retries, messaging, external systems and human support; missing inputs stay unknown.
Pricing that scales with Live projects.
First Live project free. Pro is $15 for two. Add projects as they go live.
Pricing that scales with your client portfolio.
Ship one client free. Pro is $15 for two Live clients. Add the next ones as they close.
Free
$0
Build and explore.
- One Live project
- One connected channel
- 500 messages / month
- Sandbox, drafts, and API access
- Core building features
- No credit card
- One Live project
- One connected client channel
- 500 messages / month
- Sandbox, drafts, and Wabery blueprints
- Core building features
- No credit card
Pro
$15
Launch and operate on real numbers.
Launch and operate for real clients.
- Two Live projects included
- Additional projects from $5 / month
- 50K shared messages
- Additional 50K capacity for $15
- Unlimited draft and Sandbox projects
- Unlimited team members
- Multiple channels per project
- Every core feature included
- Two Live projects included
- Additional projects from $5 / month
- 50K shared messages
- Additional 50K capacity for $15
- Unlimited draft and Sandbox projects
- Unlimited team members
- Multiple channels per project
- Every core feature included
See how project pricing works
5 Live projects
80K messages
Meta, AI usage, and taxes are billed separately.
No per-seat pricing. No per-channel fee. Cost scales with Live projects and messages, not with seats.
No per-seat pricing. No separate fee for every channel. Every core deployment feature included. Traditional platforms charge per seat, per feature or per channel. Wabery scales with the number of client deployments your agency operates.
- Launch a client without rebuilding WhatsApp infrastructure
- Keep each client's data, channels and environments isolated
- Test in Sandbox, then publish to Live
- Add WhatsApp, Instagram or Messenger without a per-connection fee
- Give the team access without paying per seat
- Scale Wabery cost as the agency wins more clients
Questions before you send the first message.
Questions agencies ask before they build.
What is Wabery?
Wabery is WhatsApp API and agent infrastructure. Sandbox first, then go live on a real WhatsApp Business number. REST, TypeScript SDK, CLI, and MCP.
Who is Wabery for?
Developers and teams who need WhatsApp in their agent, app, or automation. Not a team inbox.
How do I send my first message?
Create a free project, get an API key, join the sandbox from your phone. CLI, REST, or MCP. No Meta setup to start.
Can I bring my own agent?
Yes. Claude, ChatGPT, n8n, Make, or your own code. Wabery is the WhatsApp connection, delivery, Flows, inbox, and signed events.
How does pricing work?
First Live project free, 500 messages. Pro is $15/month for two Live projects and 50K shared messages. Meta and AI usage billed separately.
Do I pay Meta directly?
On a dedicated WABA, yes: you pay Meta directly at its published rates. Wabery pays Meta for the shared sandbox; delivery is free through September 30, 2026, then Wabery deducts the published destination-market service rate from your wallet without markup.
Which channels does Wabery support?
WhatsApp is the primary channel. Projects can also connect supported Instagram and Messenger channels.
Are webhook events secure?
Yes. Wabery signs webhook payloads so your backend can verify their origin, and retries failed deliveries.
Is my data secure?
Yes. Data is encrypted in transit, API keys are project-scoped, and projects keep their contacts, conversations, channels, and credentials isolated.
What is Wabery?
Wabery provides tools for creators, agencies and developers to build and deliver WhatsApp agents. Test in a shared sandbox, then prepare a separate project on each client's authorized WhatsApp Business number.
Is Wabery a WhatsApp inbox?
Wabery includes inbox tools, but its purpose is helping you build and operate agents for clients. You manage the client relationship; Wabery provides the infrastructure.
Do I need Meta setup to demo?
No. Demo in a shared sandbox with no Meta setup, then go live on the client's WABA.
Can I connect a native Meta Business Agent today?
Meta Business Agent support is currently available through a limited pilot. Your client needs access to Meta Business Agent and must authorize their WhatsApp account. Start with Wabery's own agent if Meta access is unavailable. Native Meta MCP connections are not supported yet.
Can the agent perform any business action?
No. Install an approved action version for the client's project and channel. Consequential changes require confirmation of the exact action details, and private data requires a current consumer authorization. Advanced backend setup still needs an integrator; there is no universal one-click connector marketplace.
Are Meta costs included in the Wabery Wallet?
No. The client pays Meta's dedicated-channel messaging fees directly. Meta Business Agent usage, where available, is externally billed and unavailable in Wabery's measured AI costs. Your Wabery wallet limit is not a Meta spending cap. There is no automatic paid fallback between runtimes.
Who is Wabery for?
Wabery is for independent creators, agencies and developers who build, adapt and operate agents for clients. It does not promise earnings or sell your services for you.
How can I build a WhatsApp chatbot with Wabery?
Build in Wabery or bring Claude, ChatGPT, n8n, Make, or your own code.
What kinds of WhatsApp chatbots can my agency ship?
Start with appointment requests, lead qualification, support, human handoff, or Wabery Reservations. Reservations can confirm tables, scheduled class places, and private appointments; unsupported booking systems, payments, and two-way calendar sync need an authorized integration.
How fast can I launch a client's WhatsApp chatbot?
You can start in Wabery's simulator, use a private browser link, or test WhatsApp through the shared Sandbox without connecting a client's Meta assets. Live publication depends on the selected channels, runtime readiness, and billing. Sandbox results are not proof of Meta Business Agent eligibility.
Which channels does Wabery support?
WhatsApp is the primary channel. A project can later include Instagram, Messenger and other supported channels without a separate per-connection fee.
How does pricing work?
Your first Live client project is free and includes 500 messages. A project becomes Live when its first real client channel connects. Pro is $15 per month for two Live projects and 50K shared messages. Additional Live projects are $5 then $3, and Enterprise pricing applies above 100 projects. Meta and AI usage are billed separately.
Do I pay Meta directly for WhatsApp messaging fees?
On a dedicated WABA, you connect your own WhatsApp Business assets and pay Meta's messaging fees directly at its published rates. For Wabery's shared sandbox, delivery is free through September 30, 2026; from October 1, Wabery deducts the same published destination-market service rate from your wallet without markup. Wabery's platform pricing is separate and based on your number of Live client projects.
Can I bring my own chatbot or automation?
Yes. Build in Wabery, or connect a chatbot made with Claude, ChatGPT, n8n, Make, your own code, or another external system. Wabery handles the WhatsApp connection and message delivery for each client.
Do I pay per team member or per channel?
No. Pro includes unlimited team members and multiple channels inside each client project. Cost scales with Live client projects and production message usage.
Is my clients' data isolated?
Yes. Each project keeps contacts, conversations, channels, credentials and environments isolated so one client does not share data with another.
Is my data secure?
Yes. Data is encrypted in transit, webhook payloads are cryptographically signed so you can verify their origin, and your messaging data stays yours.
Get a sandbox number today.
Free API key. No credit card. Open-source SDKs.
Your client needs a WhatsApp business agent.
Ship it.
The stack AI agencies already use, plus a number they can show the client today.
No credit card. Open-source SDKs. Cancel anytime.