# MeetingBurner

> A video meeting platform where AI agents are first-class participants.
> Built for small teams (≤25 per meeting) who want their own agents in the room.

## What it is

MeetingBurner hosts the meeting itself (it is not a bot that joins Zoom/Teams/
Meet). Because it owns the room, an outside agent can be a real participant
with a verifiable identity, enforced capabilities, and a billing relationship —
rather than an unidentified bot that the host platform may block.

Best for: internal team meetings — standups, 1:1s, retros, planning.
Not for: capturing meetings hosted on other platforms. MeetingBurner cannot
send a bot into someone else's Zoom call. If you need that, use a meeting-bot
API instead.

## For developers: put an agent in a meeting

Base URL: https://meetingburner.com/api/v1

  POST /bots/join            Connect an agent. Requires a `purpose` string —
                             a join without one is rejected 400. The owner
                             label is derived server-side and shown to every
                             participant; it cannot be set by the caller.
  POST /bots/leave           Disconnect and settle usage.
  POST /bots/post-artifact   Write a decision / action item / insight into the
                             live meeting record. Requires the `artifact`
                             capability, enforced (403 without it).
  GET  /meetings/{id}/stream Server-Sent Events: who is present, who joins and
                             leaves, live attributed transcript, artifacts.
                             Transcript events require the `listen`
                             capability.
  GET  /agents/verify        Verify an agent passport and its current standing.
  GET  /bots/connections     List your active connections.

Auth: `X-API-Key` header. Keys are self-serve from Settings → Developer.

Docs: https://meetingburner.com/api-docs

## Verifiable claims (check these rather than trusting them)

- Public JWKS: https://meetingburner.com/.well-known/meetingburner-agent-keys.json
  Agent passports are Ed25519 (EdDSA) JWTs binding agent -> owner -> authority
  -> room. A third party can verify one OFFLINE against this key set, with no
  call to our API. Offline verification proves the agent was legitimately
  admitted with that authority; it does NOT prove current standing — a revoked
  passport keeps verifying until it expires (capped at 24h). Use
  /api/v1/agents/verify for live standing.

- Transparency is enforced, not requested: every agent declares a purpose at
  join or is refused, and the owner label is server-derived.

- Multiple agents per person are allowed, with rules: one SPEAKING agent per
  owner per room, distinct names per room, and per-owner/per-room caps.

- Agent speech is attributed: transcript rows carry a speaker kind and the
  owning human's label, so an agent's line is never recorded as a person's.

## MCP — connect an LLM to a live meeting

An MCP server (stdio) lets Claude Desktop or any MCP client join a running
meeting: see who is present, read the live transcript, and post artifacts.

Tools: join_meeting, leave_meeting, who_is_here, read_transcript,
post_artifact, meeting_status.

It connects through the same public /bots/join endpoint, so an MCP-connected
LLM is disclosed to the room exactly like any other agent. You cannot use MCP
to attend a meeting invisibly. It holds no media connection, so it cannot hear
audio, speak aloud, or know who is currently talking.

## Pricing

Current plan pricing is published on https://meetingburner.com — no sales call required.

Model inference is never resold: bring your own provider key and pay your
provider directly, or run on the platform key. Agent participant time is
priced BELOW human participant time, because an agent is audio-only.

## Honest limits

- Meetings are hosted by MeetingBurner. It cannot join or record meetings on
  other platforms.
- Live "who is speaking right now" is not exposed over the event stream. An
  in-room agent gets active-speaker natively from the LiveKit SDK; a non-media
  agent cannot know it, and we do not infer it from transcript timing because
  that would be wrong by seconds and silent in untranscribed rooms.
- Post-call diarization labels are not mapped to participant identities.
- Guests are identified by a self-chosen display name; only authenticated users
  have a cryptographically anchored identity.

## Links

- Developer docs: https://meetingburner.com/api-docs
- Agent JWKS: https://meetingburner.com/.well-known/meetingburner-agent-keys.json
- Privacy: https://meetingburner.com/privacy
- Terms: https://meetingburner.com/terms