Reverbic

Docs / Developers

API & integrations.

Reverbic exposes your meeting knowledge two ways: the MCP server, for agents that should query it directly, and the CLI, for work you drive from a terminal. Both authenticate with tokens you issue and revoke yourself.

Read-only for now

The REST API reads your workspace; it cannot yet create meetings or upload audio. Recording and processing stay in the apps and the CLI. The internal endpoints under /api serve the web, desktop, and mobile clients and are not a supported integration surface — they change without notice. If you need writes, tell us what you are building at hello@reverbic.ai.

REST API

Base URL https://reverbic.ai/v1. Bearer authentication with the same API keys as the MCP server. Every response is JSON; list endpoints share one envelope.

curl https://reverbic.ai/v1/me \
  -H "Authorization: Bearer $REVERBIC_API_KEY"
GET
/v1/me

Identify the calling key: its organization, plan, expiry, and effective scopes. The first call to make when wiring up an integration.

scope: meetings:read

GET
/v1/meetings

List meetings, newest first.

scope: meetings:read · query: limit, offset, status, q

GET
/v1/meetings/{id}

One meeting with its key points, action items, and decisions. Includes transcript text when the key also holds transcripts:read.

scope: meetings:read

GET
/v1/meetings/{id}/transcript

Full transcript as timestamped segments, with speaker labels when the meeting was processed with speaker detection.

scope: transcripts:read

GET
/v1/actions

Action items across every meeting in the organization.

scope: tasks:read · query: limit, offset, completed, meeting_id

GET
/v1/decisions

Decisions captured across meetings.

scope: decisions:read · query: limit, offset, meeting_id

List envelope

{
  "object": "list",
  "data": [ /* … */ ],
  "has_more": true,
  "limit": 25,
  "offset": 0
}

Errors

Errors return the matching HTTP status with a typed body. type is stable and safe to branch on; message is for humans and may change.

{
  "error": {
    "type": "forbidden",
    "message": "This API key is missing the required scope: transcripts:read",
    "required_scope": "transcripts:read"
  }
}

unauthorized 401 · forbidden 403 · not_found 404 · invalid_request 400 · server_error 500

MCP server

A Model Context Protocol server over Streamable HTTP, speaking JSON-RPC 2.0 at protocol version 2025-03-26. Point any MCP-aware client at it and your agent can query meetings mid-task instead of asking you to paste.

POST https://reverbic.ai/api/mcp
Authorization: Bearer <your-api-key>
Content-Type: application/json

The MCP setup guide has paste-ready configuration for Claude, Cursor, and Codex. Requires a Team plan or above.

Tools

list_meetingsmcp:read:meetings

List recent meetings. Returns id, title, status, duration, created_at, and summary.

limit (number, default 25, max 100) · status (completed | processing | failed)

get_meetingmcp:read:meetings

Get one meeting with its summary, key points, action items, and decisions. Includes the full transcript when the key also holds mcp:read:transcripts.

id (string, required) — meeting UUID

search_meetingsmcp:read:meetings

Search meetings by title or summary substring.

query (string, required) · limit (number)

list_action_itemsmcp:read:tasks

List action items across every meeting in the organization.

completed (boolean) · limit (number)

list_decisionsmcp:read:decisions

List decisions captured across meetings.

limit (number)

API keys and scopes

Create keys in Settings → Integrations. One key works for both the REST API and the MCP server — scopes describe what data a key may read, not which protocol it speaks. Keys are scoped to your organization. The full key is shown once at creation, so store it then; only its prefix is retained afterwards. Revoke at any time from the same screen.

Keys issued before the REST API shipped store the older mcp:read:* scope names. Those keep working everywhere and map one-to-one onto the names below — check /v1/meto see a key's effective scopes.

meetings:read

Meeting metadata, summaries, key points, action items, and decisions.

transcripts:read

Full transcript text and segments. Grant only when the caller needs exact wording.

tasks:read

Action items across meetings.

decisions:read

Decisions across meetings.

Note

Grant transcripts:read deliberately. Without it a caller can work from summaries and decisions but never sees verbatim discussion — often the right default for a shared workspace.

CLI

rvb distills a file or piped text into a spec without leaving your shell. It authenticates against your account rather than an API key, and can use your active Context Pack.

rvb login
cat standup.txt | rvb distill --format claude --copy

Formats are claude, cursor, and codex. Full command reference on the CLI page.

Set up MCPBack to Docs