For WhatsApp Business on Meta's Cloud API

The operating platform for WhatsApp Business

Wabi connects your own WhatsApp Business Account to Meta's Cloud API and runs everything around it: managed webhooks, a live team inbox, localized templates through Meta approval, and AI agents that answer routine questions with sources and hand the rest to your team.

For support teams, SaaS products and operators who talk to customers on WhatsApp, and the developers and agents who automate it.

Free plan, no card. Meta bills its own message fees to your account, at cost; we never mark them up.

ML
Maria LópezInbox
Window open · 23 h
Hi! My order 4821 was due Tuesday and hasn't arrived.
Sorry about the wait, Maria. Order 4821 left our warehouse on Monday and the carrier shows it out for delivery today.
AI agent · Sources: shipping policy · order lookup
Can you send it to my office instead?
Changing the address needs someone from the team. I've passed this on with a summary; they'll reply here shortly.
Escalated to Support · handoff summary attached
Hi Maria, done: it goes to your office tomorrow morning.
You
Illustrative conversation in the Wabi inbox

The problem

Meta's APIs are powerful. Running a business on them is a project.

The Cloud API sends and receives messages. Everything a team needs around it, you build and operate yourself.

Webhooks you have to host
A public HTTPS endpoint that verifies Meta's signatures, answers fast, stores every event before processing, survives duplicates and out-of-order statuses, and never drops a message when your app is down.
Templates, one language at a time
Every message outside the 24-hour window needs an approved template. Each language is its own submission, with its own approval, rejection reason, quality rating and pause.
No inbox, no turn state
Meta gives you message events, not conversations. Who answered, who owns it, which customers are waiting and whose window closes in an hour is yours to model.
Agents you can trust
An LLM can reply. Answering from your documents, calling your tools, knowing when to hand off, and showing exactly what it did and what it cost is the hard part.

How it works

From a sandbox number to a live support line

  1. 1

    Start in the sandbox, connect your number

    Every organization gets a simulated number to try everything. When you are ready, connect your own WhatsApp Business Account with Meta's Embedded Signup or with a WABA id and system-user token.

  2. 2

    Messages flow into a live inbox

    Wabi subscribes to your account's webhooks, verifies, stores and deduplicates every event, and updates the inbox in real time with delivery and read receipts.

  3. 3

    Templates localized and approved

    Write a template once, generate each language with AI, review it, submit every locale to Meta and track each approval, rejection and quality change.

  4. 4

    An AI agent takes the routine

    It answers from your knowledge sources with citations, calls the tools you allow, and hands a conversation to your team with a summary when it should not answer.

Sandbox

Try everything before Meta approves anything

Meta's business verification and app review take days. The sandbox number works the minute you sign in, and behaves the way Meta does.

  • Sends report sent, delivered and read within seconds, with Meta-style pricing estimates.
  • Test customers write back, so the inbox, agents and your webhooks see real inbound traffic.
  • New templates are reviewed after about a minute: approved, or rejected with a reason.
  • Numbers ending in 0000 fail like an undeliverable WhatsApp number, to test your error handling.
How the sandbox works
The sandbox from a terminal
npx @meterapp/wabi login                 # browser sign-in, saves an API keynpx @meterapp/wabi get_sandbox           # your simulated number and test customersnpx @meterapp/wabi simulate_inbound_message --text "Hi, where is my order?"npx @meterapp/wabi get_onboarding        # what is left to set up, and how

What you get

Everything around the Cloud API, in one place

One data model underneath: every message, contact, template, agent session and cost belongs to the same conversation history.

Live team inbox
Real-time conversations with delivery and read receipts, assignment, internal notes, the customer's profile and their 24-hour window at a glance. Queues for unanswered, escalated and expiring conversations.
Contacts, consent and segments
One profile per customer with attributes, language, consent records and opt-outs. Rule-based segments, such as everyone whose window closes in two hours or who prefers Spanish.
Templates with AI localization
One template group per message, a localization per language. AI drafts translations that keep every variable; each locale is submitted to Meta and its approval tracked on its own.
Bulk sends to a segment
Send an approved template to a segment with the safeguards built in: consent and opt-outs checked, duplicates skipped, a cost estimate before you start.
WhatsApp Flows
Send a Flow you published in Meta by its id, store every submission, and map the answers to contact fields.
Managed webhooks
No server to run for Meta. Your own systems subscribe to signed Wabi events, such as message.received or conversation.escalated, with retries and a delivery log.
Usage and Meta cost estimates
Messages, AI replies and Meta's per-message charges by number, category and template, estimated from Meta's rate cards and shown at cost.
Teams, roles and audit
Viewer, member, admin and owner roles, teams, WhatsApp accounts and agents shared only with the people who need them, scoped API keys and an audit log.

AI agents

Agents that cite their sources and know when to stop

Deploy a support agent on any number. Every turn is traced, so you can see what it read, what it called, what it said and what it cost.

Answers from your knowledgePoint it at your docs and help articles; replies cite the sources they used.
Tools you allowGive it the lookups and actions it may call, each with its own permission.
Escalation with a handoffWhen evidence is thin, the customer asks for a person or the topic is sensitive, it hands off with a summary, the sources and what it tried.
Session explorer and tracesEvery session's turns, retrieved sources, tool calls, tokens, latency and cost, and why it stopped.
Claude by default, your key on GrowthAgents run on Anthropic's Claude unless you choose otherwise. From Growth up, bring your own model key; those replies do not count against your plan.
Humans stay in controlTake over any conversation from the inbox; the agent steps back and the customer sees one thread.

Everything is an API

52 operations, every one on REST, MCP and the CLI

Every action in the dashboard is an op with one schema, served as REST, as an MCP tool and as a CLI command. Your backend, your scripts and your coding agent use the same API your team clicks through.

curl -X POST https://getwabi.dev/api/v1/simulate_inbound_message \  -H "Authorization: Bearer wabi_…" \  -H "Content-Type: application/json" \  -d '{"text":"Hi, where is my order?"}'

Machine-readable: llms.txt, OpenAPI 3.1 and the API reference, all generated from the same registry.

Pricing

Pay for what the platform does, never a markup on Meta

Plans include messages and AI replies. Meta's own per-message fees go on your WhatsApp Business Account's bill from Meta, exactly as Meta charges them.

Free
For trying Wabi on one number.

Free

1,000 messages a month100 AI replies a month
Starter
For a small team answering customers on one number.

$29/month

10,000 messages a month1,000 AI replies a month
Growth
For businesses automating support and outreach across numbers.

$99/month

50,000 messages a month5,000 AI replies a month
Scale
For operators running several brands, markets or locations.

$299/month

250,000 messages a month25,000 AI replies a month
Compare plans

FAQ

Questions teams ask first

Send your first message in five minutes

Every organization gets a sandbox number. Sign in, message a test customer, watch the reply land in the inbox, then connect your own WhatsApp Business Account when you are ready.