# MeetStream vs Zoom Realtime Media Streams (RTMS) (slim)

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

- Full: https://www.anchorterminal.com/compare/meetstream-vs-zoom-rtms.md (~4,600 tokens) · this version ~2,830 tokens · JSON https://www.anchorterminal.com/compare/meetstream-vs-zoom-rtms.json · canonical https://www.anchorterminal.com/compare/meetstream-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)

Zoom Realtime Media Streams (RTMS) scores 58.3 (C) on agent readiness against MeetStream's 57.3 (C), and leads in 3 of 7 scored categories. MeetStream leads on schema & documentation, agent ergonomics, payments & pricing and maintenance & community. Both do meeting transcripts.

- MeetStream: C 57.3, rank #799 of 1486 · https://www.anchorterminal.com/tools/meetstream.min.md
- Zoom Realtime Media Streams (RTMS): C 58.3, rank #753 of 1486 · https://www.anchorterminal.com/tools/zoom-rtms.min.md
- MeetStream, good for Developers building their own notetaker or in-meeting voice agent on Zoom, Meet and Teams at per-hour pricing. Ahead on Schema & documentation, 83 against 71; Agent ergonomics, 88 against 59; Payments & pricing, 40 against 0; Maintenance & community, 82 against 73. Also Free to start without a card.
- 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 45; Security & auth, 63 against 42; Transparency & trust, 73 against 57. Also No incidents deducted, where MeetStream loses 4 points for them.

| Category | MeetStream | Zoom Realtime Media Streams (RTMS) |
| --- | --- | --- |
| Reliability (16%) | 45 | 67 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 71 |
| Agent ergonomics (13%) | 88 | 59 |
| Security & auth (14%) | 42 | 63 |
| Payments & pricing (10%) | 40 | 0 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 73 |
| Transparency & trust (7%) | 57 | 73 |

| Fact (where they differ) | MeetStream | Zoom Realtime Media Streams (RTMS) |
| --- | --- | --- |
| Vendor | MeetStream Corp. | Zoom Communications, Inc. |
| Hosted endpoint | `https://mcp.meetstream.ai/mcp` | `https://api.zoom.us/v2` |
| Transports | HTTP, websocket, Streamable HTTP | websocket, HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Pay per use | Paid |
| Licence | Proprietary service under MeetStream's Terms of Use. The SDKs `@meetstream/sdk` and `meetstream-sdk` and the Go MCP server are published separately | Proprietary service under the Zoom API Licence and Terms of Use. The `@zoom/rtms` SDK is MIT on npm |
| Tools exposed | 19 | none |
| MCP registry | `io.github.meetstream-ai/meetstream-mcp` | not listed |
| Last release | 2026-10-27 | 2026-10-30 |
| Terms last updated | 2026-08-07 | 2025-07-16 |
| Privacy policy last updated | 2026-08-07 | 2026-09-17 |
| 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 |

Why the edge:
- Payments & pricing, MeetStream +40: MeetStream 40 (No x402, MPP or L402 (0). Per-hour prices are public, $0.35 per bot hour, $0.10 for transcription and $0.05 per GB a month of storage past 30 days (20). $5 free credit with no card required (20). Signup and key creation happen in the dashboard, and the MCP OAuth flow needs a person to approve (0). 0+20+20+0 = 40.); 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.)
- Agent ergonomics, MeetStream +29: 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.); 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.)
- Reliability, Zoom Realtime Media Streams (RTMS) +22: 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.); 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.)
- Security & auth, Zoom Realtime Media Streams (RTMS) +21: MeetStream 42 (A key grants full access to its workspace's bots and data, and workspaces separate keys. MCP sign-in is OAuth, which mints a key per connection. No scopes or read-only keys found (15 of 30). `delete_bot_data` needs `confirm: true` and is marked destructive, and `remove_bot` keeps recordings, with no read-only mode (10 of 20). Transcripts, chat and audio come from meeting participants, and no prompt-injection guidance was found (0). A dashboard bot detail page and signed webhooks, with no audit log of API calls found (5 of 15). ISO 27001 certified (630036), SOC 2 Type 2 under audit, HIPAA with a BAA, a trust centre and HMAC-signed webhooks. No security.txt (404) or bug bounty found (12 of 20). 15+10+0+5+12 = 42.); 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.)
- Transparency & trust, Zoom Realtime Media Streams (RTMS) +16: 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.); Zoom Realtime Media Streams (RTMS) 73 (Closed service under the Zoom API Licence and Terms of Use of 16 July 2025, as for zoom-scheduler (15 of 30). The Privacy Statement (17 September 2026) and Terms of Service say communications-like customer content isn't used to train AI models, with no fixed retention periods, per the zoom-scheduler check; RTMS streams to the customer's own app, which holds the data (18 of 30). Advance, dated notices in the RTMS changelog, such as TLS 1.2 from 15 November 2026 and a V2 preview, beside API terms that let Zoom deprecate without prior notice (14 of 20). The sub-processor list (2 October 2026) names third parties and affiliates with locations, per the zoom-scheduler check (18 of 20). 15+18+14+18 = 65.)
- Schema & documentation, MeetStream +12: 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.); 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.)