# Circleback vs Meeting BaaS (slim)

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

- Full: https://www.anchorterminal.com/compare/circleback-vs-meeting-baas.md (~4,350 tokens) · this version ~2,480 tokens · JSON https://www.anchorterminal.com/compare/circleback-vs-meeting-baas.json · canonical https://www.anchorterminal.com/compare/circleback-vs-meeting-baas
- 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 Meeting BaaS's 59.9 (C), and leads in 3 of 7 scored categories. Meeting BaaS leads on schema & documentation, payments & pricing and maintenance & community. Both do meeting transcripts.

- Circleback: B 67.6, rank #315 of 1486 · https://www.anchorterminal.com/tools/circleback.min.md
- Meeting BaaS: C 59.9, rank #671 of 1486 · https://www.anchorterminal.com/tools/meeting-baas.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 62; Security & auth, 61 against 46. Also No incidents deducted, where Meeting BaaS loses 6 points for them.
- Meeting BaaS, good for Developers building a notetaker, sales or compliance recorder who want one API across Zoom, Meet and Teams, EU hosting, their own storage or a self-hosted deployment. Ahead on Schema & documentation, 93 against 81; Payments & pricing, 40 against 30; Maintenance & community, 85 against 78.

| Category | Circleback | Meeting BaaS |
| --- | --- | --- |
| Reliability (16%) | 77 | 62 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 93 |
| Agent ergonomics (13%) | 72 | 73 |
| Security & auth (14%) | 61 | 46 |
| Payments & pricing (10%) | 30 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 78 | 85 |
| Transparency & trust (7%) | 70 | 69 |

| Fact (where they differ) | Circleback | Meeting BaaS |
| --- | --- | --- |
| Vendor | Circleback AI, Inc. | SAS SPOKE |
| Hosted endpoint | `https://circleback.ai/api/mcp` | `https://api.meetingbaas.com` |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Pay per use |
| Licence | Proprietary service under Circleback's Terms of Service. The `@circleback/cli` npm package is MIT | Proprietary hosted service under SAS SPOKE's terms. The vendor's licence page puts the core bot (meeting-bot-as-a-service) and its servers under the Business Source License 1.1. Meeting-Baas/meet-teams-bot, under the Elastic License 2.0 on 8 October 2026, no longer answers a public clone. The TypeScript SDK and the MCP servers are MIT |
| Tools exposed | 28 | none |
| Read-only variant documented | yes | no |
| MCP registry | `ai.circleback/circleback` | not listed |
| Last release | 2026-11-03 | 2026-10-30 |
| Terms last updated | 2026-04-07 | 2026-10-05 |
| Privacy policy last updated | 2024-07-15 | 2026-10-05 |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | none | 113 stars, 1.9k npm/wk |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Reliability, Circleback +15: 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.); Meeting BaaS 62 (Graded on the hosted v2 API with the hosted lines. The vendor's own status page at status.meetingbaas.com shows seven components with 30-day bars (20). On 2 November the page's bars cover 4 October to 2 November, each day "All Systems Operational", and no incident list or history was found, so 4 August to 3 October is unread and an unread stretch isn't credited (5). Release v2.6.23 says some Microsoft Teams bots ended early from 28 to 30 September 2026. Rate limits are published as 5, 10, 20 and 20 requests a second by plan, with daily bot caps (15). 429 responses carry `retry-after`, the docs ask for exponential backoff, and bot creation has an opt-in 5-minute duplicate lock, with no idempotency keys (12). The terms promise best efforts for 24/7 access with no figure (0). v2 is the current API at v2.6.39 with no beta label (10).)
- Security & auth, Circleback +15: 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.); Meeting BaaS 46 (Team API keys in a header with two levels, Full Access and Sending Access, and several keys per team. The assistant connector uses OAuth with one-hour tokens. Key expiry and rotation tooling weren't found in the docs (22). Sending Access can only create bots. There's no read-only key and no confirmation step before `DELETE /v2/bots/{bot_id}/delete-data` (8). Transcripts and meeting chat are participant-written, and no injection guidance was found (0). Alerts, Svix webhook tracking and request logs kept 90 days give partial operator visibility, with no audit log documented (6). A disclosure address on the security page, a SECURITY.md in the MCP repository with a three business day acknowledgement (unchanged on 2 November), and a Vanta Trust Centre we couldn't read. No security.txt, no bug bounty found, and no SOC 2 report of the vendor's own confirmed (8).)
- Schema & documentation, Meeting BaaS +12: Circleback 81 (Each reference page embeds the OpenAPI 3.2 operation for its endpoint, but no single spec file is linked, and MCP input schemas need a sign-in (20 of 25). llms.txt and a Markdown copy of each docs page (10). Operation descriptions state what is returned and who may act, such as only the owner deleting a meeting, and the update call explains replace semantics (16 of 20). Typed parameters with enums and defaults, such as `ownership` All, Mine or Shared (13 of 15). curl examples, a JSON error envelope with `error` and `code`, and 400 and 429 responses per operation (12 of 15). Paths carry no version, and a public releases page dates each entry (10 of 15). 20+10+16+13+12+10 = 81.); Meeting BaaS 93 (Public OpenAPI 3.1 spec at api.meetingbaas.com/v2/openapi.json, 73 operations (25). An llms index at docs.meetingbaas.com/llms.txt with Markdown bundles per section (10). 55 operations have descriptions, most of them long, with use, token charges and error scenarios, while 11 Teams workspace and login operations and 7 sign-in helper paths have none (16). 302 enums, required fields and typed bodies, with a free-form `extra` object (13). 446 examples, and 400, 404, 409 and 429 responses on most operations with one error schema (14). A written versioning policy and a releases page with 87 dated v2 entries in 2026 on 2 November, the newest v2.6.39 (15). Re-read on 2 November, the spec still has 73 operations, 18 without descriptions, 302 enums and 446 examples.)
- Payments & pricing, Meeting BaaS +10: 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.); Meeting BaaS 40 (No x402, MPP or L402 (0). Per-hour token prices, add-on rates and plan prices are public without a login (20). 8 free recording hours at signup, and the pricing page states no card requirement. We didn't create an account to confirm (20). A person signs up in a browser to get a key (0).)
- Maintenance & community, Meeting BaaS +7: 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.); Meeting BaaS 85 (v2.6.39 shipped on 30 October 2026 (30). Eleven dated v2 releases since the 8 October check alone (v2.6.29 to v2.6.39), 50 from v2.4.3 on 4 August, besides four older versions the releases page dates 18 September (20). A public releases page, a support centre, email and a Discord server. We couldn't measure reply times (12). The official TypeScript SDK is at 6.2.13, tagged 23 October 2026, with 12 tags since 10 August (15). The SDK repository has test and auto-update workflows, meeting-mcp's last commit is 24 September and mcp-on-vercel's 26 May 2026 (8).)