Official WhatsApp Business Cloud API bridge. Receives webhooks, sends messages, OGG Opus audio, documents, and reactions — straight from your terminal, with built-in allowlist and a permission relay that scrubs secrets.
Official API means: real message limits, HSM templates, opt-in/opt-out, full Meta policy compliance. No hacks, no suspensions.
Receives text, image, audio (OGG Opus, transcribed), document, video, sticker, location, and reactions. Verifies Meta’s HMAC X-Hub-Signature-256 automatically.
Claude calls typed skills — no hand-rolled JSON.
Only authorized numbers reach Claude. Secrets never enter the context — they’re injected by the relay.
Local via cloudflared/ngrok. When Cloud opens: Embedded Signup + hosted webhook, optional Coexistence to run alongside human support.
compare self-hosted × cloud →You’ll need: a WhatsApp Business Cloud API token (Meta) + Phone Number ID + cloudflared installed. The plugin handles the rest.
Yes. It's Meta's official WhatsApp Business Cloud API — the same endpoint enterprise partners use. No reverse-engineering, no unofficial libraries, no risk of account bans, with Meta's own SLA.
For production, yes — any Meta integration requires WABA. For testing, Meta provides a free sandbox number inside the app.
Cloud (private beta) hosts the webhook on RIA's infra. You only do Embedded Signup with 5 clicks — join the waitlist via the hub form.
It's a Claude Code plugin — uses native MCP. The webhook is plain HTTP, so in theory it's adaptable, but the allowlist and permission relay were designed around the Claude Code model.
Self-hosted is free, Apache-2.0. Meta charges its own per-conversation fees (template/utility/marketing). Cloud (RIA) will have its own pricing when it opens.