# Circleback vs Recall.ai (slim)

> Circleback scores 67.6 (B) to Recall.ai's 59.7 (C) for meeting transcripts. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/circleback-vs-recall-ai.md (~3,950 tokens) · this version ~2,230 tokens · JSON https://www.anchorterminal.com/compare/circleback-vs-recall-ai.json · canonical https://www.anchorterminal.com/compare/circleback-vs-recall-ai
- 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)

Circleback scores 67.6 (B) on agent readiness against Recall.ai's 59.7 (C), and leads in 6 of 7 scored categories. Recall.ai leads on payments & pricing. Both do meeting transcripts.

- Circleback: B 67.6, rank #315 of 1486 · https://www.anchorterminal.com/tools/circleback.min.md
- Recall.ai: C 59.7, rank #681 of 1486 · https://www.anchorterminal.com/tools/recall-ai.min.md
- Circleback, good for Agents that need a person's meeting notes, transcripts and action items from a notetaker they already use, including on Free. Ahead on Reliability, 77 against 50; Security & auth, 61 against 54; Maintenance & community, 78 against 63.
- Recall.ai, good for Developers building a notetaker or meeting agent who want one API across Zoom, Google Meet, Teams and Webex and will handle summaries, consent and per-customer access themselves. Ahead on Payments & pricing, 35 against 30.

| Category | Circleback | Recall.ai |
| --- | --- | --- |
| Reliability (16%) | 77 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 80 |
| Agent ergonomics (13%) | 72 | 71 |
| Security & auth (14%) | 61 | 54 |
| Payments & pricing (10%) | 30 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 78 | 63 |
| Transparency & trust (7%) | 70 | 67 |

| Fact (where they differ) | Circleback | Recall.ai |
| --- | --- | --- |
| Vendor | Circleback AI, Inc. | Hyperdoc Inc. |
| Hosted endpoint | `https://circleback.ai/api/mcp` | `https://us-west-2.recall.ai` |
| Pricing | Freemium | Pay per use |
| Licence | Proprietary service under Circleback's Terms of Service. The `@circleback/cli` npm package is MIT | Proprietary service under Recall.ai's terms of use. Sample apps on GitHub, some MIT and most with no licence file |
| Tools exposed | 28 | 45 |
| Read-only variant documented | yes | no |
| MCP registry | `ai.circleback/circleback` | not listed |
| Last release | 2026-11-03 | 2026-10-08 |
| Terms last updated | 2026-04-07 | 2026-10-01 |
| Privacy policy last updated | 2024-07-15 | 2023-02-01 |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | none | 91k npm/wk |
| Agent reviews | none | 3.5/5 (4) |

Why the edge:
- Reliability, Circleback +27: Circleback 77 (Graded on the hosted REST API and MCP server with the hosted lines. incident.io status page at status.circleback.ai with four components, none of them the API (20). Its history and RSS feed, read on 6 November, list no incident from August to November and no item at all, so the page isn't shown to post incidents and the quiet window isn't credited as clean, as for tldv (20). Limits published per plan, 3 a second and 20 a minute on Free and 20 and 300 on paid plans (15). 429 carries Retry-After and every response carries RateLimit-Limit, -Remaining and -Reset. No idempotency key or safe-retry guidance for writes (12 of 15). No SLA found in the Terms or on the pricing page (0). The API has no beta label (10). 20+20+15+12+0+10 = 77.); Recall.ai 50 (Graded on the hosted lines for the REST API. No public status page was found. The site and docs link none, status.recall.ai doesn't resolve, and service status is exposed only through MCP tools that need a login (0). No readable incident history (5). Rate limits are published per endpoint and per workspace, such as 120 requests a minute for Create Bot, 60 for list endpoints and 300 for retrieve endpoints (15). 429 and 507 carry `Retry-After`, 409 asks for exponential backoff, and `Idempotency-Key` covers every POST, PUT and PATCH for one hour (15). The pricing page lists uptime guarantees on Enterprise only, with no published figure (5). The bot API is generally available. GoTo Meeting support is beta (10). Per the 8 October check, not re-read on 4 November, because Recall.ai's terms bar automated access to the non-API parts of the service.)
- Maintenance & community, Circleback +15: Circleback 78 (`@circleback/cli` 1.2.1 published on 3 November 2026 and a release entry on 2 November (30). Dated entries in the 90 days from 8 August, among them the API on 20 August, importing through the API on 9 September, writes through MCP, CLI and API on 7 October and folders in the API on 30 October, with CLI releases 0.9.0 to 1.2.1 since 6 October (20). A public releases page and a support address, with no public issue tracker (8 of 15). In the official MCP registry as ai.circleback/circleback (15). The CLI is MIT with tests and a typecheck step in its scripts and a postinstall that only prints a welcome line. Its repository isn't public (5 of 10). 30+20+8+15+5 = 78.); Recall.ai 63 (Desktop Recording SDK 2.0.36 reached npm on 8 October 2026, and the Create Bot reference was updated on 23 September (30, 27 days before 4 November). The SDK changelog has nine dated entries between 20 July and 25 September 2026. The API has no changelog of its own, so 15 of 20. Support by email and dashboard chat on every plan and a shared Slack channel on contract plans, with no public forum or issue tracker for the API (8). The Desktop SDK on npm is current. No REST client library, and the MCP server wasn't found in the official MCP registry (5). The SDK publishes nightly builds. We couldn't see its CI (5). Per the 8 October check, not re-read on 4 November, because Recall.ai's terms bar automated access to the non-API parts of the service.)
- Security & auth, Circleback +7: Circleback 61 (OAuth with dynamic client registration and two scopes on MCP, and API keys that are read-only or read and write, shown once (28 of 30). Read-only keys and a read-only MCP scope, and only an owner can delete a meeting. No confirmation step on the API for shares or deletes (14 of 20). Transcripts, notes and emails are participant-written text, and no prompt-injection guidance was found (0). A usage dashboard for workspace admins and meeting access requests, with no audit log of API or MCP calls found (4 of 15). SOC 2 Type II, EU-U.S. Data Privacy Framework certification, HIPAA, an external penetration test report on the security portal and a valid security.txt. No bug bounty found (15 of 20). 28+14+0+4+15 = 61.); Recall.ai 54 (REST API keys are revocable but don't expire and carry no scopes, so one key reaches the whole workspace. The MCP server takes OAuth with PKCE and dynamic client registration or MCP API keys, both limited by 22 scopes that can't change after creation (23). MCP is read-only by default, with separate write and developer scopes. The REST API has no read-only key and no confirmation step, and deleting a recording or removing a bot is permanent (11). Transcripts and meeting chat are participant-written, and no prompt-injection guidance was found (0). The Explorer dashboard and MCP tools show per-bot and workspace logs and webhook deliveries. No audit log of user or key actions was found (8). The site links a SOC 2 Type 2 report and an ISO 27001 certificate in a Vanta trust centre we couldn't render. security.txt returns 404, and no bug bounty or disclosure policy was found (12). Per the 8 October check, not re-read on 4 November, because Recall.ai's terms bar automated access to the non-API parts of the service.)
- Payments & pricing, Recall.ai +5: Circleback 30 (No x402, MPP or L402 (0). Seat prices are public, $15 and $25 a user a month, with nothing priced per call (10). The Free plan includes API, MCP and CLI access with 30 days of history and costs nothing. A card isn't mentioned for it (20). A person signs up in a browser and creates a key or approves OAuth (0). 0+10+20+0 = 30.); Recall.ai 35 (No x402, MPP or L402. The API's 402 is a credit-balance error (0). Per-unit prices are public, at $0.50 an hour of recording, $0.15 an hour of built-in transcription and $0.000069 per recording-hour per stored hour after seven days (20). The first five hours of recording are free, and the billing docs describe adding a payment method as a later step. We didn't walk through signup to confirm no card is asked for (15). A person signs up in a browser and creates the first key in the dashboard (0). Per the 8 October check, not re-read on 4 November, because Recall.ai's terms bar automated access to the non-API parts of the service.)