Skip to main content

What Zavu is

Zavu is the communication layer for humans and agents. You get two things, and they are the same platform:
  • An API for messages. Send and receive on WhatsApp, SMS, voice, email, Telegram, Instagram and Messenger through one integration.
  • A runtime for agents. Declare an agent in TypeScript, deploy it with one command, and it answers on those same channels. Including phone calls.
Most teams start with one and end up using both. The agent that answers a WhatsApp thread is the same object that answers the phone, and the message you send by hand goes out the same pipe.

Two ways to build

There is no wrong entry point. Pick the one that matches where your code lives.

Deploy on our infra

Write defineAgent and defineTool in a file, run npx zavudev deploy. Zavu runs the code, holds the conversation, and calls your tools.

Call our API from yours

Keep your stack. Use the REST API or an SDK to send, receive, and drive conversations from your own backend.

Ship an agent

Your code is the source of truth. Every deploy reconciles the live agent to match what the file declares, so an agent you delete from the code is deleted for real. See How agents work. Not starting from scratch? npx zavudev agents pull fermi drops a ready-made agent into your project as editable code. Seven of them ship today, for sales, support, and front desk. See Factory agents.

Send a message

No channel specified means auto: Zavu scores the channels your sender can reach the recipient on and sends through the one that wins on cost and deliverability, with fallback if it fails. See Smart routing.

Channels

Every channel shares one send contract, one set of webhook events, and one bill.

Build with your coding agent

Zavu is designed to be operated by the agent you already code with. Give it the skills and it writes correct Zavu code on the first try, instead of guessing at endpoints.
Twelve skills cover agents, functions, voice, channels, webhooks, templates, broadcasts, contacts and phone numbers. For direct API execution, add the MCP server. They compose: skills decide what to do, MCP does it.

Next steps

Agent quickstart

Deploy an agent that answers a real channel, in about ten minutes

Messaging quickstart

Send your first message from your own backend

How agents work

From TypeScript on your machine to an agent answering a phone call

CLI

Every resource in the API, from your shell and your CI

Authentication

API keys, environments, and the sender header

API reference

Every endpoint, with a live playground