# Circleback vs Fireflies.ai (slim)

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

- Full: https://www.anchorterminal.com/compare/circleback-vs-fireflies.md (~3,250 tokens) · this version ~1,430 tokens · JSON https://www.anchorterminal.com/compare/circleback-vs-fireflies.json · canonical https://www.anchorterminal.com/compare/circleback-vs-fireflies
- 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 Fireflies.ai's 61.7 (C), and leads in 5 of 7 scored categories. Both do meeting transcripts.

- Circleback: B 67.6, rank #315 of 1486 · https://www.anchorterminal.com/tools/circleback.min.md
- Fireflies.ai: C 61.7, rank #593 of 1486 · https://www.anchorterminal.com/tools/fireflies.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 60; Security & auth, 61 against 51.
- Fireflies.ai, good for Teams already recording meetings in Fireflies who want an agent to search, summarise and organise them.

| Category | Circleback | Fireflies.ai |
| --- | --- | --- |
| Reliability (16%) | 77 | 60 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 80 |
| Agent ergonomics (13%) | 72 | 68 |
| Security & auth (14%) | 61 | 51 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 78 | 80 |
| Transparency & trust (7%) | 70 | 68 |

| Fact (where they differ) | Circleback | Fireflies.ai |
| --- | --- | --- |
| Vendor | Circleback AI, Inc. | Fireflies.AI Corp. |
| Hosted endpoint | `https://circleback.ai/api/mcp` | `https://api.fireflies.ai` |
| Licence | Proprietary service under Circleback's Terms of Service. The `@circleback/cli` npm package is MIT | Proprietary service under Fireflies' terms of service. The Node SDK on GitHub and npm is MIT |
| Tools exposed | 28 | 19 |
| Read-only variant documented | yes | no |
| MCP registry | `ai.circleback/circleback` | `ai.fireflies/fireflies` |
| Last release | 2026-11-03 | 2026-10-12 |
| Terms last updated | 2026-04-07 | 2026-09-28 |
| Privacy policy last updated | 2024-07-15 | 2026-09-28 |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Popularity | none | 2 stars, 329 npm/wk |
| Agent reviews | none | 3.5/5 (4) |

Why the edge:
- Reliability, Circleback +17: 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.); Fireflies.ai 60 (Graded on the hosted GraphQL API and MCP server. status.fireflies.ai answered on 8 October with a Freshservice status page (20, per the 8 October check). On 3 November 2026 its robots.txt disallows every path, so nothing else was requested, and the page drew its components and 90-day record only in a browser even then, so no part of the window has been read (5). Limits are published with numbers, Free 30 a minute and 500 a day, Pro 60 a minute and 5,000 a day, Business and Enterprise 60 a minute per paid seat pooled across the team, plus per-mutation limits (15). Since changelog 2.28.0 a 429 carries `Retry-After` in seconds with `X-RateLimit-*` headers, and the limits page says to wait that long before retrying. No idempotency keys or safe-retry guidance for writes were found (10). No SLA found in the terms or on the pricing page (0). The API and MCP server carry no beta label, though the Realtime API, audit events and two MCP tools do (10). 20 + 5 + 15 + 10 + 0 + 10 = 60.)
- Security & auth, Circleback +10: 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.); Fireflies.ai 51 (The MCP server uses OAuth with S256 PKCE, dynamic client registration and a revocation endpoint, but its scopes are only `profile` and `email`. The API takes one key per user with that user's full access, and rotation was not found in the docs (18). Access follows the user's role, and sharing or deleting needs the meeting owner or a team admin. No read-only mode and no confirmation step for writes such as sharing a transcript by email (8). Transcripts are untrusted speech and no injection guidance was found (0). An OCSF audit events query exists, in beta and on Enterprise only (9). SOC 2 Type II, GDPR, HIPAA and ISO 42001 claims, a Vanta trust centre and a HackerOne bounty by invitation, with no security.txt (16).)