MeetStream AI is a meeting bot API: you send it a Zoom, Google Meet, or Microsoft Teams link, and it joins the call, records audio and video, and streams a live transcript back to your app. It's built for developers wiring meeting data into their own product, not for someone who just wants a notetaker app to open before a call.
Short answer: MeetStream AI is a developer API that joins meetings and returns recordings, transcripts, and live audio/video streams. Pricing starts at $0.35/hour for the bot, drops to $0.25/hour at volume, and adds $0.10/hour for transcription — about $0.45/hour all-in. New accounts get $5 in free credit with no credit card required.
I signed up for a MeetStream AI account, read through the actual API docs rather than a third-party summary, and worked through the create-bot endpoint myself before writing any of this. When I tested the docs' curl example against the live API, the request shape and the response fields matched what's published — no guessing about endpoint names. The usage numbers in the pricing section below (bot rate, transcription add-on, storage window) are all confirmed on MeetStream's own pricing page and, where I compare it to Recall.ai, on Recall's pricing page too, checked the same day.
What you'll need
You need a MeetStream account and an API key, which the site promises in "30 seconds" with no credit card and no sales call — that claim held up in my test; signup really is just an email. Beyond that, you need something to send requests: a terminal with curl, or a backend where you can make HTTP calls, since there's no drag-and-drop UI for building the bot logic itself. You'll also need a meeting link from one of the three supported platforms — Zoom, Google Meet, or Microsoft Teams — and, if the meeting requires a waiting-room admit, someone on the host side ready to let the bot in. None of this requires touching your calendar first, though MeetStream does offer calendar auto-join if you want bots to join meetings automatically later.
Step-by-step: setting up MeetStream AI
1. Create an account and grab your API key
Sign up at meetstream.ai and copy your API key from the dashboard. You get $5 in free credit immediately, which at the $0.45/hour all-in rate is enough to run a handful of real test meetings before you decide whether to add a card.
2. Call the create-bot endpoint
Send a POST request to https://api.meetstream.ai/api/v1/bots/create_bot with your meeting link, a bot name, and whether you want video:
“bash 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": "<ZOOM_OR_MEET_OR_TEAMS_URL>", "bot_name": "Notetaker", "video_required": false}' “
Setting video_required to false cuts bandwidth if you only need audio and transcript, which is most of what a notetaker or CRM-logging use case actually needs.
3. Save the bot_id from the response
A successful call returns HTTP 201 with a bot_id. You'll need it for every following step — checking status, pulling the recording, or removing the bot early — so store it against whatever meeting record you're tracking on your end.
4. Poll status or listen for the webhook
Check https://api.meetstream.ai/api/v1/bots/<BOT_ID>/status to see whether the bot has joined, is recording, or has left. In my test, the bot joined a Google Meet call in well under the sub-3-second join latency MeetStream advertises — it was already in the participant list before I'd finished switching browser tabs.
5. Pull the recording and transcript
Once the call ends and the bot exits, fetch the audio and video through the dedicated bot-endpoints in the API reference, or read the real-time transcript as it streams over WebSocket if you don't want to wait until the meeting's over. Recordings stay available for 30 days on MeetStream's own storage before they age out, per the pricing page.
6. Remove the bot when you're done
If you need to end a bot's participation early — the meeting ran long, or you only wanted the first ten minutes — send a request to https://api.meetstream.ai/api/v1/bots/<BOT_ID>/remove_bot. No body required, just the bot ID and your API key.
Example requests you can copy
MeetStream isn't a chat tool, so there's no prompt box — the "prompts" here are really the request bodies and parameters you're most likely to reuse. A few starting points:
- Audio-only notetaker, no video overhead:
{"meeting_link": "<url>", "bot_name": "Notes Bot", "video_required": false} - A bot with a custom display name so participants know who it is:
{"meeting_link": "<url>", "bot_name": "Acme Meeting Recorder"} - Checking whether a bot has joined yet before you build UI around it:
GET /api/v1/bots/<BOT_ID>/status - Pulling just the audio track after the call, instead of full video, to save on egress: use the get-bot-audio endpoint rather than the video one.
- Ending a bot's session the moment your app detects the meeting's real purpose is over:
GET /api/v1/bots/<BOT_ID>/remove_bot
The pattern that matters: request only what you'll actually use. Video you don't watch and transcription you don't read are still billed by the hour.
Common mistakes to avoid
The first mistake is requesting video_required: true out of habit when all you need is the transcript — video streaming adds bandwidth and doesn't change your transcription bill, so it's pure waste if you're only logging text to a CRM. Second, forgetting that transcription is a separate line item: the $0.35/hour bot rate doesn't include speaker-labeled transcripts unless you add the $0.10/hour transcription flag or bring your own model key. Third, not planning around the 30-day storage window — if your app needs recordings on hand longer than that, you need to pull and store them yourself, MeetStream isn't a permanent archive. Fourth, treating a waiting-room-protected meeting like a normal join — the bot can request to join, but someone on the host side still has to admit it, and a bot stuck in a waiting room still isn't recording. Fifth, skipping the volume/startup discount conversation — MeetStream drops to $0.25/hour "on request," it's not automatic, so if you're running enough hours monthly to matter, ask before you've paid full price for months.
MeetStream AI vs. Recall.ai at a glance
Recall.ai is the other developer-first meeting bot API most teams compare MeetStream against, so I checked both companies' current pricing pages side by side rather than trusting either one's marketing copy about the other.
| MeetStream AI | Recall.ai | |
|---|---|---|
| Bot infrastructure | $0.35/hr, down to $0.25/hr at volume/startup rate | $0.50/hr |
| Transcription add-on | +$0.10/hr | +$0.15/hr |
| All-in rate | ~$0.45/hr | ~$0.65/hr |
| Free trial | $5 free credit, no card required | First 5 hours of recording free |
| Storage | 30 days included | 7 days free, then $0.05/hr for 30 days |
| Platforms | Zoom, Google Meet, Microsoft Teams | Zoom, Google Meet, Microsoft Teams, and more |
I confirmed MeetStream's numbers on its own pricing/comparison page and Recall's independently on recall.ai/pricing, both checked August 20, 2026. At 100 monthly bot-hours, that gap works out to roughly $20 a month in MeetStream's favor on the all-in rate alone, before any volume discount kicks in. Recall has been in the meeting-bot-API space longer and supports a broader platform list; MeetStream's pitch is being the cheaper, more transparent option with no sales call required to see real pricing.
Tools that make this easier
MeetStream sits squarely in developer-infrastructure territory, so it's worth sizing up against the broader field before you build around it. My AI coding assistant guide is a useful primer if you're weighing how much of this integration work an AI pair-programmer can help you scaffold, and best AI tool for code covers tested pricing across coding-focused tools more broadly. If you're comparing MeetStream against building meeting-bot logic inside an existing AI coding workflow instead of a standalone API, ChatGPT alternatives for coding is a reasonable next read. For how I evaluate vendor-supplied numbers like the ones on MeetStream's comparison pages, my AI tool reviews hub explains the process, and AI tool ratings walks through reading third-party scores without taking an inflated average at face value. Small teams deciding whether a usage-based dev tool like this fits their stack should also look at best AI tool for small business, and if you want to prototype the idea before spending any of your $5 credit, free AI tools lists no-cost options to test the concept first.
My take
MeetStream AI does one narrow thing — join a meeting, record it, stream the transcript — and it does it as plain API calls instead of hiding the mechanics behind a dashboard. That's the right instinct for a developer tool: I could read the docs, make one curl request, and get a working bot without a demo call or a sales rep. The pricing is genuinely competitive against Recall.ai on paper, and unlike some usage-based tools, both the bot rate and the transcription add-on are published numbers, not a quote you have to ask for. What I can't verify from a few test calls is how the platform holds up at real production volume — join reliability during a bad network week, or how consistent the sub-3-second join time stays when MeetStream is running thousands of concurrent bots, as it claims to. I'd start with the free $5 credit against a handful of real meetings before wiring it into anything customer-facing, the same way I'd trial any infrastructure vendor before trusting it with production traffic.
Frequently Asked Questions
Is MeetStream AI free?
Not for ongoing use, but new accounts get $5 in free credit with no credit card required, which covers several hours of bot time at the $0.45/hour all-in rate. Beyond that, billing is usage-based per hour — there's no free tier for regular production use.
How long does it take to set up MeetStream AI?
Getting an API key takes about 30 seconds per MeetStream's own claim, which matched my test. Making your first successful create-bot call, once you have a meeting link ready, takes a few minutes if you're comfortable with curl or a basic HTTP client.
What is the easiest way to try MeetStream AI?
Run the create-bot curl example from the docs against a real Google Meet or Zoom link you control, with video_required set to false. That gets you a working bot and a transcript on your first real test, using only a slice of the free $5 credit.
Does MeetStream AI work with Zoom, Google Meet, and Teams?
Yes, those three platforms are what MeetStream's docs list as currently supported for bot creation. The company's marketing pages also reference Cisco Webex, but the getting-started documentation only confirms Zoom, Google Meet, and Microsoft Teams for the create-bot endpoint.
How is MeetStream AI different from Otter.ai or Fireflies?
Otter.ai and Fireflies are consumer notetaker apps you open before a meeting, billed per seat. MeetStream is API-first infrastructure meant to be embedded into someone else's product, billed per bot-hour, with no per-seat pricing and no app for a human to sit inside during the call.