Skip to main content
CallVA is an operations platform for AI voice agents. The voice agent holds the conversation; CallVA runs everything around it: queues and scheduling, the data model each call is recorded in, outcome tracking, recordings, transcripts, knowledge bases, billing and analytics. Calls run on CallVA’s own LiveKit-based voice engine, or on a voice provider you connect, such as Vapi or Retell, so you keep your choice of vendor. Whichever runs the call, it lands in CallVA as a call record of the same shape, in the same project, under the same permissions. Each project defines its own data model. You decide which fields a call carries - an appointment date, a callback flag, an outcome with your own options - and CallVA stores, filters, sorts and reports on them as if they were built in. A call record returns every field at the top level, by its key.

​
Three ways in

CallVA is built to be operated by software as well as by people. The same platform the dashboard shows is reachable three ways:

External API

REST over HTTPS with a bearer token. For your own backend, integrations and scripts. Start with the quickstart, then the API reference.

MCP

Connect any MCP-capable AI agent to https://mcp.callva.io/mcp. It signs in with OAuth; no API key to copy.

CLI

The callva command line, for terminals, shell scripts and coding agents.
An autonomous agent can run a project end to end through these: configure voice agents and their prompts, place calls, read outcomes and transcripts, and adjust what it learned. What any caller may do is decided by the permissions behind its credential - see Authentication and permissions.

​
How it fits together

Your system and the CLI call the External API with an API token. An AI agent connects to the MCP server, which calls the same API on its behalf. Before a call, the voice engine or provider fetches the agent’s configuration from CallVA; during and after it, the results - status, fields, transcript, recording - flow back into the call record. Webhook schedules call your endpoints on the timetable you set, and automations run your own scripts against call records.

​
Concepts

​
Guides

Quickstart

Create a token, talk to your agent in the browser, read the call back.

Authentication and permissions

Organization and project tokens, roles, and why a request is refused.

Calls

Place outbound calls, list and filter call records, read transcripts and recordings.

Custom fields

Shape the data model your calls are recorded in.

Webhooks

Call your endpoints on a schedule with rule-driven webhooks, and read the log of webhook traffic.

Automations

Run your own scripts against call records.