Developers
One platform. Three ways in.
A REST API over agents, calls, numbers, and knowledge. An MCP server for Claude Code and Cursor. Signed webhooks for every call event. Same platform underneath all three.
- GET /v1/calls
- zumu.calls.search
- call.flagged
Pick a door
Three ways to build on Zumu
- REST
GET /v1/calls/{id}Platform API
An OpenAPI surface over agents, calls, numbers, and knowledge. Every route your dashboard calls is a route you can call.
Read the API reference - MCP
zumu.calls.searchMCP Server
Run your call center from Claude Code or Cursor. A real OAuth 2.0 server sits behind it, not a demo integration, so an agent in your editor can search calls or update a prompt directly.
See the MCP server - EVENTS
call.flaggedWebhooks
Signed with rotation overlap, retried, dead-lettered, and replayable. Write a flag rule in plain language and a model grades every call against it.
See webhooks
Prefer a script tag?
The same agent, voice and chat, embeds on your own page with one line and its own isolated styles.
What you can build
Five things engineers actually wire up
- REST
Pull a call's full session report into your own warehouse: cost by component, which provider served it, and the complete tool trace.
- MCP
Ask Claude Code or Cursor to search transcripts or update an agent prompt without opening the dashboard.
- EVENTS
Fire a webhook the moment a call is flagged by a rule you wrote in plain language, not a regex.
- REST
Query the same knowledge retrieval an agent uses mid-call, before a change ever reaches a caller.
- REST
Read or restore an agent's configuration history from your own deploy pipeline.
Start here
Start with the API.
It covers the most ground, and the MCP server and webhooks both sit on top of the same surface.