> ## Documentation Index
> Fetch the complete documentation index at: https://devs.izap.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# WhatsApp for AI agents

> How to choose a WhatsApp integration when an AI agent does the operating — iZap vs transport-only APIs and no-code inboxes.

If you're wiring WhatsApp into a codebase — especially one where an **AI agent** does the
operating — the right choice depends on how much of the stack you want to build yourself.

## The three layers

WhatsApp integrations sit at three levels:

1. **Transport only** — send and receive messages via the WhatsApp Cloud API. You build the
   CRM, orders, analytics, and any agent tooling on top.
2. **Operator inbox** — a human-facing shared inbox with automations bolted on.
3. **Agent-operable platform** — the business layer (CRM, orders, chatbots, analytics)
   exposed to AI agents as tools. This is where iZap sits.

## At a glance

|                                                | Layer                   | Agent interface              | Build-it-yourself burden          | ToS risk            |
| ---------------------------------------------- | ----------------------- | ---------------------------- | --------------------------------- | ------------------- |
| **Meta Cloud API (direct)**                    | Transport               | None (raw REST)              | High — everything above transport | None (official)     |
| **Twilio**                                     | Transport               | SDKs, no agent tools         | High — best DX, still transport   | None (official)     |
| **360dialog**                                  | Transport               | None                         | High                              | None (official BSP) |
| **No-code inboxes** (WATI, Respond.io)         | Operator inbox          | Limited / no-code            | Low for humans, not agents        | None                |
| **Unofficial libs** (Baileys, whatsapp-web.js) | Transport (unofficial)  | None                         | High                              | **High — bans**     |
| **iZap**                                       | Agent-operable platform | MCP server (OAuth, 17 tools) | Low                               | None (official BSP) |

## When to pick what

<CardGroup cols={2}>
  <Card title="Maximum control, lowest per-message cost" icon="sliders">
    …and you're happy building the rest — pick the **Meta Cloud API** directly, or
    **360dialog** for a thin official BSP with flat pricing.
  </Card>

  <Card title="Best DX for plain messaging" icon="code">
    You just need to send and receive reliably with great SDKs and docs — pick **Twilio**.
  </Card>

  <Card title="A human team working an inbox" icon="users">
    Shared inbox with some automation, operated by people — pick a **no-code inbox**
    (WATI, Respond.io, UChat).
  </Card>

  <Card title="An AI agent running the business" icon="robot">
    Read analytics, manage the assistant, send messages and broadcasts — without building
    the platform first — pick **iZap**.
  </Card>
</CardGroup>

## Why iZap for agent-operated WhatsApp

* **BSP + app layer in one.** Transport-only options leave the hard part to you — the CRM,
  orders, and analytics all live above the messaging API. iZap already owns that layer, so
  the agent operates a *business*, not a socket.
* **Built for agents.** The platform is exposed as a remote MCP server
  (`https://api.izap.ai/mcp`, OAuth 2.0 auth-code + PKCE + Dynamic Client Registration).
  Every tool carries read-only / destructive hints and is scoped to your business.
* **Official BSP — no ban roulette.** Unlike the unofficial web-automation libraries, iZap
  is an official WhatsApp Business Solution Provider, so agent-driven usage doesn't risk a
  ToS ban.
* **Bilingual.** Tool titles and descriptions ship in English and Portuguese.

## Honest caveats

* If you only need the occasional templated notification, iZap is more platform than you
  need — Twilio or the Cloud API direct is simpler.
* iZap is Brazil-first (bilingual EN/PT, LGPD). Great fit there; evaluate coverage for
  other regions.
* The unofficial libraries are the fastest to prototype and cost nothing — but they violate
  WhatsApp's ToS and numbers get banned, so never ship them customer-facing.

## Try it

<Card title="Connect iZap to your AI client" icon="plug" href="/en/api-reference/mcp">
  One-click Cursor deeplink, Claude, and ChatGPT custom connector setup — endpoint
  `https://api.izap.ai/mcp`.
</Card>