MeetingBurner: Meetings for humans. And their agents.

Overview

MeetingBurner has a plain REST API for putting a bot or an AI agent into a live meeting as a disclosed participant, plus a Server-Sent Events stream for reading who is present and what is being said in real time. Any language that can make an HTTP request and read an SSE stream can use it — no SDK to install, and none is required.

Base URL

https://meetingburner.com/api/v1

Quick Start

1. Get Your API Key

Sign up at meetingburner.com/signup, navigate to Settings → Developer, and generate an API key. Set it once in your environment (for example in a .env file you don't commit, or with read -s MEETINGBURNER_API_KEY && export MEETINGBURNER_API_KEY) so it isn't pasted into every command.

2. Join a Meeting

curl -X POST https://meetingburner.com/api/v1/bots/join \
  -H "X-API-Key: $MEETINGBURNER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "roomId": "ROOM_ID",
    "botName": "My Agent",
    "capabilities": ["listen", "artifact"],
    "purpose": "Takes notes and flags open questions"
  }'

ROOM_ID is the last part of the meeting link. To start a meeting from your key instead of the dashboard, call POST /meetings — but first turn on Can create meetings for that key in Settings → Developer; it is off for every key until you do. Either way, your agent joins only after you have joined the meeting yourself.

3. Read What's Happening — No WebRTC Required

curl -N \
  -H "X-API-Key: $MEETINGBURNER_API_KEY" \
  "https://meetingburner.com/api/v1/meetings/ROOM_ID/stream?connectionId=YOUR_CONNECTION_ID"

Plain Server-Sent Events: who is present, who joins and leaves, and the live attributed transcript. Only add a LiveKit connection if your agent publishes or consumes audio — for that, see Bring your voice agent, with complete LiveKit Agents and OpenAI Realtime examples.

Authentication

Every request carries an X-API-Key header. Your key is tied to your MeetingBurner account — a bot can join a meeting only while you, its key's owner, are currently in that meeting yourself, whether as the host or as a participant. Joining before you do fails with owner_not_present.

X-API-Key: $MEETINGBURNER_API_KEY

Agent API

The Bot API endpoints for joining, contributing to, and leaving a meeting.

POST /meetings — set up a meeting you host and get its link back; needs Can create meetings turned on for the key in Settings → Developer (off by default, refused with meeting_creation_not_enabled until then)
GET /meetings — list the meetings this key set up
POST /bots/join — connect as a disclosed agent; requires a purpose string
POST /bots/join-with-code — the same join with no API key: a single-use code the host makes for one meeting with Invite your agent (ten minutes, one use, billed to the host)
POST /bots/post-artifact — write a decision, action item, or insight into the live meeting record
POST /bots/leave — disconnect and settle usage
GET /bots/connections — list your active connections
GET /agents/verify — verify an agent passport and its current standing
GET /account/balance — check your token balance

Meeting Event Stream

GET /meetings/{roomId}/stream is a Server-Sent Events endpoint: presence, joins and leaves, the live attributed transcript, and artifacts. It requires the listen capability from your /bots/join call.

Webhooks

Pass a webhookUrl to /bots/join and MeetingBurner POSTs lifecycle events to it — meeting.ended, bot.disconnected, participant.joined, participant.left. The URL must be HTTPS and cannot point at a private or loopback address.

Deliveries are signed when you configure a webhook secret: the X-MeetingBurner-Signature header carries sha256=<hmac-hex>, an HMAC-SHA256 over ${timestamp}.${rawBody} using your secret, where the timestamp is the Unix-seconds value in the accompanying X-MeetingBurner-Timestamp header. Recompute the signature over the raw body you received, compare it in constant time, and reject anything older than 300 seconds. No signature header is sent for a webhook with no secret configured.

MCP Server

Prefer to connect an LLM instead of writing an agent yourself? See the MCP server section on the Developers page for the config block and full tool reference.

Usage and Tokens

An agent's connection time is charged to the account that owns its API key. Time is rounded up to whole minutes, and charged when the agent leaves or the meeting ends. There are two rates, and which one applies depends on whether the agent speaks.

Text agent (no speak capability, including every MCP agent): 1 token per minute. 10 minutes cost 10 tokens.
Speaking agent (joined with speak): 2.5 tokens per minute, rounded up to whole tokens. A one-minute call costs 3 tokens, and 10 minutes cost 25 tokens.

Before an agent is let in, its owner's balance must cover at least its first minute at its rate. Check the balance with GET /account/balance.

API Documentation