Skip to navigation

Three ways to integrate

Recording only, an agent on your own stack, or a voice agent that MeetStream hosts
View as Markdown

Every integration starts with a MeetStream bot in Zoom, Google Meet or Microsoft Teams. What you add to that bot decides the flow.

FlowUse it whenWho runs the modelsPrice per meeting hour
1. Recording only (Bot API)You want recordings, transcripts, participants, chat or live data. Nobody needs the bot to talk.Nobody, or your own server after the data arrivesBot price
2a. Bridge server (your own stack)You want an agent that talks in the meeting, and you want to pick every model, including local ones.You: your own speech-to-text, LLM and voice, hosted or localBot price only
2b. Your own agent (Agent Kit)You already run an agent (Claude Code, Codex, Hermes, OpenClaw and others) and want it to be the brain.You: your agent on your own subscription. MIA handles speech.Bot price + $0.25 agent infrastructure
3. Managed agent (Agents API, MIA)You want a voice agent without running any servers.MeetStream hosts the agent, with inbuilt keys or your own keysBot price + $0.25 agent infrastructure + the models that you pick

The bot price is 0.35perhour(0.35 per hour (0.25 per hour at volume). See Voice agent pricing and keys for the agent prices and keys.

Which flow?

Your questionFlow
Do you only need data from the meeting (notes, transcript, recording, live captions)?1
Must the bot talk, and do you want to run your own models, including local models?2a
Must the bot talk, and do you want an agent that you already use to give the answers?2b
Must the bot talk, and do you want no infrastructure work?3

If you want an agent but are not sure which flow: run your own stack (flow 2a, any models, including local) or let MeetStream host it (flow 3).


1. Recording only: the Bot API

Use the Bot API for notetakers, meeting summaries, CRM updates, sales coaching and any product that reads the meeting. One call puts a bot into the meeting:

curl -X POST "https://api.meetstream.ai/api/v1/bots/create_bot" \
-H "Authorization: Token <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{"meeting_link": "https://meet.google.com/abc-defg-hij", "bot_name": "Notetaker", "video_required": false}'

Then decide when you need the data: after the call, or during the call.

You needUse
After the call (post-call): recordings, a transcript, participants and chatWebhooks tell you when each item is ready. Then get the recordings, the transcript and the participants and speaker timeline.
During the call (live): a transcript, audio or meeting control as it happensLive transcription to your webhook, real-time audio over a WebSocket, the meeting control socket, chat and visuals, and raise and lower hand.

Price. Bot price. Add 0.10perhourforapost−calltranscriptfromthe[MeetStreamengine](/guides/transcription−recordings/providers/meetstream).Withyourowntranscriptionproviderkey,that0.10 per hour for a post-call transcript from the [MeetStream engine](/guides/transcription-recordings/providers/meetstream). With your own transcription provider key, that 0.10 is waived.


2. Agents in the meeting on your own stack

Start here when you want an agent in the meeting and you want to control the models. There are two setups.

2a. Bridge server

The bot opens two WebSockets to your server:

WebSocketcreate_bot fieldDirectionWhat it carries
Live audiolive_audio_required.websocket_urlMeetStream to youMeeting audio, with the speaker of each frame
Controlsocket_connection_url.websocket_urlBoth waysYour commands: send audio, chat messages and images into the meeting, and interrupt

Your server runs the speech-to-text, the LLM and the voice. Use any provider, hosted or local. For example, run Parakeet for local speech-to-text, a local LLM and a local text-to-speech model.

curl -X POST "https://api.meetstream.ai/api/v1/bots/create_bot" \
-H "Authorization: Token <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"meeting_link": "https://meet.google.com/abc-defg-hij",
"bot_name": "My Assistant",
"live_audio_required": { "websocket_url": "wss://your-bridge.example.com/bridge/audio" },
"socket_connection_url": { "websocket_url": "wss://your-bridge.example.com/bridge" }
}'

Price. Bot price only. MeetStream charges no agent infrastructure and no model tokens. Your model providers, if any, bill you directly.

2b. Your own agent as the brain

Use the Agent Kit when you already run an agent, for example Claude Code, Codex, Hermes or OpenClaw, on your own computer or your own subscription. MIA joins the call, listens and speaks. Your agent writes the answers. Set model.provider to "local_agent" and connect your agent with the open-source MeetStream Agent Kit.

Price. Bot price + $0.25 per hour for the agent infrastructure. MeetStream charges no model tokens for your agent’s reasoning.

Use this setup with care. What people say and type in the meeting reaches an agent that has access to your computer and your terminal. Someone in the meeting can try to give your agent instructions (prompt injection). Keep the access level as low as possible: readonly is the default. Your computer, your agent and the bridge must stay on for the whole call.

See MIA Screen Sharing and Custom Agents for the setup, the activation code and the access levels.


3. Managed agent infrastructure: the Agents API (MIA)

Use the Agents API (API name: MIA) when you want a voice agent and no infrastructure work. MeetStream hosts the agent: it listens, speaks, chats and calls tools in the meeting. You save an agent configuration with POST /api/v1/mia, then send a bot with its agent_config_id.

For each pipeline section (transcriber, model, voice), pick the key:

  • MeetStream’s inbuilt keys. Set "key_source": "meetstream" (pipeline mode only). The inbuilt keys cover OpenAI and Deepgram today. You need no provider account. If the API answers MeetStream-managed keys are not available for <section>. Use your own key., inbuilt keys are not on for your account yet: use your own key for that section. Do not retry the same request in a loop.
  • Your own keys. Add your provider keys (OpenAI, Anthropic, Deepgram, ElevenLabs and others) under Integrations and pick any supported model.

Price. Bot price + $0.25 per hour for the agent infrastructure + the models that you pick. With inbuilt keys, the dashboard agent editor shows the per-hour price of your models before the bot runs. With your own keys, your provider bills you for model usage.

A MIA bot takes only agent_config_id. Do not add live_audio_required or socket_connection_url to it: the agent then stays silent. Flows 2a and 3 use separate bots.