Nylas Notetaker API vs Zoom Realtime Media Streams (RTMS)

Nylas Notetaker API 40

No x402, MPP or L402 was found in llms.txt, the OpenAPI file or the pricing page (0). Prices per additional bot hour are public, at $0.80 on Essentials, $0.70 on Pro monthly and $0.65 on Pro annual (20). The Free plan includes 5 bot hours a month and the pricing page says no credit card is required (20). A person creates the account in the Dashboard or through the CLI wizard, which signs in with Google, Microsoft or GitHub (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.

Nylas Notetaker API 89

A public OpenAPI 3.1 file covers 244 operations on 140 paths, 23 of them for Notetaker (25). llms.txt, llms-full.txt and a Markdown twin of every page are served (10). Operation descriptions say what each call does and when it applies, such as cancel before joining, leave while attending and delete in any state (16). Notetaker schemas use enums for state, recording type and ordering, ranges for retention and silence timeout, and one required field, with no untyped objects found (13). Each operation documents its 400, 401, 404, 409, 410 and 429 responses, and the media endpoints now a 207 for partial results, with examples and code samples in five languages. The error type is a plain string and the error table lists no Notetaker-specific types (12). The path is versioned as v3 and a dated changelog with an Atom feed tags Notetaker entries. No dated versions within v3 were found (13).

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.

Nylas Notetaker API 77

Media comes back as download links, select trims responses to named top-level fields, and limit caps list size (20). List calls page by cursor with next_cursor and page_token, 50 by default and 200 at most, with filters by state and join time and three sort fields (20). Errors carry type, message and request_id, join failures name a reason such as bad_meeting_link or entry_denied, and the media endpoint separates 404 for processing from 410 for deleted (17). Invites accept no idempotency key and every request schedules a new bot. Deduplication covers only Notetakers with a future join_time, and the media endpoint is documented as idempotent (6). An invite needs only meeting_link, and SDKs exist for Node.js, Python, Ruby and Kotlin/Java. The quickstart's SDK samples still use the deprecated name and meeting_settings fields (14).

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.

Nylas Notetaker API 78

Nylas IAM keys, launched 6 October 2026, bind a caller to one grant, workspace, application or organisation with roles and permissions, and can expire. The IAM guide (last updated 9 October) shows principals and credentials can also be created, rotated and revoked through a public /v3/iam API once a first management key is made in the Dashboard, as read for nylas-email. Application keys still reach every grant, and the IAM pages we read don't list Notetaker permissions by name. Keys travel in the Authorization header only. 1 is held back for the application key, as for nylas-email, and 1 because no Notetaker permission is named (28). IAM allows least-privilege callers, but delete is a hard delete with no confirmation step, and the MCP server's confirmation covers email sends only (12). The docs tell developers to treat email and calendar content as untrusted. No guidance names transcripts or meeting chat (8). IAM Access Activity records allowed and denied requests for 400 days, Config Changes records IAM edits, and each Notetaker has a history endpoint (13). The security page lists SOC 2 Type II, ISO 27001, ISO 27701, HIPAA and CSA STAR, a vulnerability disclosure programme, a private bug bounty and annual penetration tests. developer.nylas.com serves an RFC 9116 security.txt with security@nylas.com, valid to 1 August 2027, while www.nylas.com returns 404. That is the evidence nylas-email's 17 rests on, so the line matches it (17). 28+12+8+13+17 = 78.

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.

Nylas Notetaker API 78

Graded on the hosted lines for the REST API. status-v3.nylas.com is a public status page with Notetaker as its own component and a dated history feed (20). The degraded Zoom joins of 17 to 23 July (resolved 23 July 13:54 PDT) left the 90-day window. From 3 August to 1 November the one Notetaker incident is degraded Teams joins for a very limited subset of US meetings on 4 September (11:34 to 14:47 PDT, marked minor), so minor incidents only (20). The 19 August incident, delayed or missing webhooks for every email and calendar provider in the US and EU (09:11 to 14:34 PDT), holds nylas-email's line at 10. Its page lists only the Webhooks v3 component, not Notetaker, and its updates speak of affected Microsoft, Google and then all provider grants, mitigated by recovering their sync state. Notetaker events don't pass through provider grant sync and no update names Notetaker, so it isn't counted here. Limits are published as 200 requests a second per grant and 50 a second per application, but the table names no Notetaker row (12). 429 handling is documented with backoff guidance, Retry-After arrives only when a provider supplies it, and invites accept no idempotency key, so a retry can send a second bot (9). The pricing page lists a 99.99 per cent availability SLA for annual Enterprise contracts, with full terms in the customer agreement, as read for nylas-email (7). No beta or preview label was found on the Notetaker docs (10). 20+20+12+9+7+10 = 78.

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.

Nylas Notetaker API 81

The last Notetaker changelog entries are dated 26 and 29 October 2026, a 207 status for partial media and a change to the webhook time field (30). The changelog has Notetaker entries on 15, 18 and 21 September and 26 and 29 October, and platform entries through 30 October (20). Support is a public forum on every plan and email support from Pro Annual upward. We did not read the forum, so reply times are unchecked (10). Official SDKs are current, with Ruby 6.9.0 tagged on 26 October 2026 to accept the 207, Python 6.18.0 (1 October) and Node.js 8.4.0 (15). The SDK and CLI repositories are MIT and the Ruby SDK runs a test matrix in CI. The others' CI was not inspected (6). 30+20+10+15+6 = 81.

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.