For when you don't want a dashboard

Ask your calls what happened.

Planned

A versioned REST API and a read-only MCP server, so your call data is available to your own tooling and to an AI session without anyone opening a chart.

To be plain about it: this part is not built. It is described here in the future tense because that is what it is. If it is the reason you would sign up, wait for the dated line in the changelog.

Start free See pricing

14 days on Scale, no card. Full export on every tier.

In detail

How it is meant to work

REST API

Versioned, documented, org-scoped keys with scopes and revocation.

MCP server

Query calls, transcripts and revenue aggregates from Claude and other MCP clients.

Read-only by design

The MCP server queries your data. It cannot alter it.

Export always

Full CSV export on every tier — no gate, no support ticket.

Every card above describes intent, not a shipped surface. Read them as a design brief we have published early so you can tell us it is wrong.

Limits

What this does not do

The fastest way to lose someone is to let them find the edge on their own. So here it is up front.

Neither the REST API nor the MCP server is available yet. Both are planned, and we are not promising a date. The integrations page carries the same status, and anything that ships gets a dated entry in the changelog.
The MCP server will be read-only by design: it will query your workspace, and it will not be able to create, change or delete anything in it or reach outside your own data.
The API will be scoped to your workspace and will not proxy your phone system. To change routing, numbers or anything else about the call itself you will still use that system's own API.
Keys will be org-scoped, with scopes and revocation and no account-wide master key. That is a design commitment we have not shipped yet, not something you can test today.
We are not claiming to be first or only here. Several other vendors already ship MCP servers.

More of the platform

The other four parts

Every call, not a sample

Call analysis In build

Every call gets a verdict.

Read

What people actually called about

Demand intelligence Planned

Hear what every caller wanted — including the things you don't sell yet.

Read

Coach from evidence, not memory

Team performance Planned

Find the questions your team couldn't answer.

Read

One place for all of it

Tracking & revenue In build

Keep track of everything, in one place you can audit.

Read

Run it against one month of your own calls

Connect a source and check the reading against the recordings yourself. That is the only test of this that means anything.

Start free Who it is for