Zavu
Zavu is a unified multi-channel messaging platform that consolidates SMS, WhatsApp, Telegram, Email, Voice, and Messenger behind a single REST API, so developers integrate once instead of stitching together Twilio, Vonage, MessageBird and others. The Unified Messaging Layer API adds smart ML-powered channel routing with automatic fallback and retry, signed webhooks for delivery and inbound events, WhatsApp templates and 10DLC brand/campaign registration, broadcasts with AI content review, contacts, AI agents with flows and RAG knowledge bases, serverless TypeScript functions (Zavu Cloud), and phone-number provisioning. Auth is API-key bearer tokens with test (zv_test_) and live (zv_live_) modes, idempotency keys, cursor pagination, and per-project rate limiting. Official SDKs ship for TypeScript, Python, Ruby, Go, and PHP, plus an official MCP server. Zavu is a 500 Global portfolio company.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Zavu the way a machine reads it — 27 machine-readable artifacts across 21 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Zavu scores 55.5/100 (developing), with a separate agent-readiness read of 87/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Zavu
Each block below is one kind of artifact we hold for Zavu. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 21
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Zavu 10DLC API
The 10DLC API from Zavu — 11 operation(s) for 10dlc.
Zavu Account API
The Account API from Zavu — 1 operation(s) for account.
Zavu Agent Flows API
The Agent Flows API from Zavu — 3 operation(s) for agent flows.
Zavu Agent Knowledge Bases API
The Agent Knowledge Bases API from Zavu — 4 operation(s) for agent knowledge bases.
Zavu Agent Tools API
The Agent Tools API from Zavu — 3 operation(s) for agent tools.
Zavu Agents API
The Agents API from Zavu — 4 operation(s) for agents.
Zavu Balance API
The Balance API from Zavu — 1 operation(s) for balance.
Zavu Broadcasts API
The Broadcasts API from Zavu — 10 operation(s) for broadcasts.
Zavu Contacts API
The Contacts API from Zavu — 8 operation(s) for contacts.
Zavu Functions API
The Functions API from Zavu — 12 operation(s) for functions.
Zavu Introspect API
The Introspect API from Zavu — 1 operation(s) for introspect.
Zavu Invitations API
The Invitations API from Zavu — 3 operation(s) for invitations.
Zavu Messages API
The Messages API from Zavu — 4 operation(s) for messages.
Zavu Phone Numbers API
The Phone Numbers API from Zavu — 4 operation(s) for phone numbers.
Zavu Regulatory API
The Regulatory API from Zavu — 5 operation(s) for regulatory.
Zavu Senders API
The Senders API from Zavu — 5 operation(s) for senders.
Zavu Sub-Accounts API
The Sub-Accounts API from Zavu — 5 operation(s) for sub-accounts.
Zavu Templates API
The Templates API from Zavu — 3 operation(s) for templates.
Zavu URL Verification API
The URL Verification API from Zavu — 3 operation(s) for url verification.
Zavu WhatsApp Alternative API
The WhatsApp Alternative API from Zavu — 11 operation(s) for whatsapp alternative.
Zavu WhatsApp Sync API
The WhatsApp Sync API from Zavu — 3 operation(s) for whatsapp sync.
Scroll within the panel for all 21 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
zavu-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Zavu Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Zavu Messaging Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Zavu — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/zavu · machine-readable index on apis.io