{ "data": { "a": { "slug": "read-ai", "name": "Read AI", "vendor": "Read AI, Inc.", "vendorUrl": "https://www.read.ai", "kind": "mcp", "category": "meeting-capture", "summary": "Read AI is a meeting assistant that records Zoom, Google Meet and Microsoft Teams calls and produces transcripts, summaries and action items. Outside agents reach the reports through a remote MCP server and a REST API, both in open beta.", "url": "https://www.anchorterminal.com/tools/read-ai", "markdownUrl": "https://www.anchorterminal.com/tools/read-ai.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/read-ai.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/read-ai.json", "dns": "read-ai.grade.anchorterminal.com", "license": "Proprietary service under Read AI's terms of service", "transports": [ "streamable-http", "http" ], "remoteUrl": "https://api.read.ai/mcp", "packages": [], "auth": "oauth", "authNotes": "OAuth 2.1 only, with a browser sign-in to a Read AI account. A client registers itself at https://api.read.ai/oauth/register (dynamic client registration) and runs the authorisation code grant with PKCE against authn.read.ai. Scopes are `meeting:read` for the REST API and `mcp:execute` for the MCP server. Access tokens last 10 minutes and refresh tokens are single-use and rotate. Static API keys and client credentials are not supported in the beta. Workspace members need the Downloads setting enabled by an admin, and a token reaches only the reports its user can open.", "pricing": "freemium", "pricingNotes": "The API and MCP server are available on every plan, including Free (5 meeting transcripts a month, no card). Paid plans billed annually are Pro at $15, Enterprise at $22.50 and Enterprise+ at $29.75 a user a month ($19.75, $29.75 and $39.75 billed monthly). Enterprise+ needs five or more licences. Webhooks need Pro or above, and recording playback needs Enterprise or above. No per-call charge is published (checked 2026-10-08).", "priceSummary": "$15 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API reference, the MCP server article, the overview or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 4, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://support.read.ai/hc/en-us/articles/49379985941523-Read-AI-API-and-MCP-Overview", "llmsTxt": "https://www.read.ai/llms.txt", "capabilities": [ "meetings.bot", "meetings.transcript", "meetings.summary", "meetings.recording" ], "tags": [ "official", "hosted", "mcp", "oauth", "closed-source", "beta", "no-card", "llms-txt", "webhooks", "status-page", "soc2" ], "lastRelease": "2026-09-02", "graded": true, "anchor": { "graded": true, "score": 42.4, "grade": "E", "agentReady": false, "rank": 1282, "ranked": true, "rankOf": 1510, "categoryRank": 13, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 6, "payments": 30, "reliability": 27, "schema": 46, "security": 54, "transparency": 64 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "Four MCP tools and three REST endpoints return transcripts, summaries, action items and recording links, and the MCP server can send a bot to a named meeting. Both surfaces are in open beta. Access needs a browser sign-in, access tokens last 10 minutes, and no OpenAPI file, changelog or readable incident history was found.", "bestFor": "An agent working for a person or team that already records meetings with Read AI and wants transcripts, summaries and action items in context.", "strengths": [ "The remote MCP server has four tools, covering list meetings, get meeting, create meeting agent and share meeting report", "The API and MCP server are open to every plan, including the free plan of five meeting transcripts a month with no card", "OAuth 2.1 with dynamic client registration, 10-minute access tokens, rotating single-use refresh tokens and a revocation endpoint", "Creating a meeting agent twice for one meeting returns the existing record, and re-sharing a report sends no duplicate invite", "Webhooks carry an HMAC SHA-256 signature in `X-Read-Signature` and a `request_id` for discarding duplicates" ], "weaknesses": [ "Both the REST API and the MCP server are labelled open beta, with no SLA, no deprecation policy and no dated API change on record since the February 2026 launch", "No static API keys or client credentials. A person signs in through a browser, and a broken refresh chain needs that person again", "No public OpenAPI file, changelog or official SDK was found. The reference is one help centre article", "List calls return at most 10 meetings a page, and the only filter is start time", "The bot can be sent to a meeting through MCP, but no tool removes it, reports its state or controls it during the call" ], "agentNotes": [ "Persist the new refresh token after every refresh. Access tokens expire after 10 minutes and each refresh token works once.", "Request only the fields needed with `expand[]` on the REST API. Transcripts and other expansions slow the response.", "Stay under 100 requests a minute per user and back off on 429. No Retry-After header is documented.", "Confirm with the user before calling create meeting agent or share meeting report. Sharing emails the recipient unless notify is set to no.", "Ask a workspace admin to enable Downloads in Reports \u0026 Sharing first. Without it the API and MCP server return nothing for workspace members." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 42.4 } ], "editorialScores": { "ergonomics": 63, "maintenance": 6, "payments": 30, "reliability": 27, "schema": 46, "security": 54, "transparency": 45 }, "provenanceScore": 82, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://api.read.ai/v1/meetings?limit=5\u0026start_time_ms.gte=1733700000000\" \\\n -H \"Authorization: Bearer $READ_AI_ACCESS_TOKEN\" \\\n -H \"Accept: application/json\"" }, "letme": { "capability": "https://letme.dev/meetings.bot", "tool": "https://letme.dev/read-ai" }, "area": "voice", "unitPrices": [ { "item": "Pro", "unit": "seat-month", "usd": 15, "note": "billed annually, $19.75 billed monthly" }, { "item": "Enterprise", "unit": "seat-month", "usd": 22.5, "note": "billed annually, $29.75 billed monthly" }, { "item": "Enterprise+", "unit": "seat-month", "usd": 29.75, "note": "billed annually, $39.75 billed monthly, five or more licences" } ], "provenance": { "legalEntity": "Read AI, Inc.", "domain": "read.ai", "domainRegistered": "2017-12-16", "endpointOnVendorDomain": true, "terms": "https://www.read.ai/termsofservice", "privacy": "https://www.read.ai/privacy-policy", "statusPage": "https://readai.statuspage.io", "changelog": "", "securityTxt": "valid", "checked": "2026-11-04", "notes": [ "The terms of service (last updated 26 February 2026) name Read AI, Inc., 999 Third Ave, Suite 3300, Seattle, WA 98104.", "The privacy policy was last updated on 29 June 2026.", "The REST API and MCP server answer at api.read.ai and the authorisation server at authn.read.ai, both read.ai subdomains.", "www.read.ai/.well-known/security.txt is RFC 9116 format, expires 18 August 2027 and names vulnerabilities@read.ai and trust.read.ai.", "The registration date (2017-12-16) is carried from the 8 October check, which took it from a registry data service this run doesn't use.", "No changelog for the API or MCP server was found. The dates used are the help centre articles' own edit dates.", "The Trust Centre at trust.read.ai is a Vanta page that renders only with JavaScript, so its documents and sub-processor list were not read.", "Read AI's terms bar robots except for search indexing, so its hosts weren't re-read on 4 November 2026; the terms still read Last Updated February 26, 2026. The status page at readai.statuspage.io wasn't re-read either." ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/read-ai.json", "live": { "slug": "read-ai", "probe": { "target": "https://api.read.ai/mcp", "method": "mcp-initialize", "lastAt": "2026-11-07T19:22:28.931808298Z", "lastOk": true, "lastStatus": 401, "lastMs": 251, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 265, "p95ms24h": 364, "samples24h": 238, "samples30d": 7473, "days": [ { "date": "2026-10-08", "probes": 93, "ok": 93 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://readai.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:23:33.705097958Z" }, "securityTxt": { "url": "https://read.ai/.well-known/security.txt", "state": "valid", "expires": "2027-08-18T00:00:00.000Z", "checkedAt": "2026-11-07T16:00:32.905445025Z" }, "llmsTxt": { "url": "https://www.read.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:43.629020821Z" }, "domain": { "domain": "read.ai", "registered": "2017-12-16", "source": "https://rdap.identitydigital.services/rdap/domain/read.ai", "checkedAt": "2026-11-01T14:14:36.443252371Z" }, "pages": [ { "url": "https://www.read.ai/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:33:32.246975252Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "21db8189c8d4" }, { "url": "https://www.read.ai/termsofservice", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:33:35.966645718Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "51a9251fff6d" } ], "mcpTools": { "url": "https://api.read.ai/mcp", "checkedAt": "2026-11-07T01:47:10.755705667Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-08T21:34:01.397772588Z" }, "updatedAt": "2026-11-07T19:23:33.705097958Z" } }, "answer": "Zoom Realtime Media Streams (RTMS) scores 58.3 (C) on agent readiness against Read AI's 42.4 (E), and leads in 5 of 7 scored categories. Read AI leads on payments \u0026 pricing.", "b": { "slug": "zoom-rtms", "name": "Zoom Realtime Media Streams (RTMS)", "vendor": "Zoom Communications, Inc.", "vendorUrl": "https://www.zoom.com", "kind": "http-api", "category": "meeting-capture", "summary": "Zoom Realtime Media Streams (RTMS) gives a Zoom Marketplace app live audio, video, screen share, chat and diarised transcripts from Zoom Meetings, webinars, Contact Center and Video SDK sessions over WebSockets, without a bot in the meeting.", "url": "https://www.anchorterminal.com/tools/zoom-rtms", "markdownUrl": "https://www.anchorterminal.com/tools/zoom-rtms.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zoom-rtms.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zoom-rtms.json", "dns": "zoom-rtms.grade.anchorterminal.com", "repo": "https://github.com/zoom/rtms", "license": "Proprietary service under the Zoom API Licence and Terms of Use. The `@zoom/rtms` SDK is MIT on npm", "transports": [ "websocket", "http" ], "remoteUrl": "https://api.zoom.us/v2", "packages": [ { "registry": "npm", "name": "@zoom/rtms" } ], "auth": "oauth", "authNotes": "A user-managed General app on the Zoom App Marketplace with OAuth 2.0, granular RTMS scopes per media type (such as `meeting:read:meeting_audio` and `meeting:read:meeting_transcript`) and RTMS started and stopped event subscriptions. WebSocket handshakes are signed with HMAC SHA-256 from the app's client credentials.", "pricing": "paid", "pricingNotes": "Needs Zoom Developer Pack credits, sold on a usage basis. The developer pricing page shows no RTMS rates when read as text, volume above 500 credits goes through sales, and a free trial is requested through a sales form. Basic accounts can't start RTMS (checked 2026-11-06).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the RTMS docs, changelog or pricing pages (checked 2026-11-06).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://developers.zoom.us/docs/rtms/", "llmsTxt": "https://developers.zoom.us/llms.txt", "capabilities": [ "meetings.transcript", "meetings.recording", "voice.streaming", "speech.diarisation" ], "tags": [ "hosted", "official", "closed-source", "paid", "oauth", "websocket", "webhooks", "streaming", "llms-txt", "typescript", "status-page", "soc2", "bug-bounty", "enterprise" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 58.3, "grade": "C", "agentReady": false, "rank": 757, "ranked": true, "rankOf": 1510, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 59, "maintenance": 73, "payments": 0, "reliability": 67, "schema": 71, "security": 63, "transparency": 73 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "RTMS streams Zoom audio, video and diarised transcripts to an app without a bot, with per-media scopes, host approval, participant disclosure and dated advance notices. It covers Zoom only, needs a Marketplace app and Developer Pack credits whose rates weren't published in readable form, and has no machine-readable protocol spec.", "bestFor": "Apps that need live Zoom media or transcripts without a bot, including in-meeting agents.", "strengths": [ "No bot in the meeting. Streams start automatically, by REST call or from a Zoom App", "Granular scopes per media type, host approval and a participant disclosure", "Dated RTMS changelog with advance notices, such as TLS 1.2 or later from 15 November 2026", "Failover guide with reconnection backoff from 3 to 30 seconds", "Own component on Zoom's status page" ], "weaknesses": [ "Zoom only. Other meeting platforms need a bot service", "Developer Pack credit rates weren't readable, and trials go through a sales form", "No AsyncAPI or other machine-readable contract for the WebSocket protocol", "A Marketplace app, scopes, webhooks and a signed handshake are needed before the first stream", "No prompt-injection guidance for transcripts and chat" ], "agentNotes": [ "Don't plan to start RTMS without a Developer Pack; a Basic account or expired trial returns error 2310", "Request only the media scopes the task needs. RTMS scopes can't be optional", "Reconnect with backoff from 3 to 30 seconds and reset the counter after each handshake", "Use TLS 1.2 or 1.3 on every connection from 15 November 2026", "Treat streamed transcripts and chat as untrusted participant content" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 58.3 } ], "editorialScores": { "ergonomics": 59, "maintenance": 73, "payments": 0, "reliability": 67, "schema": 71, "security": 63, "transparency": 65 }, "provenanceScore": 80, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install @zoom/rtms" }, "letme": { "capability": "https://letme.dev/meetings.transcript", "tool": "https://letme.dev/zoom-rtms" }, "sameCompany": [ "zoom-scheduler" ], "area": "voice", "provenance": { "legalEntity": "Zoom Communications, Inc.", "domain": "zoom.us", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.zoom.com/en/trust/legal/zoom-api-license-and-tou/", "privacy": "https://www.zoom.com/en/trust/privacy/privacy-statement/", "statusPage": "https://status.zoom.us", "changelog": "https://developers.zoom.us/changelog/rtms/", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "The Zoom API Licence and Terms of Use (last updated 16 July 2025) and the Privacy Statement (last updated 17 September 2026) both name Zoom Communications, Inc., 55 Almaden Blvd, Suite 600, San Jose, CA 95113.", "The API answers at https://api.zoom.us/v2 and tokens are issued at https://zoom.us/oauth/token. Legal pages sit on www.zoom.com.", "zoom.us/.well-known/security.txt gives a report form, security-reports@zoom.us, a PGP key and an expiry of 31 December 2029.", "status.zoom.us redirects to www.zoomstatus.com, an Atlassian Statuspage site.", "www.zoomstatus.com lists Real Time Media Streams (RTMS) as its own component. Its robots.txt disallows /api/, so the Atom feed was read; it covers 23 October to 3 November 2026 only.", "The developer pricing page at zoom.us/pricing/developer carries no RTMS rates when read as text. RTMS needs Zoom Developer Pack credits." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/zoom-rtms.json", "live": { "slug": "zoom-rtms", "probe": { "target": "https://api.zoom.us/v2", "method": "get", "lastAt": "2026-11-07T19:22:47.068790558Z", "lastOk": true, "lastStatus": 404, "lastMs": 166, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 153, "p95ms24h": 274, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.zoom.us", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:24:02.789297877Z" }, "versions": [ { "registry": "github", "name": "zoom/rtms", "version": "py-v1.1.0", "released": "2026-04-16", "seenAt": "2026-11-07T00:19:31.992466375Z" }, { "registry": "npm", "name": "@zoom/rtms", "version": "1.1.0", "seenAt": "2026-11-07T00:19:31.178985248Z" } ], "githubStars": 40, "npmWeekly": 21643, "securityTxt": { "url": "https://zoom.us/.well-known/security.txt", "state": "valid", "expires": "2029-12-31T00:00:00.000Z", "checkedAt": "2026-11-07T16:00:10.393077783Z" }, "llmsTxt": { "url": "https://developers.zoom.us/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:31.269793617Z" }, "pages": [ { "url": "https://developers.zoom.us/changelog/rtms/", "kind": "changelog", "status": 404, "checkedAt": "2026-11-07T14:04:45.0125725Z", "changedAt": "0001-01-01T00:00:00Z" }, { "url": "https://www.zoom.com/en/trust/privacy/privacy-statement/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:37:55.98989692Z", "changedAt": "2026-10-22T01:39:12.393937492Z", "fingerprint": "c0d31e14e3ee" }, { "url": "https://www.zoom.com/en/trust/legal/zoom-api-license-and-tou/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:37:51.514566725Z", "changedAt": "2026-10-22T01:39:09.991974204Z", "fingerprint": "62f6354085e2" } ], "updatedAt": "2026-11-07T19:24:02.789297877Z" } }, "edges": [ { "by": 67, "category": "maintenance", "leads": "zoom-rtms", "name": "Maintenance \u0026 community", "reasons": { "a": "No changelog or release list was found on 8 October, and Read AI's hosts are paused today, so only recorded dates count. The MCP server article's edit date of 2 September 2026 records no stated change, and a page date without a recorded change doesn't set recency. The last dated API change on record is the MCP launch of 25 February 2026, over 180 days ago (0). Connection guides for Claude, ChatGPT and Microsoft Copilot Studio published between 25 and 27 August 2026 are documents, not dated releases, so fewer than three entries fall in the 90 days from 6 August (0). A support request form, no public changelog or developer forum found (6, a partial value kept). No readable MCP registry entry and no official SDK (0). No packages to assess (0). 0+0+6+0+0 = 6.", "b": "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." }, "scores": { "a": 6, "b": 73 } }, { "by": 40, "category": "reliability", "leads": "zoom-rtms", "name": "Reliability", "reasons": { "a": "Graded as a hosted service on the MCP server and REST API. Read AI's terms bar robots except to compile search results, so its hosts are paused and the 8 October readings stand where kept. The status page at readai.statuspage.io wasn't re-read on 4 November. Its components and incidents had been read only from the page's data path, which this run doesn't use, so the status-page line scores 0 and the window from 6 August is unread (5). 100 requests a minute per user, per the 8 October check (15). 429 is documented as retry later with no Retry-After or backoff guidance, while create meeting agent and share meeting report are documented as safe to repeat, per the 8 October check (7, a partial value kept). No SLA found (0). Both surfaces are open beta (0). 0+5+15+7+0+0 = 27.", "b": "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." }, "scores": { "a": 27, "b": 67 } }, { "by": 30, "category": "payments", "leads": "read-ai", "name": "Payments \u0026 pricing", "reasons": { "a": "Per the 8 October check, not re-read on 4 November (terms pause). No x402, MPP or L402 (0). Plan prices are public ($15, $22.50 and $29.75 a user a month billed annually) with nothing charged per call (10). The free plan needs no card and includes the API and MCP server (20). Client registration is programmatic, but a person has to sign in and consent in a browser (0). 0+10+20+0 = 30.", "b": "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." }, "scores": { "a": 30, "b": 0 } }, { "by": 25, "category": "schema", "leads": "zoom-rtms", "name": "Schema \u0026 documentation", "reasons": { "a": "Per the 8 October check, not re-read on 4 November (terms pause). No public OpenAPI file was found. The MCP tool schemas sit behind sign-in and were not read, and the help centre's parameter tables are prose documentation, not a machine-readable contract, so the contract line scores 0 (the tables count on typed inputs). www.read.ai/llms.txt points to the help centre's article index (10). The API reference says when to use the live endpoint over the standard one, and the MCP article lists inputs, defaults and limits for each of four tools (13). Parameters are typed in tables and access levels are enumerated, with no schema to confirm constraints (8). Each endpoint has a curl request and a sample response. Errors are a table of status codes with no body schema (10). A /v1 path prefix, no changelog (5). 0+10+13+8+10+5 = 46.", "b": "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." }, "scores": { "a": 46, "b": 71 } }, { "by": 9, "category": "security", "leads": "zoom-rtms", "name": "Security \u0026 auth", "reasons": { "a": "Per the 8 October check, not re-read on 4 November (terms pause). OAuth 2.1 with dynamic client registration, PKCE, 10-minute access tokens, rotating single-use refresh tokens and a revocation endpoint. Only two scopes, `meeting:read` and `mcp:execute`, so MCP access can't be narrowed to reading (24). A token reaches only reports its user can open, and a workspace admin can switch off access through the Downloads setting. No confirmation step is documented for sending a bot or sharing a report by email (9). Transcripts are untrusted speech and no injection guidance was found (0). Workspace audit logs in OCSF by webhook on Enterprise+ record sign-ins and integration connections, not individual calls (6). security.txt valid to 18 August 2027, SOC 2 Type 2 and a HIPAA option per the help centre, no bug bounty found (15). 24+9+0+6+15 = 54.", "b": "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." }, "scores": { "a": 54, "b": 63 } }, { "by": 9, "category": "transparency", "leads": "zoom-rtms", "name": "Transparency \u0026 trust", "reasons": { "a": "Per the 8 October check, not re-read on 4 November (terms pause). Closed service with published terms, last updated 26 February 2026, which still carry that date on 4 November (15). The privacy policy of 29 June 2026 keeps audio and video for no longer than two years and paid accounts' data until payment stops or deletion is requested. The help centre says model training is opt-in, while the terms grant a licence to train subject to opt-in or opt-out settings, and the DPA sits in a Trust Centre we couldn't read (20). No deprecation policy for the beta API (0). A sub-processor list is linked at trust.read.ai/subprocessors but didn't render for us, and EU and Canada data regions were announced on 2 February 2026 (10). 15+20+0+10 = 45.", "b": "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." }, "scores": { "a": 64, "b": 73 } } ], "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "Read AI, Inc.", "b": "Zoom Communications, Inc.", "name": "Vendor" }, { "a": "https://api.read.ai/mcp", "b": "https://api.zoom.us/v2", "name": "Hosted endpoint" }, { "a": "Streamable HTTP, HTTP", "b": "websocket, HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Read AI's terms of service", "b": "Proprietary service under the Zoom API Licence and Terms of Use. The `@zoom/rtms` SDK is MIT on npm", "name": "Licence" }, { "a": "4", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-02", "b": "2026-10-30", "name": "Last release" }, { "a": "2026-02-26", "b": "2025-07-16", "name": "Terms last updated" }, { "a": "2026-06-29", "b": "2026-09-17", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Zoom Realtime Media Streams (RTMS) scores 58.3 (C) on agent readiness against Read AI's 42.4 (E), and leads in 5 of 7 scored categories. Read AI leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Read AI or Zoom Realtime Media Streams (RTMS)?" }, { "answer": "Both use an OAuth sign-in.", "question": "Do Read AI and Zoom Realtime Media Streams (RTMS) need an API key?" }, { "answer": "Yes. Read AI has a hosted endpoint at https://api.read.ai/mcp and Zoom Realtime Media Streams (RTMS) at https://api.zoom.us/v2.", "question": "Can an agent call Read AI and Zoom Realtime Media Streams (RTMS) without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 30 against 0" ], "also": [ "Free to start without a card" ], "goodFor": "An agent working for a person or team that already records meetings with Read AI and wants transcripts, summaries and action items in context.", "slug": "read-ai", "watchFor": "Both the REST API and the MCP server are labelled open beta, with no SLA, no deprecation policy and no dated API change on record since the February 2026 launch" }, { "aheadOn": [ "Reliability, 67 against 27", "Schema \u0026 documentation, 71 against 46", "Security \u0026 auth, 63 against 54", "Maintenance \u0026 community, 73 against 6", "Transparency \u0026 trust, 73 against 64" ], "also": null, "goodFor": "Apps that need live Zoom media or transcripts without a bot, including in-meeting agents.", "slug": "zoom-rtms", "watchFor": "Zoom only. Other meeting platforms need a bot service" } ], "history": { "read-ai": [ { "causes": [ "correction" ], "date": "2026-11-04", "delta": -8, "from": 50.4, "fromGrade": "D", "to": 42.4, "toGrade": "E" }, { "causes": [ "correction" ], "date": "2026-10-28", "delta": -0.1, "from": 50.5, "fromGrade": "D", "to": 50.4, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 50.4, "fromGrade": "D", "to": 50.5, "toGrade": "D" } ], "zoom-rtms": null }, "job": { "capability": "meetings.transcript", "name": "Meeting transcripts" }, "others": [ { "json": "https://www.anchorterminal.com/compare/attendee-vs-zoom-rtms.json", "title": "Attendee vs Zoom Realtime Media Streams (RTMS)", "url": "https://www.anchorterminal.com/compare/attendee-vs-zoom-rtms" }, { "json": "https://www.anchorterminal.com/compare/circleback-vs-read-ai.json", "title": "Circleback vs Read AI", "url": "https://www.anchorterminal.com/compare/circleback-vs-read-ai" }, { "json": "https://www.anchorterminal.com/compare/circleback-vs-zoom-rtms.json", "title": "Circleback vs Zoom Realtime Media Streams (RTMS)", "url": "https://www.anchorterminal.com/compare/circleback-vs-zoom-rtms" }, { "json": "https://www.anchorterminal.com/compare/fathom-vs-read-ai.json", "title": "Fathom vs Read AI", "url": "https://www.anchorterminal.com/compare/fathom-vs-read-ai" }, { "json": "https://www.anchorterminal.com/compare/fathom-vs-zoom-rtms.json", "title": "Fathom vs Zoom Realtime Media Streams (RTMS)", "url": "https://www.anchorterminal.com/compare/fathom-vs-zoom-rtms" }, { "json": "https://www.anchorterminal.com/compare/fireflies-vs-read-ai.json", "title": "Fireflies.ai vs Read AI", "url": "https://www.anchorterminal.com/compare/fireflies-vs-read-ai" }, { "json": "https://www.anchorterminal.com/compare/fireflies-vs-zoom-rtms.json", "title": "Fireflies.ai vs Zoom Realtime Media Streams (RTMS)", "url": "https://www.anchorterminal.com/compare/fireflies-vs-zoom-rtms" }, { "json": "https://www.anchorterminal.com/compare/granola-vs-read-ai.json", "title": "Granola vs Read AI", "url": "https://www.anchorterminal.com/compare/granola-vs-read-ai" }, { "json": "https://www.anchorterminal.com/compare/granola-vs-zoom-rtms.json", "title": "Granola vs Zoom Realtime Media Streams (RTMS)", "url": "https://www.anchorterminal.com/compare/granola-vs-zoom-rtms" }, { "json": "https://www.anchorterminal.com/compare/meetgeek-vs-read-ai.json", "title": "MeetGeek vs Read AI", "url": "https://www.anchorterminal.com/compare/meetgeek-vs-read-ai" }, { "json": "https://www.anchorterminal.com/compare/meetgeek-vs-zoom-rtms.json", "title": "MeetGeek vs Zoom Realtime Media Streams (RTMS)", "url": "https://www.anchorterminal.com/compare/meetgeek-vs-zoom-rtms" }, { "json": "https://www.anchorterminal.com/compare/meeting-baas-vs-zoom-rtms.json", "title": "Meeting BaaS vs Zoom Realtime Media Streams (RTMS)", "url": "https://www.anchorterminal.com/compare/meeting-baas-vs-zoom-rtms" }, { "json": "https://www.anchorterminal.com/compare/meetstream-vs-zoom-rtms.json", "title": "MeetStream vs Zoom Realtime Media Streams (RTMS)", "url": "https://www.anchorterminal.com/compare/meetstream-vs-zoom-rtms" }, { "json": "https://www.anchorterminal.com/compare/nylas-notetaker-vs-zoom-rtms.json", "title": "Nylas Notetaker API vs Zoom Realtime Media Streams (RTMS)", "url": "https://www.anchorterminal.com/compare/nylas-notetaker-vs-zoom-rtms" }, { "json": "https://www.anchorterminal.com/compare/read-ai-vs-tldv.json", "title": "Read AI vs tl;dv", "url": "https://www.anchorterminal.com/compare/read-ai-vs-tldv" }, { "json": "https://www.anchorterminal.com/compare/recall-ai-vs-zoom-rtms.json", "title": "Recall.ai vs Zoom Realtime Media Streams (RTMS)", "url": "https://www.anchorterminal.com/compare/recall-ai-vs-zoom-rtms" }, { "json": "https://www.anchorterminal.com/compare/tldv-vs-zoom-rtms.json", "title": "tl;dv vs Zoom Realtime Media Streams (RTMS)", "url": "https://www.anchorterminal.com/compare/tldv-vs-zoom-rtms" }, { "json": "https://www.anchorterminal.com/compare/attendee-vs-read-ai.json", "title": "Attendee vs Read AI", "url": "https://www.anchorterminal.com/compare/attendee-vs-read-ai" }, { "json": "https://www.anchorterminal.com/compare/meeting-baas-vs-read-ai.json", "title": "Meeting BaaS vs Read AI", "url": "https://www.anchorterminal.com/compare/meeting-baas-vs-read-ai" }, { "json": "https://www.anchorterminal.com/compare/meetstream-vs-read-ai.json", "title": "MeetStream vs Read AI", "url": "https://www.anchorterminal.com/compare/meetstream-vs-read-ai" }, { "json": "https://www.anchorterminal.com/compare/nylas-notetaker-vs-read-ai.json", "title": "Nylas Notetaker API vs Read AI", "url": "https://www.anchorterminal.com/compare/nylas-notetaker-vs-read-ai" }, { "json": "https://www.anchorterminal.com/compare/read-ai-vs-recall-ai.json", "title": "Read AI vs Recall.ai", "url": "https://www.anchorterminal.com/compare/read-ai-vs-recall-ai" } ], "panel": null, "scores": [ { "by": 40, "edge": "zoom-rtms", "key": "reliability", "name": "Reliability", "read-ai": 27, "weight": 16, "zoom-rtms": 67 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 25, "edge": "zoom-rtms", "key": "schema", "name": "Schema \u0026 documentation", "read-ai": 46, "weight": 13, "zoom-rtms": 71 }, { "by": 4, "edge": "read-ai", "key": "ergonomics", "name": "Agent ergonomics", "read-ai": 63, "weight": 13, "zoom-rtms": 59 }, { "by": 9, "edge": "zoom-rtms", "key": "security", "name": "Security \u0026 auth", "read-ai": 54, "weight": 14, "zoom-rtms": 63 }, { "by": 30, "edge": "read-ai", "key": "payments", "name": "Payments \u0026 pricing", "read-ai": 30, "weight": 10, "zoom-rtms": 0 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 67, "edge": "zoom-rtms", "key": "maintenance", "name": "Maintenance \u0026 community", "read-ai": 6, "weight": 7, "zoom-rtms": 73 }, { "by": 9, "edge": "zoom-rtms", "key": "transparency", "name": "Transparency \u0026 trust", "read-ai": 64, "weight": 7, "zoom-rtms": 73 } ], "summary": "Zoom Realtime Media Streams (RTMS) scores 58.3 (C) on agent readiness against Read AI's 42.4 (E), and leads in 5 of 7 scored categories. Read AI leads on payments \u0026 pricing. Both do meeting transcripts.", "tasks": null, "tutorials": [], "verdicts": { "read-ai": "Four MCP tools and three REST endpoints return transcripts, summaries, action items and recording links, and the MCP server can send a bot to a named meeting. Both surfaces are in open beta. Access needs a browser sign-in, access tokens last 10 minutes, and no OpenAPI file, changelog or readable incident history was found.", "zoom-rtms": "RTMS streams Zoom audio, video and diarised transcripts to an app without a bot, with per-media scopes, host approval, participant disclosure and dated advance notices. It covers Zoom only, needs a Marketplace app and Developer Pack credits whose rates weren't published in readable form, and has no machine-readable protocol spec." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/read-ai-vs-zoom-rtms", "json": "https://www.anchorterminal.com/compare/read-ai-vs-zoom-rtms.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/read-ai-vs-zoom-rtms.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/read-ai-vs-zoom-rtms.min.md" }, "markdown": "Zoom Realtime Media Streams (RTMS) scores 58.3 (C) on agent readiness against Read AI's 42.4 (E), and leads in 5 of 7 scored categories. Read AI leads on payments \u0026 pricing. Both do meeting transcripts.\n\n- Read AI: grade E, 42.4/100, rank #1282 of 1510. Markdown https://www.anchorterminal.com/tools/read-ai.md · JSON https://www.anchorterminal.com/api/v1/tools/read-ai.json\n- Zoom Realtime Media Streams (RTMS): grade C, 58.3/100, rank #757 of 1510. Markdown https://www.anchorterminal.com/tools/zoom-rtms.md · JSON https://www.anchorterminal.com/api/v1/tools/zoom-rtms.json\n- Best meeting bots, recording and transcript APIs for AI agents: https://www.anchorterminal.com/best/meeting-capture/index.md\n- All 78 meetings comparisons: https://www.anchorterminal.com/compare/meeting-capture/index.md\n\n## Which one, for what\n\n### Read AI (E)\n\nGood for: An agent working for a person or team that already records meetings with Read AI and wants transcripts, summaries and action items in context.\n\nAhead on:\n- Payments \u0026 pricing, 30 against 0\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: Both the REST API and the MCP server are labelled open beta, with no SLA, no deprecation policy and no dated API change on record since the February 2026 launch\n\n### Zoom Realtime Media Streams (RTMS) (C)\n\nGood for: Apps that need live Zoom media or transcripts without a bot, including in-meeting agents.\n\nAhead on:\n- Reliability, 67 against 27\n- Schema \u0026 documentation, 71 against 46\n- Security \u0026 auth, 63 against 54\n- Maintenance \u0026 community, 73 against 6\n- Transparency \u0026 trust, 73 against 64\n\nWatch for: Zoom only. Other meeting platforms need a bot service\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Zoom Realtime Media Streams (RTMS) +67\n\n- Read AI (6): No changelog or release list was found on 8 October, and Read AI's hosts are paused today, so only recorded dates count. The MCP server article's edit date of 2 September 2026 records no stated change, and a page date without a recorded change doesn't set recency. The last dated API change on record is the MCP launch of 25 February 2026, over 180 days ago (0). Connection guides for Claude, ChatGPT and Microsoft Copilot Studio published between 25 and 27 August 2026 are documents, not dated releases, so fewer than three entries fall in the 90 days from 6 August (0). A support request form, no public changelog or developer forum found (6, a partial value kept). No readable MCP registry entry and no official SDK (0). No packages to assess (0). 0+0+6+0+0 = 6.\n- 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.\n\n### Reliability: Zoom Realtime Media Streams (RTMS) +40\n\n- Read AI (27): Graded as a hosted service on the MCP server and REST API. Read AI's terms bar robots except to compile search results, so its hosts are paused and the 8 October readings stand where kept. The status page at readai.statuspage.io wasn't re-read on 4 November. Its components and incidents had been read only from the page's data path, which this run doesn't use, so the status-page line scores 0 and the window from 6 August is unread (5). 100 requests a minute per user, per the 8 October check (15). 429 is documented as retry later with no Retry-After or backoff guidance, while create meeting agent and share meeting report are documented as safe to repeat, per the 8 October check (7, a partial value kept). No SLA found (0). Both surfaces are open beta (0). 0+5+15+7+0+0 = 27.\n- 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.\n\n### Payments \u0026 pricing: Read AI +30\n\n- Read AI (30): Per the 8 October check, not re-read on 4 November (terms pause). No x402, MPP or L402 (0). Plan prices are public ($15, $22.50 and $29.75 a user a month billed annually) with nothing charged per call (10). The free plan needs no card and includes the API and MCP server (20). Client registration is programmatic, but a person has to sign in and consent in a browser (0). 0+10+20+0 = 30.\n- 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.\n\n### Schema \u0026 documentation: Zoom Realtime Media Streams (RTMS) +25\n\n- Read AI (46): Per the 8 October check, not re-read on 4 November (terms pause). No public OpenAPI file was found. The MCP tool schemas sit behind sign-in and were not read, and the help centre's parameter tables are prose documentation, not a machine-readable contract, so the contract line scores 0 (the tables count on typed inputs). www.read.ai/llms.txt points to the help centre's article index (10). The API reference says when to use the live endpoint over the standard one, and the MCP article lists inputs, defaults and limits for each of four tools (13). Parameters are typed in tables and access levels are enumerated, with no schema to confirm constraints (8). Each endpoint has a curl request and a sample response. Errors are a table of status codes with no body schema (10). A /v1 path prefix, no changelog (5). 0+10+13+8+10+5 = 46.\n- 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.\n\n### Security \u0026 auth: Zoom Realtime Media Streams (RTMS) +9\n\n- Read AI (54): Per the 8 October check, not re-read on 4 November (terms pause). OAuth 2.1 with dynamic client registration, PKCE, 10-minute access tokens, rotating single-use refresh tokens and a revocation endpoint. Only two scopes, `meeting:read` and `mcp:execute`, so MCP access can't be narrowed to reading (24). A token reaches only reports its user can open, and a workspace admin can switch off access through the Downloads setting. No confirmation step is documented for sending a bot or sharing a report by email (9). Transcripts are untrusted speech and no injection guidance was found (0). Workspace audit logs in OCSF by webhook on Enterprise+ record sign-ins and integration connections, not individual calls (6). security.txt valid to 18 August 2027, SOC 2 Type 2 and a HIPAA option per the help centre, no bug bounty found (15). 24+9+0+6+15 = 54.\n- 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.\n\n### Transparency \u0026 trust: Zoom Realtime Media Streams (RTMS) +9\n\n- Read AI (64): Per the 8 October check, not re-read on 4 November (terms pause). Closed service with published terms, last updated 26 February 2026, which still carry that date on 4 November (15). The privacy policy of 29 June 2026 keeps audio and video for no longer than two years and paid accounts' data until payment stops or deletion is requested. The help centre says model training is opt-in, while the terms grant a licence to train subject to opt-in or opt-out settings, and the DPA sits in a Trust Centre we couldn't read (20). No deprecation policy for the beta API (0). A sub-processor list is linked at trust.read.ai/subprocessors but didn't render for us, and EU and Canada data regions were announced on 2 February 2026 (10). 15+20+0+10 = 45.\n- 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.\n\n## Score by category\n\n| Category | Weight | Read AI | Zoom Realtime Media Streams (RTMS) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 27 | 67 | Zoom Realtime Media Streams (RTMS) +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 46 | 71 | Zoom Realtime Media Streams (RTMS) +25 |\n| Agent ergonomics | 13% (16.2 this run) | 63 | 59 | Read AI +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 54 | 63 | Zoom Realtime Media Streams (RTMS) +9 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 0 | Read AI +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 6 | 73 | Zoom Realtime Media Streams (RTMS) +67 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 64 | 73 | Zoom Realtime Media Streams (RTMS) +9 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **42.4 · E** | **58.3 · C** | |\n\n## Facts side by side\n\n| Fact | Read AI | Zoom Realtime Media Streams (RTMS) |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Read AI, Inc. | Zoom Communications, Inc. |\n| Hosted endpoint | `https://api.read.ai/mcp` | `https://api.zoom.us/v2` |\n| Transports | Streamable HTTP, HTTP | websocket, HTTP |\n| Auth | OAuth | OAuth |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Read AI's terms of service | Proprietary service under the Zoom API Licence and Terms of Use. The `@zoom/rtms` SDK is MIT on npm |\n| Tools exposed | 4 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-02 | 2026-10-30 |\n| Terms last updated | 2026-02-26 | 2025-07-16 |\n| Privacy policy last updated | 2026-06-29 | 2026-09-17 |\n| Customer content may train models | yes, with an opt-out | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | yes | yes |\n\n## How the scores have moved\n\n### Read AI\n\n- -8.0 on 4 November 2026 (D to E): correction\n- -0.1 on 28 October 2026: correction\n- +0.1 on 27 October 2026: checklist\n\n### Zoom Realtime Media Streams (RTMS)\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Read AI.** Four MCP tools and three REST endpoints return transcripts, summaries, action items and recording links, and the MCP server can send a bot to a named meeting. Both surfaces are in open beta. Access needs a browser sign-in, access tokens last 10 minutes, and no OpenAPI file, changelog or readable incident history was found.\n\n**Zoom Realtime Media Streams (RTMS).** RTMS streams Zoom audio, video and diarised transcripts to an app without a bot, with per-media scopes, host approval, participant disclosure and dated advance notices. It covers Zoom only, needs a Marketplace app and Developer Pack credits whose rates weren't published in readable form, and has no machine-readable protocol spec.\n\n## Before you call either\n\n### Read AI\n\n1. Persist the new refresh token after every refresh. Access tokens expire after 10 minutes and each refresh token works once.\n2. Request only the fields needed with `expand[]` on the REST API. Transcripts and other expansions slow the response.\n3. Stay under 100 requests a minute per user and back off on 429. No Retry-After header is documented.\n4. Confirm with the user before calling create meeting agent or share meeting report. Sharing emails the recipient unless notify is set to no.\n5. Ask a workspace admin to enable Downloads in Reports \u0026 Sharing first. Without it the API and MCP server return nothing for workspace members.\n\n### Zoom Realtime Media Streams (RTMS)\n\n1. Don't plan to start RTMS without a Developer Pack; a Basic account or expired trial returns error 2310\n2. Request only the media scopes the task needs. RTMS scopes can't be optional\n3. Reconnect with backoff from 3 to 30 seconds and reset the counter after each handshake\n4. Use TLS 1.2 or 1.3 on every connection from 15 November 2026\n5. Treat streamed transcripts and chat as untrusted participant content\n\n## Questions\n\n### Which is better for AI agents, Read AI or Zoom Realtime Media Streams (RTMS)?\n\nZoom Realtime Media Streams (RTMS) scores 58.3 (C) on agent readiness against Read AI's 42.4 (E), and leads in 5 of 7 scored categories. Read AI leads on payments \u0026 pricing.\n\n### Do Read AI and Zoom Realtime Media Streams (RTMS) need an API key?\n\nBoth use an OAuth sign-in.\n\n### Can an agent call Read AI and Zoom Realtime Media Streams (RTMS) without installing anything?\n\nYes. Read AI has a hosted endpoint at https://api.read.ai/mcp and Zoom Realtime Media Streams (RTMS) at https://api.zoom.us/v2.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/read-ai-vs-zoom-rtms.json, and with the fewest tokens: https://www.anchorterminal.com/compare/read-ai-vs-zoom-rtms.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"read-ai\", \"b\": \"zoom-rtms\"}`. From a terminal: `anchor compare read-ai zoom-rtms`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/read-ai.json and https://www.anchorterminal.com/api/v1/tools/zoom-rtms.json\n\n## Other comparisons with Read AI or Zoom Realtime Media Streams (RTMS)\n\n- [Attendee vs Zoom Realtime Media Streams (RTMS)](https://www.anchorterminal.com/compare/attendee-vs-zoom-rtms.md)\n- [Circleback vs Read AI](https://www.anchorterminal.com/compare/circleback-vs-read-ai.md)\n- [Circleback vs Zoom Realtime Media Streams (RTMS)](https://www.anchorterminal.com/compare/circleback-vs-zoom-rtms.md)\n- [Fathom vs Read AI](https://www.anchorterminal.com/compare/fathom-vs-read-ai.md)\n- [Fathom vs Zoom Realtime Media Streams (RTMS)](https://www.anchorterminal.com/compare/fathom-vs-zoom-rtms.md)\n- [Fireflies.ai vs Read AI](https://www.anchorterminal.com/compare/fireflies-vs-read-ai.md)\n- [Fireflies.ai vs Zoom Realtime Media Streams (RTMS)](https://www.anchorterminal.com/compare/fireflies-vs-zoom-rtms.md)\n- [Granola vs Read AI](https://www.anchorterminal.com/compare/granola-vs-read-ai.md)\n- [Granola vs Zoom Realtime Media Streams (RTMS)](https://www.anchorterminal.com/compare/granola-vs-zoom-rtms.md)\n- [MeetGeek vs Read AI](https://www.anchorterminal.com/compare/meetgeek-vs-read-ai.md)\n- [MeetGeek vs Zoom Realtime Media Streams (RTMS)](https://www.anchorterminal.com/compare/meetgeek-vs-zoom-rtms.md)\n- [Meeting BaaS vs Zoom Realtime Media Streams (RTMS)](https://www.anchorterminal.com/compare/meeting-baas-vs-zoom-rtms.md)\n- [MeetStream vs Zoom Realtime Media Streams (RTMS)](https://www.anchorterminal.com/compare/meetstream-vs-zoom-rtms.md)\n- [Nylas Notetaker API vs Zoom Realtime Media Streams (RTMS)](https://www.anchorterminal.com/compare/nylas-notetaker-vs-zoom-rtms.md)\n- [Read AI vs tl;dv](https://www.anchorterminal.com/compare/read-ai-vs-tldv.md)\n- [Recall.ai vs Zoom Realtime Media Streams (RTMS)](https://www.anchorterminal.com/compare/recall-ai-vs-zoom-rtms.md)\n- [tl;dv vs Zoom Realtime Media Streams (RTMS)](https://www.anchorterminal.com/compare/tldv-vs-zoom-rtms.md)\n- [Attendee vs Read AI](https://www.anchorterminal.com/compare/attendee-vs-read-ai.md)\n- [Meeting BaaS vs Read AI](https://www.anchorterminal.com/compare/meeting-baas-vs-read-ai.md)\n- [MeetStream vs Read AI](https://www.anchorterminal.com/compare/meetstream-vs-read-ai.md)\n- [Nylas Notetaker API vs Read AI](https://www.anchorterminal.com/compare/nylas-notetaker-vs-read-ai.md)\n- [Read AI vs Recall.ai](https://www.anchorterminal.com/compare/read-ai-vs-recall-ai.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Read AI vs Zoom Realtime Media Streams (RTMS)", "url": "" } ], "description": "Zoom Realtime Media Streams scores 58.3 (C) to Read AI's 42.4 (E) for meeting transcripts. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Read AI E 42.4", "Zoom Realtime Media Streams (RTMS) C 58.3", "scores" ], "h1": "Read AI vs Zoom Realtime Media Streams (RTMS)", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/read-ai-vs-zoom-rtms", "published": "2026-10-01", "section": "tools", "title": "Read AI vs Zoom Realtime Media Streams for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/read-ai-vs-zoom-rtms" }, "tokens": { "markdown": 4750, "slim": 2930 }, "version": 1 }