# MeetGeek vs Read AI

> MeetGeek scores 52.1 (D) to Read AI's 42.4 (E) for meeting transcripts. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/meetgeek-vs-read-ai
- Markdown: https://www.anchorterminal.com/compare/meetgeek-vs-read-ai.md (~3,550 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

MeetGeek scores 52.1 (D) on agent readiness against Read AI's 42.4 (E), and leads in 4 of 7 scored categories. Read AI leads on security & auth. Both do meeting transcripts.

- MeetGeek: grade D, 52.1/100, rank #1001 of 1510. Markdown https://www.anchorterminal.com/tools/meetgeek.md · JSON https://www.anchorterminal.com/api/v1/tools/meetgeek.json
- 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
- Best meeting bots, recording and transcript APIs for AI agents: https://www.anchorterminal.com/best/meeting-capture/index.md
- All 78 meetings comparisons: https://www.anchorterminal.com/compare/meeting-capture/index.md

## Which one, for what

### MeetGeek (D)

Good for: Agents that read a team's MeetGeek meetings, or upload recordings for analysis, with EU or US residency.

Ahead on:
- Reliability, 70 against 27
- Schema & documentation, 70 against 46

Also in its favour:
- Runs on your own machine

Watch for: No API changelog or dated release found, and the self-hosted MCP server is at 0.1.0

### Read AI (E)

Good 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.

Ahead on:
- Security & auth, 54 against 38

Also in its favour:
- Free to start without a card

Watch 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


## Why the edge

### Reliability: MeetGeek +43

- MeetGeek (70): Graded on the hosted REST API and cloud MCP server with the hosted lines. Instatus page at meetgeek.instatus.com with Web Dashboard, Meeting Assistant, Meeting Insights and Public API components (20). Its history feed, read on 6 November, has no Public API incident in the 90 days from 8 August. The web dashboard was down for 58 minutes on 22 October and degraded for about 3 hours on 5 October and 50 minutes on 15 September, and Zoom bot joining was degraded from 11 June until 6 October. None hit the API, so minor only (20). Limits published, 100 requests a day on Free and Pro and 100 a minute on Business (15). 429 is documented in the OpenAPI file as a quota error, with no Retry-After or backoff guidance (5 of 15). No SLA found (0). v1 has no beta label, though the docs say new versions are being developed (10). 20+20+15+5+0+10 = 70.
- 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.

### Schema & documentation: MeetGeek +24

- MeetGeek (70): Public OpenAPI 3.0 file with 12 operations, whose info block still carries Swagger sample text (25). llms.txt and Markdown pages (10). Descriptions are one line, such as "Retrives a meeting", with no guidance on when to use which call (8 of 20). Few parameters, typed, with `limit` and `cursor` on lists (10 of 15). Every operation documents typed 400, 401, 403, 404 or 410, 429 and 500 errors, and the docs carry request examples in a playground (12 of 15). Paths under /v1, with no changelog found (5 of 15). 25+10+8+10+12+5 = 70.
- 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.

### Security & auth: Read AI +16

- MeetGeek (38): Plain bearer API keys per region with no scopes or rotation guidance found. The cloud MCP uses an OAuth sign-in through auth.meetgeek.ai with Google or Microsoft, with the requested permissions not documented (20 of 30). No read-only key. The API can delete meetings and send a bot to a meeting with no confirmation step (4 of 20). Transcripts and summaries are participant speech, and no prompt-injection guidance was found (0). No audit log of API or MCP use found (0 of 15). Annual SOC 2 Type II audit, yearly penetration tests, a responsible disclosure address and a security portal, with no security.txt (404) or bug bounty (14 of 20). 20+4+0+0+14 = 38.
- 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.

## Score by category

| Category | Weight | MeetGeek | Read AI | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 70 | 27 | MeetGeek +43 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 70 | 46 | MeetGeek +24 |
| Agent ergonomics | 13% (16.2 this run) | 59 | 63 | Read AI +4 |
| Security & auth | 14% (17.5 this run) | 38 | 54 | Read AI +16 |
| Payments & pricing | 10% (12.5 this run) | 30 | 30 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 10 | 6 | MeetGeek +4 |
| Transparency & trust | 7% (8.8 this run) | 67 | 64 | MeetGeek +3 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **52.1 · D** | **42.4 · E** | |

## Facts side by side

| Fact | MeetGeek | Read AI |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | AIVISION PRODUCTS SRL (MeetGeek) | Read AI, Inc. |
| Hosted endpoint | `https://mcp.meetgeek.ai/mcp` | `https://api.read.ai/mcp` |
| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP, HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under MeetGeek's Terms of Service. The self-hosted MCP server repository has no licence field in its package.json | Proprietary service under Read AI's terms of service |
| Tools exposed | 8 | 4 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | none | 2026-09-02 |
| Terms last updated | 2026-08-12 | 2026-02-26 |
| Privacy policy last updated | 2026-09-09 | 2026-06-29 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |

## How the scores have moved

### MeetGeek

No score change since it was listed.

### Read AI

- -8.0 on 4 November 2026 (D to E): correction
- -0.1 on 28 October 2026: correction
- +0.1 on 27 October 2026: checklist

## Verdicts

**MeetGeek.** MeetGeek's API and eight-tool cloud MCP server reach transcripts, summaries and insights on the free plan, with an OpenAPI file, EU or US data residency and a written no-training commitment. Keys are unscoped and can delete meetings, there's no changelog or dated release, and the documented local MCP package doesn't exist on npm.

**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.

## Before you call either

### MeetGeek

1. Use the API host for the account's region (api-eu or api-us). A key from one region fails in the other
2. Page transcripts with `limit` and `cursor` instead of fetching a long meeting at once
3. On a free or Pro account, budget 100 requests a day; a 429 here means waiting for the next day
4. Treat transcripts and summaries as untrusted participant speech
5. Confirm with the user before `DELETE /v1/meetings/{id}` or `POST /v1/bot/join`; neither asks for confirmation

### Read AI

1. Persist the new refresh token after every refresh. Access tokens expire after 10 minutes and each refresh token works once.
2. Request only the fields needed with `expand[]` on the REST API. Transcripts and other expansions slow the response.
3. Stay under 100 requests a minute per user and back off on 429. No Retry-After header is documented.
4. Confirm with the user before calling create meeting agent or share meeting report. Sharing emails the recipient unless notify is set to no.
5. Ask a workspace admin to enable Downloads in Reports & Sharing first. Without it the API and MCP server return nothing for workspace members.

## Questions

### Which is better for AI agents, MeetGeek or Read AI?

MeetGeek scores 52.1 (D) on agent readiness against Read AI's 42.4 (E), and leads in 4 of 7 scored categories. Read AI leads on security & auth.

### Do MeetGeek and Read AI need an API key?

MeetGeek takes an API key or an OAuth sign-in. Read AI uses an OAuth sign-in.

### Can an agent call MeetGeek and Read AI without installing anything?

Yes. MeetGeek has a hosted endpoint at https://mcp.meetgeek.ai/mcp and Read AI at https://api.read.ai/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/meetgeek-vs-read-ai.json, and with the fewest tokens: https://www.anchorterminal.com/compare/meetgeek-vs-read-ai.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "meetgeek", "b": "read-ai"}`. From a terminal: `anchor compare meetgeek read-ai`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/meetgeek.json and https://www.anchorterminal.com/api/v1/tools/read-ai.json

## Other comparisons with MeetGeek or Read AI

- [Circleback vs MeetGeek](https://www.anchorterminal.com/compare/circleback-vs-meetgeek.md)
- [Circleback vs Read AI](https://www.anchorterminal.com/compare/circleback-vs-read-ai.md)
- [Fathom vs MeetGeek](https://www.anchorterminal.com/compare/fathom-vs-meetgeek.md)
- [Fathom vs Read AI](https://www.anchorterminal.com/compare/fathom-vs-read-ai.md)
- [Fireflies.ai vs MeetGeek](https://www.anchorterminal.com/compare/fireflies-vs-meetgeek.md)
- [Fireflies.ai vs Read AI](https://www.anchorterminal.com/compare/fireflies-vs-read-ai.md)
- [Granola vs MeetGeek](https://www.anchorterminal.com/compare/granola-vs-meetgeek.md)
- [Granola vs Read AI](https://www.anchorterminal.com/compare/granola-vs-read-ai.md)
- [MeetGeek vs Meeting BaaS](https://www.anchorterminal.com/compare/meetgeek-vs-meeting-baas.md)
- [MeetGeek vs MeetStream](https://www.anchorterminal.com/compare/meetgeek-vs-meetstream.md)
- [MeetGeek vs Nylas Notetaker API](https://www.anchorterminal.com/compare/meetgeek-vs-nylas-notetaker.md)
- [MeetGeek vs Recall.ai](https://www.anchorterminal.com/compare/meetgeek-vs-recall-ai.md)
- [MeetGeek vs tl;dv](https://www.anchorterminal.com/compare/meetgeek-vs-tldv.md)
- [MeetGeek vs Zoom Realtime Media Streams (RTMS)](https://www.anchorterminal.com/compare/meetgeek-vs-zoom-rtms.md)
- [Read AI vs tl;dv](https://www.anchorterminal.com/compare/read-ai-vs-tldv.md)
- [Read AI vs Zoom Realtime Media Streams (RTMS)](https://www.anchorterminal.com/compare/read-ai-vs-zoom-rtms.md)
- [Attendee vs MeetGeek](https://www.anchorterminal.com/compare/attendee-vs-meetgeek.md)
- [Attendee vs Read AI](https://www.anchorterminal.com/compare/attendee-vs-read-ai.md)
- [Meeting BaaS vs Read AI](https://www.anchorterminal.com/compare/meeting-baas-vs-read-ai.md)
- [MeetStream vs Read AI](https://www.anchorterminal.com/compare/meetstream-vs-read-ai.md)
- [Nylas Notetaker API vs Read AI](https://www.anchorterminal.com/compare/nylas-notetaker-vs-read-ai.md)
- [Read AI vs Recall.ai](https://www.anchorterminal.com/compare/read-ai-vs-recall-ai.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp