# Fathom vs MeetStream (slim)

> MeetStream scores 57.3 (C) to Fathom's 55.3 (C) for meeting transcripts. Prices, MCP, x402, uptime and agent notes side by side.

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

MeetStream scores 57.3 (C) on agent readiness against Fathom's 55.3 (C), and leads in 4 of 7 scored categories. Fathom leads on reliability and transparency & trust. Both do meeting transcripts.

- Fathom: C 55.3, rank #871 of 1486 · https://www.anchorterminal.com/tools/fathom.min.md
- MeetStream: C 57.3, rank #799 of 1486 · https://www.anchorterminal.com/tools/meetstream.min.md
- Fathom, good for Teams already recording meetings in Fathom who want an agent to read transcripts, summaries, action items and recordings. Ahead on Reliability, 58 against 45; Transparency & trust, 68 against 57. Also No incidents deducted, where MeetStream loses 4 points for them.
- MeetStream, good for Developers building their own notetaker or in-meeting voice agent on Zoom, Meet and Teams at per-hour pricing. Ahead on Agent ergonomics, 88 against 64; Payments & pricing, 40 against 30; Maintenance & community, 82 against 37. Also Free to start without a card.

| Category | Fathom | MeetStream |
| --- | --- | --- |
| Reliability (16%) | 58 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 80 | 83 |
| Agent ergonomics (13%) | 64 | 88 |
| Security & auth (14%) | 42 | 42 |
| Payments & pricing (10%) | 30 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 37 | 82 |
| Transparency & trust (7%) | 68 | 57 |

| Fact (where they differ) | Fathom | MeetStream |
| --- | --- | --- |
| Vendor | Fathom Video Inc. | MeetStream Corp. |
| Hosted endpoint | `https://api.fathom.ai/external/v1` | `https://mcp.meetstream.ai/mcp` |
| Transports | HTTP, Streamable HTTP | HTTP, websocket, Streamable HTTP |
| Pricing | Freemium | Pay per use |
| Licence | Proprietary service under Fathom's terms of service. The TypeScript and Python SDKs are published on npm and PyPI with no licence in the package metadata | Proprietary service under MeetStream's Terms of Use. The SDKs `@meetstream/sdk` and `meetstream-sdk` and the Go MCP server are published separately |
| Tools exposed | none | 19 |
| MCP registry | `ai.fathom.api/mcp` | `io.github.meetstream-ai/meetstream-mcp` |
| Last release | 2026-07-29 | 2026-10-27 |
| Terms last updated | 2026-03-04 | 2026-08-07 |
| Privacy policy last updated | 2026-08-16 | 2026-08-07 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 83k npm/wk, 58k PyPI/wk | none |
| Agent reviews | 4/5 (4) | none |

Why the edge:
- Maintenance & community, MeetStream +45: Fathom 37 (The newest dated release on record is SDK version 0.0.43 on 29 July 2026, per the 8 October check, 98 days before this check. The docs changelog's newest entry is labelled July 2026 by month only, which doesn't set recency (10 of 30). SDK 0.0.42 (23 July) and 0.0.43 (29 July) fall before 6 August, and no release or dated entry inside the 90 days is on record (0 of 20). A public changelog, weekly product release notes, a support address and a handled API incident on the status page, with no public issue tracker (8 of 25). Listed in the official MCP registry as ai.fathom.api/mcp, with current TypeScript and Python SDKs (15). The SDKs are generated with Speakeasy, at 0.0.x, with no public repository or licence in the package metadata (4 of 10).); MeetStream 82 (Changelog entries on 27 October 2026 (camera streaming and prepaid creation limits) (30). Dated entries throughout the 90 days, among them 11, 10, 9, 7, 4, 3, 2 and 1 September and 31, 30, 29, 26 and 24 August (20). A public changelog, support@meetstream.ai and Slack support, with no evidence read of reply times (10 of 15). In the official MCP registry as io.github.meetstream-ai/meetstream-mcp 0.3.0, and official SDKs 1.0.0 since 26 August 2026 (15). The SDKs list zero runtime dependencies for TypeScript, and the CLI and MCP server send telemetry with an opt-out. The repositories weren't cloned (7 of 10). 30+20+10+15+7 = 82.)
- Agent ergonomics, MeetStream +24: Fathom 64 (Responses are sized with `include_transcript`, `include_summary`, `include_action_items`, `include_highlights` and `include_crm_matches`, all off by default, and separate summary and transcript endpoints. The page size is fixed at 10 and the MCP tool count could not be read (17 of 25). Cursor pagination with filters for date range, recorder, team, invitee domain and meeting type. No page-size parameter, attendee filter or text search (15 of 20). Errors are documented as status codes without codes or a body schema (8 of 20). Nine of 11 operations are GET and webhook deliveries can be deduplicated by `webhook-id`. No idempotency keys, and MCP annotations could not be read (10 of 20). Few required parameters and official TypeScript and Python SDKs, both beta at 0.0.43 (14 of 15). Per the 8 October check, not re-read on 4 November.); 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.)
- Reliability, Fathom +13: Fathom 58 (Graded on the hosted REST API and MCP server, per the 8 October check, not re-read on 4 November. Fathom's terms bar any automated tool from accessing the Service, and this run pauses such hosts pending a ruling. status.fathom.video is a Statuspage site, per the 8 October check (20). The 8 October component and incident counts came from the page's /api/ path, which its robots.txt disallows, so both are struck, and with nothing readable today the window from 6 August is unread (5). Limits are published with numbers, 60 calls a minute and 30 for heavy requests (15). 429 carries `Retry-After` and `RateLimit-*` headers and the SDKs retry. No idempotency key or safe-retry guidance covers the two POST calls, so this is Retry-After guidance alone (10). No uptime SLA was found. Enterprise lists priority support SLAs only (0). The API and MCP server carry no beta label, while both SDKs are declared beta (8).); 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.)
- Transparency & trust, Fathom +11: Fathom 68 (Closed service with published terms, last updated 4 March 2026. They have no clause on API use and bar any automated tool from accessing the Service (12 of 30). The privacy policy, the DPA and the help centre agree that data is stored in the United States, third parties may not train on it and Fathom trains in-house models on de-identified content unless the user opts out. The privacy policy says deletion within 30 days, the help centre says backups clear after a further 7 days, and no general retention period is given (22 of 30). No deprecation policy was found. SDK breaking changes at 0.0.30 are documented and the terms allow parts of the Service to be discontinued at any time (5 of 20). The DPA points to a sub-processor list at trust.fathom.video, which we could not read. The help centre names Anthropic, OpenAI and Google as AI sub-processors (12 of 20). Per the 8 October check, not re-read on 4 November.); 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.)
- Payments & pricing, MeetStream +10: Fathom 30 (No x402, MPP or L402 (0). Plan prices are public ($20, $19 and $34 a user a month, less when billed annually), with nothing priced per call (10). The Free plan includes API keys and webhooks (20). A person signs up in a browser and generates a key or approves OAuth (0). Per the 8 October check, not re-read on 4 November.); 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.)