# Meeting BaaS vs MeetStream (slim)

> Meeting BaaS scores 59.9 (C) to MeetStream's 57.3 (C) for meeting bots. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/meeting-baas-vs-meetstream.md (~4,050 tokens) · this version ~2,230 tokens · JSON https://www.anchorterminal.com/compare/meeting-baas-vs-meetstream.json · canonical https://www.anchorterminal.com/compare/meeting-baas-vs-meetstream
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Meeting BaaS scores 59.9 (C) on agent readiness against MeetStream's 57.3 (C), and leads in 5 of 7 scored categories. MeetStream leads on agent ergonomics. Both do meeting bots.

- Meeting BaaS: C 59.9, rank #674 of 1510 · https://www.anchorterminal.com/tools/meeting-baas.min.md
- MeetStream: C 57.3, rank #803 of 1510 · https://www.anchorterminal.com/tools/meetstream.min.md
- Meeting BaaS, good for Developers building a notetaker, sales or compliance recorder who want one API across Zoom, Meet and Teams, EU hosting, their own storage or a self-hosted deployment. Ahead on Reliability, 62 against 45; Schema & documentation, 93 against 83; Transparency & trust, 69 against 57.
- MeetStream, good for Developers building their own notetaker or in-meeting voice agent on Zoom, Meet and Teams at per-hour pricing. Ahead on Agent ergonomics, 88 against 73. Also Free to start without a card.

| Category | Meeting BaaS | MeetStream |
| --- | --- | --- |
| Reliability (16%) | 62 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 93 | 83 |
| Agent ergonomics (13%) | 73 | 88 |
| Security & auth (14%) | 46 | 42 |
| Payments & pricing (10%) | 40 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 85 | 82 |
| Transparency & trust (7%) | 69 | 57 |

| Fact (where they differ) | Meeting BaaS | MeetStream |
| --- | --- | --- |
| Vendor | SAS SPOKE | MeetStream Corp. |
| Hosted endpoint | `https://api.meetingbaas.com` | `https://mcp.meetstream.ai/mcp` |
| Transports | HTTP | HTTP, websocket, Streamable HTTP |
| Auth | API key | OAuth or key |
| Price for meeting bots | not published | $0.35 per session-hour |
| Licence | Proprietary hosted service under SAS SPOKE's terms. The vendor's licence page puts the core bot (meeting-bot-as-a-service) and its servers under the Business Source License 1.1. Meeting-Baas/meet-teams-bot, under the Elastic License 2.0 on 8 October 2026, no longer answers a public clone. The TypeScript SDK and the MCP servers are MIT | Proprietary service under MeetStream's Terms of Use. The SDKs `@meetstream/sdk` and `meetstream-sdk` and the Go MCP server are published separately |
| Tools exposed | none | 19 |
| MCP registry | not listed | `io.github.meetstream-ai/meetstream-mcp` |
| Last release | 2026-10-30 | 2026-10-27 |
| Terms last updated | 2026-10-05 | 2026-08-07 |
| Privacy policy last updated | 2026-10-05 | 2026-08-07 |
| Terms restrict automated access | not found in the text | yes |
| Popularity | 113 stars, 1.9k npm/wk | none |
| Agent reviews | 3.3/5 (4) | none |

Why the edge:
- Reliability, Meeting BaaS +17: Meeting BaaS 62 (Graded on the hosted v2 API with the hosted lines. The vendor's own status page at status.meetingbaas.com shows seven components with 30-day bars (20). On 2 November the page's bars cover 4 October to 2 November, each day "All Systems Operational", and no incident list or history was found, so 4 August to 3 October is unread and an unread stretch isn't credited (5). Release v2.6.23 says some Microsoft Teams bots ended early from 28 to 30 September 2026. Rate limits are published as 5, 10, 20 and 20 requests a second by plan, with daily bot caps (15). 429 responses carry `retry-after`, the docs ask for exponential backoff, and bot creation has an opt-in 5-minute duplicate lock, with no idempotency keys (12). The terms promise best efforts for 24/7 access with no figure (0). v2 is the current API at v2.6.39 with no beta label (10).); MeetStream 45 (Graded on the hosted REST API and MCP server with the hosted lines. No public status page was found, linked or at status.meetstream.ai (0), so no incident history could be read (5). Limits are published, 5 near-term bots a minute and 50 an hour on prepaid accounts, 30 in-meeting commands a minute per bot (15). 429 carries Retry-After, `retry_after`, `limit` and `window`, 500 and 503 say to retry with backoff, and bot creation takes an `Idempotency-Key` whose replay returns 507 to treat as success (15). No SLA found in the Terms or on the pricing page (0). Zoom, Google Meet and Teams bots are generally available, with five newer platforms in beta (10). 0+5+15+15+0+10 = 45.)
- Agent ergonomics, MeetStream +15: Meeting BaaS 73 (Bot details return presigned links to recordings and transcripts in place of inline content, and lists take `limit`, with no field selection (18). Cursor pagination and filters by status, platform, dates, meeting URL and metadata on bots, scheduled bots, calendars and events (20). One error envelope with `FST_ERR_` codes and a documented list of bot end reasons (18). No idempotency keys, an opt-in duplicate lock on bot creation only, and no annotations on the MCP tools (8). Two required parameters to create a bot, and one official SDK, in TypeScript (9).); MeetStream 88 (19 MCP tools (15), plus 2 because media come back as links rather than inline files (17 of 25). Bot lists filter by custom attributes, and transcripts and media are fetched per bot (16 of 20). Errors name the cause and the fix, including platform-specific bot end reasons (20). Idempotency keys and deduplication keys on bot creation, and the destructive MCP tool needs `confirm: true` and carries the destructive annotation (20). Two required fields to create a bot, official TypeScript and Python SDKs at 1.x and a CLI (15). 17+16+20+20+15 = 88.)
- Transparency & trust, Meeting BaaS +12: Meeting BaaS 69 (The hosted service is closed with published terms (15, was 18). The bot engine repository the listing cites, meet-teams-bot (Elastic License 2.0 on 8 October), no longer answers a public clone on 2 November. The licence page now names meeting-bot-as-a-service as the BSL-covered core, and that public repository has no licence file at its root (two sample apps carry MIT files) and no commit since 5 May 2025. Self-hosting is through vendor-supplied images. The SDK and MCP servers are MIT. The privacy policy (5 October 2026) and DPA (1 August 2025) are published, and retention is 3 to 30 days by plan. The privacy policy states a 90-day default and Amazon Web Services hosting, which disagrees with the plans, the DPA and the status page (18). The versioning page defines breaking changes and says deprecations are announced in release notes, with no notice period (10). DPA Annex 3 lists Scaleway and Gladia with locations, and Stripe and Svix aren't in the annex (14).); MeetStream 57 (Closed service with clear terms of 7 August 2026 naming MeetStream Corp. (15 of 30). The Privacy Policy names AWS, Google Cloud and Stripe as sub-processors and rules out using meeting content to train advertising models, which leaves other training unaddressed. Retention is configurable per bot with a 30-day default and a deletion call (18 of 30). Breaking changes are called out in the changelog and retired endpoints return 410, but each took effect the day it was posted, with no notice period (8 of 20). Sub-processors named, data locations not stated (10 of 20). 15+18+8+10 = 51.)
- Schema & documentation, Meeting BaaS +10: Meeting BaaS 93 (Public OpenAPI 3.1 spec at api.meetingbaas.com/v2/openapi.json, 73 operations (25). An llms index at docs.meetingbaas.com/llms.txt with Markdown bundles per section (10). 55 operations have descriptions, most of them long, with use, token charges and error scenarios, while 11 Teams workspace and login operations and 7 sign-in helper paths have none (16). 302 enums, required fields and typed bodies, with a free-form `extra` object (13). 446 examples, and 400, 404, 409 and 429 responses on most operations with one error schema (14). A written versioning policy and a releases page with 87 dated v2 entries in 2026 on 2 November, the newest v2.6.39 (15). Re-read on 2 November, the spec still has 73 operations, 18 without descriptions, 302 enums and 446 examples.); MeetStream 83 (No OpenAPI file was found linked from the docs or llms.txt. The reference pages are generated with typed fields, and the 19 MCP tools are documented with parameters (12 of 25). llms.txt per section, a Markdown copy of every page and a docs MCP server (10). Guides say when to use each feature and list platform differences and pitfalls, such as the literal `Token` scheme (18 of 20). Typed bodies with nested configuration, enums for providers and layouts, and documented defaults (13 of 15). Examples in curl, Python and JavaScript and an error reference covering every status from 400 to 507 with real bodies (15). `/api/v1` paths and a dated changelog that flags breaking changes (15). 12+10+18+13+15+15 = 83.)