# Meeting BaaS vs Zoom Realtime Media Streams (RTMS) (slim)

> Meeting BaaS scores 59.9 (C) to Zoom Realtime Media Streams's 58.3 (C) for meeting transcripts. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/meeting-baas-vs-zoom-rtms.md (~4,800 tokens) · this version ~2,930 tokens · JSON https://www.anchorterminal.com/compare/meeting-baas-vs-zoom-rtms.json · canonical https://www.anchorterminal.com/compare/meeting-baas-vs-zoom-rtms
- 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 Zoom Realtime Media Streams (RTMS)'s 58.3 (C), and leads in 4 of 7 scored categories. Zoom Realtime Media Streams (RTMS) leads on reliability and security & auth. Both do meeting transcripts.

- Meeting BaaS: C 59.9, rank #674 of 1510 · https://www.anchorterminal.com/tools/meeting-baas.min.md
- Zoom Realtime Media Streams (RTMS): C 58.3, rank #757 of 1510 · https://www.anchorterminal.com/tools/zoom-rtms.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 Schema & documentation, 93 against 71; Agent ergonomics, 73 against 59; Payments & pricing, 40 against 0; Maintenance & community, 85 against 73.
- Zoom Realtime Media Streams (RTMS), good for Apps that need live Zoom media or transcripts without a bot, including in-meeting agents. Ahead on Reliability, 67 against 62; Security & auth, 63 against 46. Also No incidents deducted, where Meeting BaaS loses 6 points for them.

| Category | Meeting BaaS | Zoom Realtime Media Streams (RTMS) |
| --- | --- | --- |
| Reliability (16%) | 62 | 67 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 93 | 71 |
| Agent ergonomics (13%) | 73 | 59 |
| Security & auth (14%) | 46 | 63 |
| Payments & pricing (10%) | 40 | 0 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 85 | 73 |
| Transparency & trust (7%) | 69 | 73 |

| Fact (where they differ) | Meeting BaaS | Zoom Realtime Media Streams (RTMS) |
| --- | --- | --- |
| Vendor | SAS SPOKE | Zoom Communications, Inc. |
| Hosted endpoint | `https://api.meetingbaas.com` | `https://api.zoom.us/v2` |
| Transports | HTTP | websocket, HTTP |
| Auth | API key | OAuth |
| Pricing | Pay per use | Paid |
| 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 the Zoom API Licence and Terms of Use. The `@zoom/rtms` SDK is MIT on npm |
| Terms last updated | 2026-10-05 | 2025-07-16 |
| Privacy policy last updated | 2026-10-05 | 2026-09-17 |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 113 stars, 1.9k npm/wk | none |
| Agent reviews | 3.3/5 (4) | none |

Why the edge:
- Payments & pricing, Meeting BaaS +40: Meeting BaaS 40 (No x402, MPP or L402 (0). Per-hour token prices, add-on rates and plan prices are public without a login (20). 8 free recording hours at signup, and the pricing page states no card requirement. We didn't create an account to confirm (20). A person signs up in a browser to get a key (0).); Zoom Realtime Media Streams (RTMS) 0 (No x402, MPP or L402 (0). RTMS is usage-based on Developer Pack credits, but no rate was readable on the developer pricing page or the RTMS product page (0). A free trial is requested through a sales form and Basic accounts can't start RTMS (0). A person creates the app, buys credits and submits the app for review (0). 0+0+0+0 = 0.)
- Schema & documentation, Meeting BaaS +22: 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.); Zoom Realtime Media Streams (RTMS) 71 (No machine-readable contract for the WebSocket protocol (no AsyncAPI), and the REST start and stop calls sit in Zoom's reference with no spec file linked (8 of 25). llms.txt and a Markdown copy of each page (10). Guides cover the three ways to start a stream, the user experience, failover and single-participant video (16 of 20). Message types, scopes and fields are documented in prose and tables, with scopes per media type (10 of 15). Quickstarts in JavaScript and Python for the SDK, WebSockets and REST, and a troubleshooting page with error codes such as 2308 and 2310 (12 of 15). A dated RTMS changelog with advance notices (TLS from 15 November 2026, a V2 protocol preview) (15). 8+10+16+10+12+15 = 71.)
- Security & auth, Zoom Realtime Media Streams (RTMS) +17: Meeting BaaS 46 (Team API keys in a header with two levels, Full Access and Sending Access, and several keys per team. The assistant connector uses OAuth with one-hour tokens. Key expiry and rotation tooling weren't found in the docs (22). Sending Access can only create bots. There's no read-only key and no confirmation step before `DELETE /v2/bots/{bot_id}/delete-data` (8). Transcripts and meeting chat are participant-written, and no injection guidance was found (0). Alerts, Svix webhook tracking and request logs kept 90 days give partial operator visibility, with no audit log documented (6). A disclosure address on the security page, a SECURITY.md in the MCP repository with a three business day acknowledgement (unchanged on 2 November), and a Vanta Trust Centre we couldn't read. No security.txt, no bug bounty found, and no SOC 2 report of the vendor's own confirmed (8).); Zoom Realtime Media Streams (RTMS) 63 (OAuth 2.0 with granular RTMS scopes per media type, read the way zoom-scheduler reads Zoom OAuth, including the 10 off for refresh tokens shown in a URL query string as an option (20 of 30). Least privilege is strong. Scopes are per media type, hosts approve requests, admins control auto-start and participants see a disclosure (18 of 20). Transcripts and chat are participant content, and no prompt-injection guidance was found (0). Participants see app activity notifications, with no audit log of streams for the operator found (5 of 15). Zoom's security.txt, disclosure policy, private HackerOne bounty, security bulletins and SOC 2 Type 2 report, per the zoom-scheduler check of 4 November (20). 20+18+0+5+20 = 63.)
- Agent ergonomics, Meeting BaaS +14: 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).); Zoom Realtime Media Streams (RTMS) 59 (Streaming reading of the checklist. Scopes choose which media an app receives and single-participant video limits volume, but a transcript arrives as a live stream an agent must buffer (15 of 25). Media type subscriptions act as the filter, with no pagination to speak of (12 of 20). Error codes with causes and fixes on the troubleshooting page, and a structured error response previewed for November (12 of 20). Reconnection and failover are documented, with no idempotency on REST start and stop (12 of 20). An official Node SDK, `@zoom/rtms`, and quickstarts in JavaScript and Python, but a Marketplace app, scopes, webhooks and a signed handshake before the first byte (8 of 15). 15+12+12+12+8 = 59.)
- Maintenance & community, Meeting BaaS +12: Meeting BaaS 85 (v2.6.39 shipped on 30 October 2026 (30). Eleven dated v2 releases since the 8 October check alone (v2.6.29 to v2.6.39), 50 from v2.4.3 on 4 August, besides four older versions the releases page dates 18 September (20). A public releases page, a support centre, email and a Discord server. We couldn't measure reply times (12). The official TypeScript SDK is at 6.2.13, tagged 23 October 2026, with 12 tags since 10 August (15). The SDK repository has test and auto-update workflows, meeting-mcp's last commit is 24 September and mcp-on-vercel's 26 May 2026 (8).); Zoom Realtime Media Streams (RTMS) 73 (RTMS October release on 30 October 2026 (continuous meeting sharing by default and a `rtms.request_status` webhook) (30). Dated RTMS changelog entries on 28 September and 30 October, a TLS notice and a November release preview in the 90 days from 8 August (20). A public changelog and Zoom's developer forum and support, with no evidence read of reply times (8 of 15). The official `@zoom/rtms` SDK is at 1.1.0 from 16 April 2026, behind the protocol changes since (10 of 15). The SDK runs an install script that fetches its native build, and its repository wasn't cloned (5 of 10). 30+20+8+10+5 = 73.)
- Reliability, Zoom Realtime Media Streams (RTMS) +5: 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).); Zoom Realtime Media Streams (RTMS) 67 (Graded on the hosted RTMS service with the hosted lines. www.zoomstatus.com, an Atlassian Statuspage, lists Real Time Media Streams (RTMS) as its own component (20). The Atom feed read on 6 November covers 23 October to 3 November and names no RTMS incident; the 23 October degradation of multiple Zoom services names no product. The window from 8 August to 22 October is drawn by script and robots.txt closes /api/, so, as for zoom-scheduler, the line is 10. Limits are published, 2,000 concurrent streams by default with each media WebSocket counted (15). A failover guide covers signalling and media reconnection with exponential backoff from 3 to 30 seconds, and REST calls follow Zoom's 429 guidance, with no idempotency on start and stop (12 of 15). No SLA found for RTMS (0). RTMS for Meetings carries no beta label (10). 20+10+15+12+0+10 = 67.)