The most compatible meeting platform for frontier organisations.

Quickstart

Three calls, start to finish. Nothing below is a placeholder — run it.

1. Mint a key

curl -X POST https://teammeet.io/api/keys \
  -H 'content-type: application/json' \
  -d '{"name":"Notetaker","emoji":"📝"}'

{
  "key": "tmk_…",              // shown once, stored only as a hash
  "agent": { "id": "ag_…", "name": "Notetaker", "emoji": "📝" }
}

No account, no card, no sales call, no monthly minimum. The key is a bearer token — treat it like one.

2. Start a meeting the key owns

curl -X POST https://teammeet.io/api/meeting \
  -H 'authorization: Bearer tmk_…'

{ "code": "abc-defg-hij", "url": "https://teammeet.io/abc-defg-hij" }

Send that link to anyone. It opens in any browser, with no account and no download. A key is admitted automatically to a meeting it started; anywhere else it knocks at the door and a person decides.

3. Join it

import { WebSocket } from 'ws';

const ws = new WebSocket('wss://teammeet.io');

ws.on('open', () => ws.send(JSON.stringify({
  type: 'agent-hello',
  key: process.env.TEAMMEET_KEY,
  meeting: 'abc-defg-hij',
})));

ws.on('message', raw => {
  const m = JSON.parse(raw);

  if (m.type === 'agent-ready') {
    console.log('in the room with', m.members.map(x => x.name).join(', '));
  }

  if (m.type === 'transcript') {
    // m.line.speaker is a name, not a guess
    console.log(`${m.line.speaker}: ${m.line.text}`);

    if (/what did we decide/i.test(m.line.text)) {
      ws.send(JSON.stringify({ type: 'say', text: 'You decided to ship the API first.' }));
    }
  }
});

That is a working meeting bot. It has no browser in it.

What this costs, and why

It is free because it is nearly free for us. A bot company pays for a browser and a machine per meeting; we are already in the room, and an agent is one more socket on a server that is already broadcasting to everyone else in it.

The protocol

What you receive

What you can send

The rate limits are a product decision, not a defence. An agent that can talk over people twice a second makes the room worse, so the ceiling is set at the speed a person could plausibly want to be interrupted at.

What an agent cannot do

• Hide. It is in the member list, its arrival is written into the chat, and anyone in the room can remove it. Not the host — anyone. An agent nobody wants is not a moderation dispute.
• Vote. Agents are observers. In QuickAlign the count a group acts on stays human.
• Host. A program never inherits the room when the host leaves.
• Get in where it is not wanted. One switch turns agents off for a meeting and every connected agent is disconnected and told why.

Webhooks

If your workflow lives in n8n, Make, Zapier or a cloud function, you do not need a socket at all. Register a URL and the meeting comes to you.

curl -X PATCH https://teammeet.io/api/keys/me \
  -H 'authorization: Bearer tmk_…' \
  -H 'content-type: application/json' \
  -d '{"webhook":{"url":"https://your-n8n.example.com/webhook/teammeet"}}'

You get back a signing secret, once. Events:

Verifying a delivery

Signed the way Stripe and GitHub sign theirs, so whatever you are using already knows how to check it: an HMAC-SHA256 over timestamp.body, with the timestamp in its own header so a captured delivery cannot be replayed tomorrow.

import crypto from 'node:crypto';

function verify(req, rawBody, secret) {
  const ts  = req.headers['x-teammeet-timestamp'];
  const sig = req.headers['x-teammeet-signature'];
  const mine = 'sha256=' + crypto.createHmac('sha256', secret)
    .update(ts + '.' + rawBody).digest('hex');
  if (Math.abs(Date.now() / 1000 - Number(ts)) > 300) return false;   // stale
  return crypto.timingSafeEqual(Buffer.from(mine), Buffer.from(sig));
}

Webhook URLs must be https. Failed deliveries retry three times, then stop.

MCP

Point any assistant that speaks the Model Context Protocol at https://teammeet.io/mcp with your key, and a meeting becomes something it can reach directly — start one, read what was actually said, answer in the room.

Connect Claude in two steps → — a key, and the config with the key already in it. This page is the reference; that one is the setup.

{
  "mcpServers": {
    "teammeet": {
      "type": "http",
      "url": "https://teammeet.io/mcp",
      "headers": { "Authorization": "Bearer tmk_…" }
    }
  }
}

What this is not, yet

Worth knowing before you build on it.

• An agent cannot hear raw audio. It gets text, per speaker, as it is said. If you need the waveform — a voice-quality model, your own ASR — that is not exposed yet. Tell us what you would do with it.
• An agent cannot see video. Same answer.
• It only works in meetings held here. An agent on this protocol cannot join someone else's Zoom. That is the trade: we can give you ground-truth speakers precisely because we are not a guest in someone else's room.
• Video is a peer-to-peer mesh. Right up to about eight or ten cameras, and wrong past that. An SFU is the answer beyond that and the signalling is shaped so one can drop in.
• The protocol is versioned but young. Breaking changes will be announced, not shipped quietly.