Pipecat vs Bolna

Agent ops

1. ai-native userMy coding agent can provision a complete voice agent end to end — create the agent, attach a number, and place a call — through the API, CLI, or MCP without touching the dashboard

   weight 3 · round to Bolna
   Pipecat~partialprobed3/10

   Pipecat provides a CLI (`pipecat init`, `pipecat cloud`, `pipecat context-hub`) and code-level telephony hooks (`python bot.py -t twilio -x ngrok...`) that let a coding agent scaffold and run a bot, and the context-hub can register an MCP server for coding-agent tooling, but there is no documented single API/CLI/MCP flow that creates the agent, provisions/attaches a phone number, and places a call — telephony setup still relies on the carrier's (Twilio/Telnyx) own console/API for number purchase and webhook config. missing for 10: a unified provisioning API or CLI command that attaches a phone number and places a call, MCP-driven agent creation (context-hub only builds a docs index, not agent provisioning), evidence of number attachment without touching a carrier dashboard.

   • [claimed-docs] “Telephony bots have a different shape than WebRTC bots. The session doesn't start because a client sent your dispatcher an HTTP request — it…”
   • [claimed-docs] “the carrier (Twilio, Telnyx, Plivo, Exotel, or your SIP provider) is calling your webhook to tell you there's an inbound call”
   • [claimed-docs] “python bot.py -t twilio -x your-name.ngrok.io”
   • [claimed-docs] “pipecat init quickstart # Change to the project directory cd pipecat-quickstart”
   • [claimed-docs] “pipecat init quickstart”
   • [claimed-docs] “pipecat context-hub install registers the hub as an MCP server with your coding agent and builds the local index”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Pipecat CLI (pypi pipecat-ai[cli]) ran keylessly via uvx — `pipecat --help` lists init (pr…”

   proof ↗⚑ flag

   Bolna✓fullprobed8/10

   Bolna offers all three surfaces needed for agent-native provisioning: a documented API quickstart to create an agent, attach a number, and place a call (bolna-docs-14, bolna-docs-15), a native Go CLI to manage agents, calls, and phone numbers from the terminal (bolna-docs-16, bolna-probe-4), and an official MCP server to connect Claude/Cursor/Windsurf clients (bolna-docs-17, bolna-probe-3), all without requiring dashboard interaction. missing for 10: independent/hands-on confirmation that MCP or CLI can complete the full create-attach-call flow end-to-end (only vendor docs), and no OpenAPI spec was resolvable (bolna-probe-2) to verify API completeness.

   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”
   • [claimed-docs] “Click the Create a new API Key button to generate your unique authentication credentials.”
   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [probe] “official MCP server documented at https://www.bolna.ai/docs/build-with-ai/mcp”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.bolna.ai/openapi.json, https://docs.bolna.ai/swagger.json, https://docs.bolna.ai/api/op…”

   proof ↗⚑ flag

2. ai-native userThe platform's own AI helps me author agents — generating or improving prompts, flows, and test cases from a description

   weight 1 · round drawn
   Pipecat—none0/10

   Evidence shows Pipecat has a context-hub that registers as an MCP server so external coding agents (e.g. Claude) can get context about the framework, and an Evals system for testing agent behavior — but these rely on the user writing prompts/flows/tests and connecting third-party AI tools, not Pipecat's own AI generating or improving prompts, flows, or test cases from a description. No evidence of an in-platform AI assistant that authors agent configs.

   • [claimed-docs] “pipecat context-hub install registers the hub as an MCP server with your coding agent and builds the local index”
   • [claimed-docs] “pipecat context-hub install` registers the hub as an MCP server with your coding agent and builds the local index”
   • [claimed-docs] “Pipecat Evals is the framework's built-in system for testing agent behavior. You describe a conversation and the behavior you expect, and Pi…”
   • [claimed-docs] “You describe a conversation and the behavior you expect, and Pipecat runs it against your real agent (the same pipeline, the same services, …”

   proof ↗⚑ flag

   Bolna—none0/10

   No evidence shows Bolna's own platform AI generating or improving prompts, flows, or test cases from a description; the closest feature (build-with-ai/mcp) is an MCP server that lets external AI clients like Claude or Cursor manage the account via API, not the platform itself authoring agents. Templates can be cloned, but that's static copying, not AI-generated authoring.

   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [claimed-docs] “Clone any template and customize it for your business.”

   proof ↗⚑ flag

Build

1. developerBuild a working phone voice agent — prompt, voice, and phone number — and take my first live call within an hour

   weight 3 · round to Bolna
   Pipecat~partialprobed7/10

   Pipecat's quickstart gets a browser voice bot running in ~5 minutes with prompt+voice configurable across 200+ providers, and the telephony guide shows the same bot file working with real carriers (Twilio/Telnyx/Plivo) via a one-line command with ngrok tunneling, so all three pieces (prompt, voice, phone number) are documented and connectable to the same codebase. However, the telephony path is a separate 'production' doc requiring carrier account setup/ngrok tunneling not folded into the 5-minute quickstart, and there's no first-party or independent account of someone going from zero to a live phone call within an hour. Missing for 10: an end-to-end timed walkthrough combining phone-number provisioning with the quickstart, and independent hands-on confirmation of the 'first live call within an hour' claim.

   • [claimed-docs] “Build and run your first Pipecat voice AI bot in under 5 minutes”
   • [claimed-docs] “Build and run your first Pipecat voice AI bot in under 5 minutes: a simple conversational agent you can talk to in a browser.”
   • [claimed-docs] “python bot.py -t twilio -x your-name.ngrok.io”
   • [claimed-docs] “the carrier (Twilio, Telnyx, Plivo, Exotel, or your SIP provider) is calling your webhook to tell you there's an inbound call”
   • [claimed-docs] “Telephony bots have a different shape than WebRTC bots. The session doesn't start because a client sent your dispatcher an HTTP request — it…”
   • [claimed-docs] “Swap speech, language, and vision services from any of 200+ integrated providers and services — usually one line of code.”
   • [claimed-docs] “Any Transport: WebRTC, SIP, PSTN”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Pipecat CLI (pypi pipecat-ai[cli]) ran keylessly via uvx — `pipecat --help` lists init (pr…”
   • [probe] “PROBE runtime (recorded 2026-09-05): pypi pipecat-ai 1.8.1 (BSD-2 OSS) installs and `import pipecat` succeeds with no key, printing its star…”

   proof ↗⚑ flag

   Bolna✓fullclaimed8/10

   Docs directly support the story: templates can be cloned and customized, build/deploy claimed under 5 minutes, voice/accent selection, phone number and telephony setup (BYOT/SIP), and a quickstart walking through key verification, agent creation, placing a call, and fetching a transcript in ~5 minutes. This covers prompt (agent config/templates), voice (voice/provider selection), and phone number (telephony/SIP) end-to-end for a first live call within an hour. Missing for 10: independent/hands-on confirmation of the 'under 5 minutes' or 'first call in an hour' claims beyond vendor docs, and no third-party success report.

   • [claimed-docs] “Build and deploy in under 5 minutes”
   • [claimed-docs] “Clone any template and customize it for your business.”
   • [claimed-docs] “You can choose different voices, accents, and speaking styles to match your brand.”
   • [claimed-docs] “Bring Your Own Telephony (BYOT) lets you connect any standards-compliant SIP trunk to the Bolna platform.”
   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”
   • [claimed-docs] “Bolna supports Deepgram, Azure, ElevenLabs, and more.”

   proof ↗⚑ flag

2. developerRun conversations in multiple languages, including detecting and switching language mid-call

   weight 2 · round to Bolna
   Pipecat—none0/10

   The evidence mentions swapping speech/language services across providers (one line of code) but nothing about detecting a spoken language mid-call or dynamically switching STT/TTS/LLM language settings within an active conversation. No docs, community reports, or runtime probes address multilingual or language-switching behavior. missing for 10: language detection mechanism, mid-call language switching mechanism, any docs/demo showing multilingual conversation handling.

   • [claimed-docs] “Swap speech, language, and vision services from any of 200+ integrated providers and services — usually one line of code.”

   proof ↗⚑ flag

   Bolna~partialclaimed6/10

   Docs claim the agent "detects and switches mid-call on its own" and marketing mentions "multilingual intelligence" for thousands of calls, directly supporting the story, but there's no detail on supported languages, configuration options, or independent/hands-on verification of mid-call switching reliability. Missing for 10: language list/configuration docs, hands-on or third-party confirmation of switching accuracy, and edge-case handling details.

   • [claimed-docs] “the agent detects and switches mid-call on its own”
   • [claimed-docs] “Power thousands of inbound and outbound calls every minute with human-like, multilingual intelligence”

   proof ↗⚑ flag

3. founderDesign multi-step conversation flows in a visual builder with branching, states, and handoffs without writing code

   weight 2 · round drawn
   Pipecat—none0/10

   Pipecat Flows lets you define branching conversation states via Python functions/config (docs-6, docs-22, docs-39), but this is a code-first framework with a CLI and Python SDK, not a visual drag-and-drop builder — no evidence pack item mentions any GUI/no-code flow designer. Since competing voice-agent platforms do offer visual builders, this is a fair axis to ask about, and Pipecat's evidence shows the opposite (functions/config authored in code).

   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: 1. Process data ... 2. Progress the conversation by transitioning between nodes”
   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: Process data by interfacing with external systems and APIs...Progress the conversation by…”
   • [claimed-docs] “Flows auto-derives the function's metadata — name, description, parameter properties (with their descriptions), and which parameters are req…”
   • [claimed-docs] “Hand off to subagents for long-running tools and complex tasks, and use Pipecat Flows when a conversation needs to follow a defined path.”

   proof ↗⚑ flag

   Bolna—none0/10

   Evidence shows Bolna is built around APIs, CLI, and MCP server for defining agents and multi-step outreach sequences (bolna-docs-12, bolna-docs-16, bolna-docs-17), but there is no mention of a visual/no-code builder with branching, states, or handoffs; workflows are described as 'driven entirely through the Bolna API.' Missing for 10: any visual flow-builder UI, drag-and-drop branching/state design, no-code handoff configuration.

   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”
   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [github] “Bolna is the end-to-end open source production ready framework for quickly building LLM based voice driven conversational applications.”

   proof ↗⚑ flag

Personalization

1. developerInject dynamic variables and per-caller context at call time so each conversation is personalized

   weight 2 · round drawn
   Pipecat—none0/10

   Evidence shows Pipecat Flows functions can process data and transition conversation state, and telephony bots receive caller info via webhook, but nothing documents a mechanism for injecting per-caller dynamic variables/context into the bot's prompt or state at call start for personalization. This is a fair capability to expect from a voice-agent framework, but no citation directly demonstrates it.

   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: 1. Process data ... 2. Progress the conversation by transitioning between nodes”
   • [claimed-docs] “Telephony bots have a different shape than WebRTC bots. The session doesn't start because a client sent your dispatcher an HTTP request — it…”
   • [claimed-docs] “Flows auto-derives the function's metadata — name, description, parameter properties (with their descriptions), and which parameters are req…”

   proof ↗⚑ flag

   Bolna—none0/10

   The evidence pack covers agent creation, extraction categories, call summaries, workflows, and providers, but nothing documents passing per-caller dynamic variables or context payloads at call time to personalize a conversation.

   ⚑ flag

2. developerGround the agent on my documents with a built-in knowledge base or RAG so it answers from my content

   weight 2 · round drawn
   Pipecat—none0/10

   Pipecat's docs describe voice/multimodal pipeline orchestration, function calling via Flows, telephony, evals, and a context-hub for coding-agent tooling — but nothing about a built-in knowledge base or RAG mechanism for grounding the agent on user documents. The closest hit (context-hub) indexes Pipecat's own docs/API for coding assistants, not user content for the voice agent.

   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: 1. Process data ... 2. Progress the conversation by transitioning between nodes”
   • [claimed-docs] “pipecat context-hub install registers the hub as an MCP server with your coding agent and builds the local index”
   • [claimed-docs] “pipecat context-hub install` registers the hub as an MCP server with your coding agent and builds the local index”

   proof ↗⚑ flag

   Bolna—none0/10

   Bolna is a voice AI agent platform (telephony, TTS/STT, LLM providers, workflows) but the evidence pack contains no mention of a knowledge base, document ingestion, or RAG capability for grounding agent responses in custom content. This axis clearly applies to conversational agent-building platforms, so absence of evidence yields 'none'.

   ⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Pipecat✓fullprobed9/10

   Pipecat provides a working llms.txt endpoint (confirmed HTTP 200 with agent-oriented summary) plus an explicit context-hub CLI feature that registers docs as an MCP server for coding agents and builds a local index, directly enabling agents to consume its docs programmatically. missing for 10: no independent/community confirmation of an agent successfully using llms.txt or context-hub end-to-end.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.pipecat.ai/llms.txt # Pipecat > Pipecat is an open source ecosystem for building voice and multimo…”
   • [claimed-docs] “pipecat context-hub install registers the hub as an MCP server with your coding agent and builds the local index”
   • [claimed-docs] “pipecat context-hub install` registers the hub as an MCP server with your coding agent and builds the local index”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Pipecat CLI (pypi pipecat-ai[cli]) ran keylessly via uvx — `pipecat --help` lists init (pr…”

   proof ↗⚑ flag

   Bolna✓fullprobed9/10

   A probe confirms llms.txt is live and returns 200 with structured agent-oriented doc links (bolna-probe-1), and Bolna also documents an official MCP server for connecting AI clients like Claude/Cursor to its docs/account (bolna-docs-17, bolna-probe-3), directly enabling agent-native consumption of its documentation. Missing for 10: no independent third-party confirmation that agents successfully use llms.txt in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.bolna.ai/llms.txt # Bolna Docs > Quickly build and deploy conversational Voice AI agents - [Home]…”
   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [probe] “official MCP server documented at https://www.bolna.ai/docs/build-with-ai/mcp”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Pipecat~partialprobed6/10

   Pipecat is a Python framework that is pip-installable with no key required and runs bots as scripts (bot.py) with a CLI supporting init, cloud deploy, and eval subcommands, which supports headless/CI-friendly automation; the Evals system explicitly runs conversations against the real agent programmatically, suitable for CI. However there is no explicit CI/CD example, no documented headless flag or non-interactive mode guidance, and the development runner is framed around local dev/demo UI rather than CI. missing for 10: explicit CI pipeline documentation/example, confirmation that pipecat.runner.run or bot.py can run fully headless without any UI/browser dependency, independent hands-on report of running Pipecat in an automated CI environment.

   • [claimed-docs] “Pipecat Evals is the framework's built-in system for testing agent behavior. You describe a conversation and the behavior you expect, and Pi…”
   • [claimed-docs] “You describe a conversation and the behavior you expect, and Pipecat runs it against your real agent (the same pipeline, the same services, …”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Pipecat CLI (pypi pipecat-ai[cli]) ran keylessly via uvx — `pipecat --help` lists init (pr…”
   • [probe] “PROBE runtime (recorded 2026-09-05): pypi pipecat-ai 1.8.1 (BSD-2 OSS) installs and `import pipecat` succeeds with no key, printing its star…”
   • [claimed-docs] “Pipecat ships a built-in development runner (pipecat.runner.run) that handles the server-side glue most bots need during development: creati…”
   • [claimed-docs] “python bot.py -t twilio -x your-name.ngrok.io”

   proof ↗⚑ flag

   Bolna~partialprobed6/10

   Bolna offers a CLI (single Go binary) for managing agents, calls, phone numbers, and batches from the terminal, plus a REST API for scripted call creation and transcript retrieval — both usable in CI/automation pipelines without a GUI. However, there's no explicit CI/pipeline example, headless-mode documentation, or exit-code/automation-specific guidance. missing for 10: explicit CI integration examples/guides, documented non-interactive/headless flags or exit codes, third-party confirmation of CI usage.

   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”
   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”
   • [claimed-docs] “Click the Create a new API Key button to generate your unique authentication credentials.”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Pipecat—none0/10

   The evidence only shows Pipecat's context-hub CLI *exposing itself* as an MCP server to a coding agent (docs-11/38) — the reverse of what the story asks (Pipecat consuming external MCP servers to gain their tools inside its voice-agent pipelines). No evidence shows Pipecat's Flows/function-calling system connecting to arbitrary MCP servers as a client.

   • [claimed-docs] “pipecat context-hub install registers the hub as an MCP server with your coding agent and builds the local index”
   • [claimed-docs] “pipecat context-hub install` registers the hub as an MCP server with your coding agent and builds the local index”

   proof ↗⚑ flag

   Bolna—none0/10

   Evidence shows Bolna ships an MCP *server* so external clients like Claude, Cursor, or Windsurf can control a Bolna account (bolna-docs-17, bolna-probe-3) — this is the reverse direction from the story, which asks whether Bolna's own agents can plug in external MCP servers to gain their tools. No evidence describes Bolna voice agents consuming or calling external MCP servers.

   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [probe] “official MCP server documented at https://www.bolna.ai/docs/build-with-ai/mcp”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Bolna
   Pipecat~partialprobed6/10

   Pipecat ships an official `pipecat context-hub install` CLI command that registers itself as an MCP server with a coding agent, building a local docs/examples index — confirmed both in docs and via a runtime CLI probe showing the `context-hub` subcommand exists. This is a genuine official MCP server for agent connection, but it's scoped narrowly to indexing Pipecat's own docs/examples for coding assistants rather than exposing Pipecat's runtime voice-agent capabilities to arbitrary MCP clients. Missing for 10: independent/hands-on confirmation that the MCP server actually functions end-to-end (only CLI help text was probed, not live MCP protocol behavior), and broader documentation of what tools/resources the MCP server exposes.

   • [claimed-docs] “pipecat context-hub install registers the hub as an MCP server with your coding agent and builds the local index”
   • [claimed-docs] “pipecat context-hub install` registers the hub as an MCP server with your coding agent and builds the local index”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Pipecat CLI (pypi pipecat-ai[cli]) ran keylessly via uvx — `pipecat --help` lists init (pr…”

   proof ↗⚑ flag

   Bolna✓fullprobed8/10

   Bolna documents an official MCP server that lets Claude, Cursor, Windsurf, or any MCP client connect to a Bolna account, confirmed by both docs and an independent probe hitting the live page. Missing for 10: independent hands-on validation or community confirmation of the MCP server working in practice beyond the docs/probe.

   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [probe] “official MCP server documented at https://www.bolna.ai/docs/build-with-ai/mcp”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Pipecat
   Pipecat✓fullprobed9/10

   Pipecat ships an official CLI (pip-installable pipecat-ai[cli], confirmed via runtime probe) supporting init/scaffolding, cloud deploy, eval, and context-hub (MCP registration for coding agents), well documented at docs.pipecat.ai/api-reference/cli/overview. This directly supports AI-native agentic workflows (context-hub install registers as MCP server, writes AGENTS.md/CLAUDE.md for coding agents). missing for 10: independent/third-party review of the CLI's robustness beyond vendor docs and a single runtime probe.

   • [probe] “PROBE runtime (recorded 2026-09-05): the official Pipecat CLI (pypi pipecat-ai[cli]) ran keylessly via uvx — `pipecat --help` lists init (pr…”
   • [probe] “official CLI documented at https://docs.pipecat.ai/api-reference/cli/overview”
   • [claimed-docs] “pipecat context-hub install registers the hub as an MCP server with your coding agent and builds the local index”
   • [claimed-docs] “Install the Pipecat CLI and scaffold the quickstart project (also writes AGENTS.md + CLAUDE.md)”
   • [claimed-docs] “pipecat context-hub install` registers the hub as an MCP server with your coding agent and builds the local index”

   proof ↗⚑ flag

   Bolna✓fullprobed8/10

   Bolna documents an official CLI (single Go binary) letting users manage agents, calls, phone numbers, and batches from the terminal, corroborated by a live docs probe confirming the page exists. missing for 10: no independent/hands-on community usage reports or version/release history confirming real-world adoption beyond first-party docs.

   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to Bolna
   Pipecat~partialprobed7/10

   Pipecat exposes a well-documented programmatic surface — a Python framework API (frame processors, Flows functions with auto-derived metadata), a runner API, and an official CLI (init/cloud/eval/context-hub) confirmed to work keylessly via runtime probe — giving AI-native users a documented, scriptable way to drive the product. However, probing shows no REST/OpenAPI spec (all openapi.json candidates 404'd), so there's no conventional network-callable public API, only the code-level Python/CLI surface. Missing for 10: a formal REST/OpenAPI-documented HTTP API, and independent hands-on confirmation of driving a full pipeline purely via that public API surface.

   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: 1. Process data ... 2. Progress the conversation by transitioning between nodes”
   • [claimed-docs] “Pipecat ships a built-in development runner (\`pipecat.runner.run\`) that handles the server-side glue most bots need during development”
   • [claimed-docs] “Pipecat ships a built-in development runner (pipecat.runner.run) that handles the server-side glue most bots need during development: creati…”
   • [claimed-docs] “Flows auto-derives the function's metadata — name, description, parameter properties (with their descriptions), and which parameters are req…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.pipecat.ai/openapi.json, https://docs.pipecat.ai/swagger.json, https://docs.pipecat.ai/…”
   • [probe] “official CLI documented at https://docs.pipecat.ai/api-reference/cli/overview”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Pipecat CLI (pypi pipecat-ai[cli]) ran keylessly via uvx — `pipecat --help` lists init (pr…”

   proof ↗⚑ flag

   Bolna✓fullprobed8/10

   Bolna provides a documented public API with quickstart, authentication, agent/call/extraction endpoints, and workflow automation entirely through the API, plus a CLI and MCP server built on top of it. Missing for 10: a discoverable OpenAPI/Swagger spec (probe found all standard OpenAPI paths 404) and independent third-party corroboration of API robustness.

   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”
   • [claimed-docs] “Click the Create a new API Key button to generate your unique authentication credentials.”
   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”
   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.bolna.ai/openapi.json, https://docs.bolna.ai/swagger.json, https://docs.bolna.ai/api/op…”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Pipecat—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bolna—none0/10

   Bolna documents API key creation but there is no evidence of scoped or least-privilege credential controls (e.g., role-based permissions, scoped tokens, restricted access levels) — only a single account-wide key generation flow is described.

   • [claimed-docs] “Click the Create a new API Key button to generate your unique authentication credentials.”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Pipecat
   Pipecat✓fullprobed9/10

   Pipecat is itself an official open-source Python SDK/framework (pip-installable, verified via runtime probe to install and import cleanly), and it also ships a family of official 'Pipecat Client' SDKs for web/mobile integration plus pre-built React components, all documented on the official site. Missing for 10: independent/third-party confirmation of the client SDKs' quality beyond docs (only the core Python framework was hands-on verified).

   • [claimed-docs] “Pipecat Clients are a family of SDKs that connect users to your Pipecat agents through web and mobile applications.”
   • [claimed-docs] “Pipecat Clients are a family of SDKs that connect users to your Pipecat agents through web and mobile applications. They handle real-time au…”
   • [claimed-docs] “Pre-built React components for voice AI interfaces.”
   • [claimed-docs] “Open source Python framework for building voice and multimodal AI pipelines. Orchestrate 150+ AI services with ultra-low latency.”
   • [probe] “PROBE runtime (recorded 2026-09-05): pypi pipecat-ai 1.8.1 (BSD-2 OSS) installs and `import pipecat` succeeds with no key, printing its star…”
   • [github] “Build a single voice agent or a full multi-agent system where specialists hand off, fan out in parallel, and coordinate over a shared bus, l…”

   proof ↗⚑ flag

   Bolna~partialprobed5/10

   Bolna documents an official Web Call SDK (bolna-docs-18) under a 'developer-resources/sdks' path, plus a CLI and MCP server, giving AI-native builders some official tooling to build against, but there is no evidence of broader language SDKs (e.g., Python, Node, Go client libraries) beyond the browser-based Web Call SDK. missing for 10: multi-language server-side SDKs, independent/hands-on verification of SDK usability, breadth beyond the single web-call SDK.

   • [claimed-docs] “The Web Call SDK connects a browser tab directly to a Bolna voice agent for a live, two-way conversation.”
   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”
   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Pipecat—none0/10

   Webhooks appear only as an inbound mechanism (a telephony carrier calling Pipecat's webhook to signal an incoming call), not as an outbound event-subscription system that lets a user register a webhook to receive Pipecat's own events (e.g., call end, transcript ready, errors). No evidence of a webhook subscription API or configurable event notifications for consumers.

   • [claimed-docs] “Telephony bots have a different shape than WebRTC bots. The session doesn't start because a client sent your dispatcher an HTTP request — it…”
   • [claimed-docs] “the carrier (Twilio, Telnyx, Plivo, Exotel, or your SIP provider) is calling your webhook to tell you there's an inbound call”
   • [claimed-docs] “python bot.py -t twilio -x your-name.ngrok.io”

   proof ↗⚑ flag

   Bolna—none0/10

   No evidence in the pack mentions webhooks or event subscription for Bolna; the docs cover agents, calls, CLI, MCP, SIP, pricing, and security but nothing about outbound event notifications. Missing for 10: any webhook registration/config API, event payload documentation, or third-party confirmation of webhook delivery.

   ⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Bolna
   Pipecat—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bolna~partialclaimed5/10

   Bolna offers agent-level call_summary_enabled to auto-generate AI summaries and an extraction-categories API to pull structured insights out of call data, both of which are AI-generated insights derived from user data (calls). However, there's no evidence of broader cross-call analytics, trend insights, or proactive suggestions surfaced in a dashboard beyond per-call outputs. Missing for 10: aggregated/dashboard-level insights across multiple calls, proactive recommendation surfacing, and independent confirmation of quality of generated summaries/extractions.

   • [claimed-docs] “POST /agent/{agent_id}/extraction-categories — create a category (name + model) and attach it to an agent”
   • [claimed-docs] “Call summaries are an agent-level toggle: call_summary_enabled (boolean, off by default) on the agent create and update APIs”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Bolna
   Pipecat~partialclaimed4/10

   Pipecat supports multi-agent systems where 'specialists hand off, fan out in parallel, and coordinate over a shared bus, locally or distributed' and can 'hand off to subagents for long-running tools and complex tasks,' plus telephony bots that start autonomously when a carrier calls a webhook rather than a user request — suggesting some background/autonomous agent operation. But Pipecat's core model is a live, turn-based conversational pipeline tied to an active voice/video session, not a scheduler or cron-like background automation runner independent of a live interaction. Missing for 10: explicit scheduling/triggering mechanisms for unattended background jobs, evidence of agents running without any live session, and independent confirmation of autonomous multi-agent orchestration in production.

   • [github] “Build a single voice agent or a full multi-agent system where specialists hand off, fan out in parallel, and coordinate over a shared bus, l…”
   • [claimed-docs] “Hand off to subagents for long-running tools and complex tasks, and use Pipecat Flows when a conversation needs to follow a defined path.”
   • [claimed-docs] “Telephony bots have a different shape than WebRTC bots. The session doesn't start because a client sent your dispatcher an HTTP request — it…”
   • [claimed-docs] “the carrier (Twilio, Telnyx, Plivo, Exotel, or your SIP provider) is calling your webhook to tell you there's an inbound call”

   proof ↗⚑ flag

   Bolna~partialprobed6/10

   Bolna's workflows feature lets users build multi-step outreach sequences (voice calls, WhatsApp, API calls, waits, retries) driven entirely through the API, which supports background automation, and the CLI can manage batches of calls autonomously. However there's no documented evidence of scheduling/triggers, monitoring/alerting on autonomous runs, or a dashboard for managing long-running background jobs beyond the API-driven workflow primitives. missing for 10: scheduling/trigger mechanisms, autonomous-run monitoring/alerting, independent hands-on confirmation of unattended long-running workflows.

   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”
   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Pipecat—none0/10

   Pipecat's docs describe a framework/CLI for building voice AI agents, a context-hub that exposes Pipecat's own docs as an MCP server to external coding agents, and dev tooling (runner, evals, Flows) — but none of this is a built-in assistant inside Pipecat's own product surface that a user delegates tasks to. Missing for 10: any first-party 'chat with an assistant' feature in the CLI/dashboard/docs site, evidence of task delegation to an embedded assistant, or independent confirmation of such a feature.

   • [claimed-docs] “pipecat context-hub install` registers the hub as an MCP server with your coding agent and builds the local index”
   • [claimed-docs] “pipecat context-hub install registers the hub as an MCP server with your coding agent and builds the local index”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Pipecat CLI (pypi pipecat-ai[cli]) ran keylessly via uvx — `pipecat --help` lists init (pr…”

   proof ↗⚑ flag

   Bolna—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Bolna
   Pipecat~partialprobed6/10

   Pipecat's entire raison d'être is building voice agents that end users control via natural spoken language — turn detection, interruption/barge-in, and Flows functions that progress conversations based on NL input (pipecat-docs-9, pipecat-docs-19, pipecat-docs-6/22/30) all support NL-driven operation of the *bots* it produces. However, the story is ambiguous about whether it's the bots or the Pipecat tooling itself; Pipecat's own developer-facing surfaces (CLI init/cloud/eval/context-hub) are traditional structured commands, not natural-language commands (pipecat-probe-rt-1, pipecat-docs-34/37). Missing for 10: evidence that the Pipecat framework/CLI itself (not just end-user bots) can be operated by an AI-native user via natural-language instructions rather than code/CLI syntax.

   • [claimed-docs] “Smart Turn Detection uses an advanced machine learning model to determine when a user has finished speaking and your bot should respond.”
   • [claimed-docs] “Interruptions (also called barge-in) let the user talk over the bot. When the user starts speaking while the bot is talking, the bot stops i…”
   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: 1. Process data ... 2. Progress the conversation by transitioning between nodes”
   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: Process data by interfacing with external systems and APIs...Progress the conversation by…”
   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: 1. Process data by interfacing with external systems and APIs... 2. Progress the conversa…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Pipecat CLI (pypi pipecat-ai[cli]) ran keylessly via uvx — `pipecat --help` lists init (pr…”
   • [claimed-docs] “pipecat init quickstart # Change to the project directory cd pipecat-quickstart”

   proof ↗⚑ flag

   Bolna✓fullprobed7/10

   Bolna ships an official MCP server that lets AI-native tools like Claude, Cursor, or Windsurf connect to a Bolna account and operate it (manage agents, calls, etc.) via natural-language commands, confirmed both in docs and via a live probe. Missing for 10: independent/hands-on verification that the MCP integration works as described, and no additional natural-language control surfaces (e.g., chat-based dashboard) beyond MCP.

   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [probe] “official MCP server documented at https://www.bolna.ai/docs/build-with-ai/mcp”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Pipecat—none0/10

   Pipecat's docs are static markdown pages (get-started, fundamentals, flows, CLI reference) with no evidence of an interactive API reference or runnable code examples; a direct probe for OpenAPI/Swagger endpoints returned 404 on all candidate paths, indicating no interactive API explorer exists.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.pipecat.ai/openapi.json, https://docs.pipecat.ai/swagger.json, https://docs.pipecat.ai/…”
   • [probe] “official CLI documented at https://docs.pipecat.ai/api-reference/cli/overview”

   proof ↗⚑ flag

   Bolna—none0/10

   Bolna has an API reference doc listing basics like API key creation, but there is no evidence of an interactive reference with runnable/try-it examples, and a probe for a machine-readable OpenAPI spec (which typically powers such interactive docs) returned 404 on all checked paths.

   • [claimed-docs] “Click the Create a new API Key button to generate your unique authentication credentials.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.bolna.ai/openapi.json, https://docs.bolna.ai/swagger.json, https://docs.bolna.ai/api/op…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Pipecat—none0/10

   A direct probe for OpenAPI/swagger specs at all standard locations (openapi.json, swagger.json, etc.) on docs.pipecat.ai returned 404s, and no evidence pack item shows a downloadable machine-readable API spec despite Pipecat having an api-reference docs section and cloud service.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.pipecat.ai/openapi.json, https://docs.pipecat.ai/swagger.json, https://docs.pipecat.ai/…”

   proof ↗⚑ flag

   Bolna—none0/10

   A direct probe for OpenAPI/Swagger spec files at all standard locations returned 404s, and no evidence pack item shows a downloadable machine-readable API spec despite having an API reference page.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.bolna.ai/openapi.json, https://docs.bolna.ai/swagger.json, https://docs.bolna.ai/api/op…”
   • [claimed-docs] “Click the Create a new API Key button to generate your unique authentication credentials.”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Pipecat
   Pipecat~partialclaimed5/10

   Pipecat provides a local development runner (`pipecat.runner.run`) and CLI scaffolding that let developers run and iterate on bots entirely locally, plus a built-in Evals system that runs described conversations against 'your real agent' pipeline for behavior testing — both usable without deploying to Pipecat Cloud or touching a production instance. However, there's no explicit 'sandbox environment' concept with data isolation from production (e.g. no staging vs prod data separation, no test-data seeding, no mention of production data at all since Pipecat doesn't store conversational data centrally). Missing for 10: explicit sandbox/production data isolation, documented data classification for dev vs prod, hands-on confirmation that Evals or local runner never touch live production resources.

   • [claimed-docs] “Pipecat ships a built-in development runner (\`pipecat.runner.run\`) that handles the server-side glue most bots need during development”
   • [claimed-docs] “Pipecat ships a built-in development runner (pipecat.runner.run) that handles the server-side glue most bots need during development: creati…”
   • [claimed-docs] “Pipecat ships a built-in development runner (`pipecat.runner.run`) that handles the server-side glue most bots need during development: crea…”
   • [claimed-docs] “Pipecat Evals is the framework's built-in system for testing agent behavior. You describe a conversation and the behavior you expect, and Pi…”
   • [claimed-docs] “You describe a conversation and the behavior you expect, and Pipecat runs it against your real agent (the same pipeline, the same services, …”
   • [claimed-docs] “This is the property that makes the same bot file portable across the development runner, Pipecat Cloud, and most production self-hosting se…”

   proof ↗⚑ flag

   Bolna—none0/10

   No evidence pack item mentions a sandbox environment, test mode, staging account, or separation from production data for Bolna; the closest concepts (self-hosting, BYOK, data residency) are about deployment/privacy, not a distinct sandbox/test mode. missing for 10: any mention of a sandbox/test environment, test API keys, or safe testing workflow that avoids production data.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Pipecat—none0/10

   No evidence pack item discusses API versioning scheme, version numbers surfaced in docs, or any documented deprecation policy/timeline for Pipecat's SDKs or APIs; the only version datum (pip package 1.8.1) shows a version exists but nothing about a deprecation policy is documented.

   ⚑ flag

   Bolna—none0/10

   There is a changelog page referenced and an API reference, but no evidence of API versioning scheme or a documented deprecation policy anywhere in the pack; OpenAPI spec probes even returned 404s. Missing for 10: versioned API endpoints/headers, explicit deprecation policy documentation, migration/versioning changelog entries.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.bolna.ai/openapi.json, https://docs.bolna.ai/swagger.json, https://docs.bolna.ai/api/op…”
   • [claimed-docs] “Click the Create a new API Key button to generate your unique authentication credentials.”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Bolna
   Pipecat~partialclaimed3/10

   Pipecat supports 'unlimited concurrency' for running many simultaneous voice sessions and multi-agent fan-out ('fan out in parallel... coordinate over a shared bus'), which could support bulk-style parallel processing of many calls/agents at once. However, there is no explicit bulk-operation tooling (e.g., batch APIs, bulk data import/export, mass-edit of items) documented anywhere in the evidence pack. Missing for 10: explicit bulk/batch operation APIs or workflows, evidence of processing many discrete 'items' (not just concurrent voice sessions) in one operation, and any hands-on confirmation of this at scale.

   • [claimed-docs] “Pipecat Cloud supports unlimited concurrency.”
   • [github] “Build a single voice agent or a full multi-agent system where specialists hand off, fan out in parallel, and coordinate over a shared bus, l…”

   proof ↗⚑ flag

   Bolna~partialclaimed5/10

   The CLI explicitly manages 'batches' of calls alongside agents and phone numbers (bolna-docs-16), and the platform claims to power 'thousands of inbound and outbound calls every minute' (bolna-docs-22), implying built-in bulk calling capability. However, there is no documentation of a specific bulk API endpoint, CSV/list upload, or bulk agent/category management workflow. Missing for 10: explicit bulk-operation API docs (e.g., batch call creation, bulk agent updates), a documented interface for uploading many items at once, and independent confirmation of bulk throughput.

   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [claimed-docs] “Power thousands of inbound and outbound calls every minute with human-like, multilingual intelligence”
   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Pipecat
   Pipecat~partialclaimed6/10

   Pipecat's frame-based pipeline is inherently event-driven — interruption events automatically halt bot output when the user speaks, and Pipecat Flows functions can process data and automatically transition conversation nodes based on function-call events. This gives a real automation layer, but it's scoped to conversation/pipeline events rather than a general-purpose rules engine for arbitrary triggers/actions. Missing for 10: a documented generic rule-definition system (arbitrary trigger→action bindings outside conversation flow), and independent/hands-on evidence of custom event-rule automation beyond the built-in interruption/Flows mechanics.

   • [claimed-docs] “When the user starts speaking while the bot is talking, the bot stops immediately, in-flight work is cancelled, and the pipeline is ready fo…”
   • [claimed-docs] “Interruptions (also called barge-in) let the user talk over the bot. When the user starts speaking while the bot is talking, the bot stops i…”
   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: 1. Process data ... 2. Progress the conversation by transitioning between nodes”
   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: Process data by interfacing with external systems and APIs...Progress the conversation by…”
   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: 1. Process data by interfacing with external systems and APIs... 2. Progress the conversa…”
   • [claimed-docs] “Pipecat's turn events make it easy to collect both user and assistant messages as they occur.”

   proof ↗⚑ flag

   Bolna~partialclaimed4/10

   Bolna's workflow feature lets users chain voice calls, WhatsApp messages, API calls, waits and retries via the API, which is a form of automation, but the docs never describe defining conditional 'if event X happens then do Y' rules or an event/trigger system — it's presented as sequential outreach flows rather than rule-based event triggers. Missing for 10: explicit event-trigger/rule definition syntax, conditional branching logic, and any webhook-or-event-driven automation examples beyond the sequential workflow description.

   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Pipecat—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bolna—none0/10

   Bolna's workflow docs describe multi-step outreach sequences with waits and retries (bolna-docs-12), but there is no evidence of a scheduler for recurring/cron-based jobs or workflows that re-trigger automatically over time. missing for 10: recurring/scheduled trigger mechanism, cron-like job definitions, evidence of periodic re-execution.

   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Pipecat—none0/10

   Pipecat's docs describe building pipelines/Flows in Python code but no evidence of built-in versioning, review workflows, or rollback capabilities for automations (Flows or pipelines) — no changelog, diff, or rollback tooling is mentioned anywhere in the evidence pack.

   ⚑ flag

   Bolna—none0/10

   Bolna is a voice AI agent platform (agent creation, calls, workflows, telephony) but the evidence pack shows no version control, review workflow, or rollback mechanism for automations/agents — no mention of agent versioning, change history, approval flows, or revert capability.

   ⚑ flag

Compliance

1. founderMeet call-recording consent and disclosure obligations with per-call recording controls and configurable data retention

   weight 2 · round to Pipecat
   Pipecat~partialclaimed3/10

   Pipecat provides an AudioBufferProcessor that developers can use to capture call recordings, which is a building block a founder could use to implement recording, but there's no documented feature for per-call consent/disclosure toggles or configurable data-retention policies — those would have to be built entirely by the developer. missing for 10: consent/disclosure mechanisms, retention-policy configuration, compliance-specific controls, any documentation tying recording to legal/consent obligations.

   • [claimed-docs] “Pipecat's \`AudioBufferProcessor\` makes it easy to capture high-quality audio recordings of both the user and bot during interactions.”
   • [claimed-docs] “Pipecat's AudioBufferProcessor makes it easy to capture high-quality audio recordings of both the user and bot during interactions.”
   • [claimed-docs] “Pipecat's `AudioBufferProcessor` makes it easy to capture high-quality audio recordings of both the user and bot during interactions.”

   proof ↗⚑ flag

   Bolna—none0/10

   The evidence pack shows security/data-residency features and call-summary toggles, but nothing about call-recording consent, per-call recording enable/disable controls, disclosure/announcement features, or configurable retention periods for recordings/transcripts. No mention of recording consent mechanisms or retention settings anywhere in the docs pack.

   ⚑ flag

2. platform-engineerRun regulated workloads with HIPAA/BAA support, SOC 2, and data-residency options

   weight 2 · round to Bolna
   Pipecat—none0/10

   No evidence in the pack mentions HIPAA/BAA, SOC 2 certification, or data-residency options for Pipecat or Pipecat Cloud; the pack covers pipeline features, telephony, CLI, and dev tooling but nothing on compliance/regulatory posture. missing for 10: HIPAA/BAA documentation, SOC 2 attestation, data-residency configuration options.

   ⚑ flag

   Bolna~partialclaimed3/10

   Bolna documents Indian data residency and self-hosting via Docker/Kubernetes for private enterprise deployments, but there is no mention of HIPAA/BAA support or SOC 2 certification anywhere in the evidence pack. missing for 10: HIPAA/BAA attestation, SOC 2 report or certification, broader multi-region data-residency options beyond India.

   • [claimed-docs] “Indian data residency is available for deployments where data must remain in India.”
   • [claimed-docs] “Learn how to self-host Bolna Voice AI on your own servers using Docker or Kubernetes for secure, private, and scalable enterprise deployment…”

   proof ↗⚑ flag

Scale

1. platform-engineerSee documented concurrency limits and scale to many simultaneous calls without manual capacity begging

   weight 2 · round to Pipecat
   Pipecat~partialcommunity4/10

   Pipecat Cloud's pricing page asserts 'unlimited concurrency' and offers multiple agent profiles for compute needs, giving a vendor-level answer to scaling, but there is no documented capacity planning guide, per-instance concurrency limits, or benchmarks for self-hosted deployments. Community commentary (a developer porting Pipecat to avoid Python's GIL for 'real concurrency') suggests self-hosted scaling is not frictionless and may require manual work to reach high concurrency. Missing for 10: documented concurrency ceilings/benchmarks for self-hosted deployments, load-testing data, and detail behind the 'unlimited concurrency' claim beyond a pricing-page bullet.

   • [claimed-docs] “Pipecat Cloud supports unlimited concurrency.”
   • [claimed-docs] “Pipecat Cloud offers different agent profiles, to best support your use case and compute needs.”
   • [community] “I got tired of running Python servers for voice agents, so I started porting Pipecat over. The design is Pipecat's, frames and processors an…”

   proof ↗⚑ flag

   Bolna~partialclaimed3/10

   Bolna's marketing page claims it can 'power thousands of inbound and outbound calls every minute' and docs mention self-hosting via Docker/Kubernetes for 'scalable enterprise deployments,' but there are no documented concurrency limits, rate-limit tables, or self-serve capacity-scaling mechanisms (e.g., no API rate-limit docs, no autoscaling guide, no numeric SLA). missing for 10: documented numeric concurrency/rate limits, self-serve scale-up process, autoscaling architecture details, independent verification of claimed call volume.

   • [claimed-docs] “Power thousands of inbound and outbound calls every minute with human-like, multilingual intelligence”
   • [claimed-docs] “Learn how to self-host Bolna Voice AI on your own servers using Docker or Kubernetes for secure, private, and scalable enterprise deployment…”

   proof ↗⚑ flag

Self host

1. platform-engineerSelf-host the voice agent runtime from open-source code on my own infrastructure

   weight 3 · round to Pipecat
   Pipecat✓fullprobed9/10

   Pipecat is confirmed as a pip-installable, BSD-2 open-source Python framework that runs keylessly with no vendor lock-in, ships a development runner and CLI, and docs explicitly state bot files are portable across the dev runner, Pipecat Cloud, and 'most production self-hosting setups.' Runtime probes confirm the package installs and imports successfully outside any managed cloud, and community evidence corroborates real-world self-hosted usage (local inference via Ollama/Whisper, custom ports of the framework). Missing for 10: a first-party detailed production self-hosting deployment guide (e.g., Docker/Kubernetes reference architecture) beyond the telephony/local-runner docs.

   • [probe] “PROBE runtime (recorded 2026-09-05): pypi pipecat-ai 1.8.1 (BSD-2 OSS) installs and `import pipecat` succeeds with no key, printing its star…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Pipecat CLI (pypi pipecat-ai[cli]) ran keylessly via uvx — `pipecat --help` lists init (pr…”
   • [claimed-docs] “This is the property that makes the same bot file portable across the development runner, Pipecat Cloud, and most production self-hosting se…”
   • [claimed-docs] “Open source Python framework for building voice and multimodal AI pipelines. Orchestrate 150+ AI services with ultra-low latency.”
   • [community] “Local inference is already supported via Pipecat, you can use ollama or any custom OpenAI endpoint. Local STT is also supported via whisper,…”
   • [community] “Yes, Pipecat already supports that natively, so this can be done easily with ollama... Also, check out any provider they support, and it can…”
   • [github] “Build a single voice agent or a full multi-agent system where specialists hand off, fan out in parallel, and coordinate over a shared bus, l…”

   proof ↗⚑ flag

   Bolna✓fullclaimed8/10

   Bolna is explicitly an open-source framework on GitHub, and docs include dedicated enterprise instructions for self-hosting on Docker or Kubernetes for private/enterprise deployments. Missing for 10: independent hands-on reports confirming successful self-host deployment and more detail on infrastructure requirements/limitations of the self-hosted version vs SaaS.

   • [github] “Bolna is the end-to-end open source production ready framework for quickly building LLM based voice driven conversational applications.”
   • [claimed-docs] “Learn how to self-host Bolna Voice AI on your own servers using Docker or Kubernetes for secure, private, and scalable enterprise deployment…”

   proof ↗⚑ flag

Latency

1. platform-engineerSee documented end-to-end voice latency numbers or tuning guidance backing the platform's speed claims

   weight 3 · round to Pipecat
   Pipecat~partialclaimed6/10

   Pipecat documents a dedicated STT-latency-tuning guide describing measured P99 latency values per service and a TTFS (Time To Final Segment) metric, plus a built-in metrics system for enabling latency instrumentation — real tuning guidance exists. However, this is scoped to STT stage latency rather than a comprehensive end-to-end voice round-trip latency benchmark, and no actual published numbers/tables or independent corroboration of the claimed P99 figures are shown. Missing for 10: published end-to-end latency benchmark numbers (not just STT), tuning guidance across the full voice pipeline (TTS/LLM/turn-taking), and independent verification of the claimed latency figures.

   • [claimed-docs] “Pipecat ships with measured P99 latency values for each supported service so that turn detection can account for this delay automatically.”
   • [claimed-docs] “Time To Final Segment (TTFS) measures how long it takes from the moment a user stops speaking until the STT service delivers the final trans…”
   • [claimed-docs] “Pipecat offers built-in metrics for both, which can be enabled with straightforward configuration options.”

   proof ↗⚑ flag

   Bolna—none0/10

   No evidence pack item provides documented latency numbers, benchmarks, or tuning guidance for end-to-end voice latency; only vague marketing claims like 'build in under 5 minutes' or 'power thousands of calls' appear, with no actual latency figures or turn-taking tuning documentation.

   • [claimed-docs] “Build and deploy in under 5 minutes”
   • [claimed-docs] “Power thousands of inbound and outbound calls every minute with human-like, multilingual intelligence”

   proof ↗⚑ flag

Turn taking

1. developerRely on the agent to handle interruptions (barge-in) gracefully — stopping speech, updating context, and recovering the turn

   weight 3 · round to Pipecat
   Pipecat✓fullclaimed8/10

   Pipecat has explicit, dedicated documentation on interruptions/barge-in describing immediate speech stop, cancellation of in-flight work, and pipeline readiness for new input, plus Smart Turn Detection for natural turn-taking and Krisp-based false-interruption suppression in Pipecat Cloud. Missing for 10: independent hands-on validation of graceful context/turn recovery specifically (community evidence is about debugging/latency tooling, not barge-in correctness) and no explicit documentation of how conversation context is updated/rolled back after an interruption.

   • [claimed-docs] “When the user starts speaking while the bot is talking, the bot stops immediately, in-flight work is cancelled, and the pipeline is ready fo…”
   • [claimed-docs] “Interruptions (also called barge-in) let the user talk over the bot. When the user starts speaking while the bot is talking, the bot stops i…”
   • [claimed-docs] “Smart Turn Detection uses an advanced machine learning model to determine when a user has finished speaking and your bot should respond.”
   • [claimed-docs] “Smart Turn Detection recognizes natural conversational cues like intonation patterns and linguistic signals for more natural conversations.”
   • [claimed-docs] “Eliminates background noise and voices that cause false interruptions, powered by Krisp.”

   proof ↗⚑ flag

   Bolna—none0/10

   No evidence pack item mentions barge-in, interruption handling, speech-stop, or turn recovery mechanics; the docs cover extraction categories, summaries, providers, CLI, MCP, pricing, etc., but nothing about turn-taking or interruption behavior. missing for 10: any documentation of barge-in/interruption detection, mid-speech stop mechanics, context update on interruption, turn recovery logic.

   ⚑ flag

2. developerEnable noise suppression or audio filtering so the agent stays coherent on noisy real-world calls

   weight 1 · round to Pipecat
   Pipecat✓fullclaimed8/10

   Pipecat Cloud explicitly ships Krisp-powered noise/background-voice suppression to eliminate false interruptions, and the framework's Smart Turn Detection complements this by recognizing genuine speech cues, keeping the agent coherent on noisy calls. Missing for 10: no first-party docs on self-hosted (non-cloud) noise suppression configuration, and no independent hands-on validation of suppression quality in real noisy environments.

   • [claimed-docs] “Eliminates background noise and voices that cause false interruptions, powered by Krisp.”
   • [claimed-docs] “Smart Turn Detection uses an advanced machine learning model to determine when a user has finished speaking and your bot should respond.”
   • [claimed-docs] “Smart Turn Detection recognizes natural conversational cues like intonation patterns and linguistic signals for more natural conversations.”

   proof ↗⚑ flag

   Bolna—none0/10

   No evidence pack item mentions noise suppression, background noise handling, or audio filtering settings for calls; the docs cover extraction categories, summaries, telephony, SDKs, and pricing but not audio quality/noise robustness features. Missing for 10: any mention of noise suppression/audio filtering configuration, VAD tuning for noisy environments, or documented handling of real-world call noise.

   ⚑ flag

3. developerUse model-based end-of-turn detection beyond simple VAD silence timeouts so the agent doesn't talk over slow speakers

   weight 2 · round to Pipecat
   Pipecat✓fullclaimed8/10

   Pipecat documents 'Smart Turn Detection' as an ML model that determines end-of-turn based on intonation and linguistic cues, going beyond simple VAD silence timeouts, directly matching the story (pipecat-docs-9, pipecat-docs-31). Additional STT latency-tuning docs show the framework accounts for provider-specific delays to avoid premature cutoffs (pipecat-docs-15, pipecat-docs-20). Missing for 10: independent/hands-on evidence validating the model's accuracy on slow speakers in production, and no third-party benchmark of false-interruption reduction.

   • [claimed-docs] “Smart Turn Detection uses an advanced machine learning model to determine when a user has finished speaking and your bot should respond.”
   • [claimed-docs] “Smart Turn Detection recognizes natural conversational cues like intonation patterns and linguistic signals for more natural conversations.”
   • [claimed-docs] “Pipecat ships with measured P99 latency values for each supported service so that turn detection can account for this delay automatically.”
   • [claimed-docs] “Time To Final Segment (TTFS) measures how long it takes from the moment a user stops speaking until the STT service delivers the final trans…”

   proof ↗⚑ flag

   Bolna—none0/10

   No evidence describes model-based end-of-turn/turn-taking detection distinct from VAD silence timeouts; evidence only covers mid-call model switching, extraction categories, and unrelated features. Missing for 10: any mention of endpointing model, semantic turn detection, or configurable end-of-turn logic beyond silence thresholds.

   ⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Bolna
   Pipecat~partialprobed4/10

   Pipecat is fundamentally code-first: the CLI covers init/scaffolding, cloud deploy, evals, and context-hub (pipecat-probe-rt-1, pipecat-docs-16/34/37), and the framework itself is the primary interface. But evidence never explicitly confirms that Pipecat Cloud's web dashboard (agent profiles, concurrency settings, monitoring) exposes no exclusive UI-only functionality, nor does it document a full REST/OpenAPI surface (probe shows no discoverable OpenAPI spec, pipecat-probe-2) for programmatic parity with any cloud console. Missing for 10: explicit UI/API parity statement, documented OpenAPI/REST API for Pipecat Cloud console features, and confirmation no dashboard-only settings exist.

   • [probe] “PROBE runtime (recorded 2026-09-05): the official Pipecat CLI (pypi pipecat-ai[cli]) ran keylessly via uvx — `pipecat --help` lists init (pr…”
   • [claimed-docs] “Install the Pipecat CLI and scaffold the quickstart project (also writes AGENTS.md + CLAUDE.md)”
   • [claimed-docs] “pipecat init quickstart # Change to the project directory cd pipecat-quickstart”
   • [claimed-docs] “Pipecat Cloud offers different agent profiles, to best support your use case and compute needs.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.pipecat.ai/openapi.json, https://docs.pipecat.ai/swagger.json, https://docs.pipecat.ai/…”
   • [claimed-docs] “Pipecat ships a built-in development runner (pipecat.runner.run) that handles the server-side glue most bots need during development: creati…”

   proof ↗⚑ flag

   Bolna~partialprobed7/10

   Docs show the platform is API-first — agent creation, extraction categories, call summaries, workflows, and telephony are all described as configurable via the API, and a CLI and MCP server both wrap that same API, implying broad parity. However, there is no explicit documentation stating full UI/API feature parity, and probes found no discoverable OpenAPI/swagger spec (404s), leaving some doubt about completeness of coverage for every UI action. Missing for 10: explicit UI-API parity statement, published OpenAPI/swagger spec, independent confirmation that all UI actions have API equivalents.

   • [claimed-docs] “POST /agent/{agent_id}/extraction-categories — create a category (name + model) and attach it to an agent”
   • [claimed-docs] “Call summaries are an agent-level toggle: call_summary_enabled (boolean, off by default) on the agent create and update APIs”
   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”
   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.bolna.ai/openapi.json, https://docs.bolna.ai/swagger.json, https://docs.bolna.ai/api/op…”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Pipecat
   Pipecat~partialprobed5/10

   Pipecat is open-source (BSD-2) and self-hostable, meaning users inherently retain full control of their data (audio, transcripts, logs) rather than it being locked in a vendor's system — recordings via AudioBufferProcessor and transcripts via turn events are captured directly in the developer's own infrastructure. However, there's no explicit documentation of an 'export' feature, standardized open data formats, or migration tooling for leaving a hosted deployment (e.g., Pipecat Cloud). missing for 10: explicit data-export/format documentation, Pipecat Cloud data portability/exit guarantees, independent confirmation of format openness.

   • [claimed-docs] “Pipecat's \`AudioBufferProcessor\` makes it easy to capture high-quality audio recordings of both the user and bot during interactions.”
   • [claimed-docs] “Pipecat's turn events make it easy to collect both user and assistant messages as they occur.”
   • [probe] “PROBE runtime (recorded 2026-09-05): pypi pipecat-ai 1.8.1 (BSD-2 OSS) installs and `import pipecat` succeeds with no key, printing its star…”
   • [claimed-docs] “Open source Python framework for building voice and multimodal AI pipelines. Orchestrate 150+ AI services with ultra-low latency.”

   proof ↗⚑ flag

   Bolna~partialclaimed3/10

   Bolna's API lets you fetch call transcripts (bolna-docs-14) and the platform can be self-hosted via Docker/Kubernetes (bolna-docs-9), with an open-source core framework (bolna-gh-1), which together provide some data portability, but there is no documented bulk 'export all data' feature or guarantee of open, standard export formats covering call recordings, agent configs, analytics, etc. Missing for 10: an explicit full-data export tool/endpoint, documented open format specification for exported data, and independent confirmation that a user can fully migrate away with all their data.

   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”
   • [claimed-docs] “Learn how to self-host Bolna Voice AI on your own servers using Docker or Kubernetes for secure, private, and scalable enterprise deployment…”
   • [github] “Bolna is the end-to-end open source production ready framework for quickly building LLM based voice driven conversational applications.”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Pipecat
   Pipecat✓fullprobed9/10

   Pipecat is explicitly documented as an 'Open source Python framework' with a public GitHub repo, and a runtime probe confirms the pip package is BSD-2 licensed and installable/importable without any key, confirming genuine open-source source access. Missing for 10: no explicit citation of a LICENSE file or license text itself, only the probe's characterization.

   • [claimed-docs] “Open source Python framework for building voice and multimodal AI pipelines. Orchestrate 150+ AI services with ultra-low latency.”
   • [github] “Build a single voice agent or a full multi-agent system where specialists hand off, fan out in parallel, and coordinate over a shared bus, l…”
   • [probe] “PROBE runtime (recorded 2026-09-05): pypi pipecat-ai 1.8.1 (BSD-2 OSS) installs and `import pipecat` succeeds with no key, printing its star…”

   proof ↗⚑ flag

   Bolna~partialclaimed5/10

   The GitHub repo description explicitly calls Bolna 'the end-to-end open source production ready framework,' supporting that its source is publicly available under an open-license framing, but no specific license (e.g., MIT/Apache) is named or verified, and no independent corroboration exists. Missing for 10: explicit license identification (e.g., LICENSE file contents), confirmation the entire product (not just the framework) is open-sourced, and independent verification.

   • [github] “Bolna is the end-to-end open source production ready framework for quickly building LLM based voice driven conversational applications.”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Pipecat✓fullprobed8/10

   Pipecat is an open-source Python framework (BSD-2 licensed), pip-installable and runnable with no key/cloud dependency, with a documented dev runner and explicit note that the same bot file is portable to self-hosting setups; local inference (Ollama, Whisper) further confirms self-hosting without vendor lock-in. missing for 10: no dedicated self-hosting/production deployment guide (e.g., Docker/Kubernetes reference architecture) or independent case study of a large-scale self-hosted deployment.

   • [probe] “PROBE runtime (recorded 2026-09-05): pypi pipecat-ai 1.8.1 (BSD-2 OSS) installs and `import pipecat` succeeds with no key, printing its star…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Pipecat CLI (pypi pipecat-ai[cli]) ran keylessly via uvx — `pipecat --help` lists init (pr…”
   • [claimed-docs] “This is the property that makes the same bot file portable across the development runner, Pipecat Cloud, and most production self-hosting se…”
   • [community] “Local inference is already supported via Pipecat, you can use ollama or any custom OpenAI endpoint. Local STT is also supported via whisper,…”
   • [community] “Yes, Pipecat already supports that natively, so this can be done easily with ollama... Also, check out any provider they support, and it can…”

   proof ↗⚑ flag

   Bolna✓fullclaimed8/10

   Bolna is explicitly open source (GitHub repo) and documentation provides dedicated on-premise instructions for self-hosting via Docker or Kubernetes for enterprise deployments, directly satisfying the self-host story. Missing for 10: independent/hands-on confirmation of a successful self-hosted deployment and more detail on feature parity between self-hosted and cloud versions.

   • [github] “Bolna is the end-to-end open source production ready framework for quickly building LLM based voice driven conversational applications.”
   • [claimed-docs] “Learn how to self-host Bolna Voice AI on your own servers using Docker or Kubernetes for secure, private, and scalable enterprise deployment…”

   proof ↗⚑ flag

Pricing

1. founderSee published per-minute or usage pricing and estimate cost per call before committing

   weight 2 · round to Bolna
   Pipecat—none0/10

   The evidence pack references a Pipecat Cloud pricing page (concurrency, agent profiles) but never shows actual per-minute/usage rates, a pricing table, or a cost calculator that would let a founder estimate cost per call; the core open-source framework itself is free/self-hosted with no billing model at all.

   • [claimed-docs] “Pipecat Cloud supports unlimited concurrency.”
   • [claimed-docs] “Pipecat Cloud offers different agent profiles, to best support your use case and compute needs.”

   proof ↗⚑ flag

   Bolna~partialclaimed4/10

   There is a dedicated call-pricing doc page and mentions that BYOK/connected providers aren't charged (bolna-docs-19, bolna-docs-10), indicating some usage-based pricing structure exists, but no evidence pack item actually quotes a per-minute rate, tiered pricing table, or a cost calculator a founder could use to estimate cost per call. Missing for 10: explicit per-minute/usage rate figures, a pricing calculator or worked cost example, and independent confirmation that published rates are accurate.

   • [claimed-docs] “When you bring your own keys (BYOK), Bolna does not charge for those components.”
   • [claimed-docs] “We don't charge for any usage for providers that you have connected to Bolna.”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Bolna
   Pipecat~partialprobed3/10

   Pipecat is an open-source, self-hostable framework (pip-installable, runs locally or on your own infrastructure), which implicitly lets an operator choose where data/compute resides by choosing their own deployment location; however there is no explicit documentation of region/residency selection controls, especially for the hosted Pipecat Cloud offering. Missing for 10: explicit region-selection UI/API for Pipecat Cloud, data-residency compliance documentation (GDPR/SOC2 region guarantees), and confirmation that self-hosting is the only path to residency control.

   • [probe] “PROBE runtime (recorded 2026-09-05): pypi pipecat-ai 1.8.1 (BSD-2 OSS) installs and `import pipecat` succeeds with no key, printing its star…”
   • [claimed-docs] “Pipecat ships a built-in development runner (pipecat.runner.run) that handles the server-side glue most bots need during development: creati…”
   • [claimed-docs] “This is the property that makes the same bot file portable across the development runner, Pipecat Cloud, and most production self-hosting se…”
   • [claimed-docs] “Pipecat Cloud offers different agent profiles, to best support your use case and compute needs.”

   proof ↗⚑ flag

   Bolna~partialclaimed6/10

   Docs explicitly mention Indian data residency as an available option, and self-hosting via Docker/Kubernetes lets enterprises control where data lives entirely. However, there's no broader multi-region selection (e.g., EU, US) documented beyond India, and no detail on how residency is configured or enforced. Missing for 10: documented multi-region choice beyond India, configuration/UI for selecting region, and independent confirmation of residency enforcement.

   • [claimed-docs] “Indian data residency is available for deployments where data must remain in India.”
   • [claimed-docs] “Learn how to self-host Bolna Voice AI on your own servers using Docker or Kubernetes for secure, private, and scalable enterprise deployment…”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Pipecat—none0/10

   The evidence pack contains no mention of data-training opt-outs, data-usage policies, or privacy commitments regarding customer data and AI model training for either the open-source Pipecat framework or the hosted Pipecat Cloud service. Since Pipecat Cloud is a real hosted product where such a policy could plausibly exist, this axis applies, but no evidence supports it. Missing for 10: any privacy policy, ToS clause, or documentation stating customer data is not used to train models, and no independent corroboration.

   ⚑ flag

   Bolna—none0/10

   No evidence pack item addresses a training-data opt-out or policy on AI model training use; security docs cover data residency and IP whitelisting only, not training-data usage controls. missing for 10: any explicit statement on AI training data usage/opt-out policy, data processing agreement terms, or contractual guarantee against training use.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Pipecat—none0/10

   Pipecat is a self-hostable open-source framework and also offers a hosted Pipecat Cloud option that processes voice/audio data, so data-retention/deletion controls are a fair question for this product category, but the evidence pack contains no documentation of retention policies, deletion APIs, or data lifecycle controls — only unrelated features like recording/transcription and metrics.

   ⚑ flag

   Bolna—none0/10

   No evidence of data retention controls, deletion APIs, or user-facing privacy/data-lifecycle settings; only tangential mentions of security (IP whitelisting, India data residency) which do not address retention/deletion. Self-hosting option exists but that's deployment control, not a retention/deletion feature.

   • [claimed-docs] “Indian data residency is available for deployments where data must remain in India.”
   • [claimed-docs] “Whitelist all three IPs on your server or firewall”
   • [claimed-docs] “Learn how to self-host Bolna Voice AI on your own servers using Docker or Kubernetes for secure, private, and scalable enterprise deployment…”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Pipecat—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Bolna—none0/10

   No evidence pack item addresses telemetry, analytics opt-out, or usage-tracking controls for the platform itself; existing security/data-residency docs don't cover this. Missing for 10: any documentation of telemetry collection or an opt-out/disable mechanism, privacy policy statement on usage tracking, self-host confirmation of no phone-home behavior.

   ⚑ flag

Call control

1. developerEscalate a live call to a human with warm or blind transfer, passing context along

   weight 2 · round drawn
   Pipecat—none0/10

   The evidence pack covers Pipecat's telephony deployment (webhook/carrier integration for Twilio, Telnyx, etc.), conversation flow transitions via Pipecat Flows, and subagent hand-off for tasks, but nothing addresses call transfer to a human agent (warm or blind) or passing call context/metadata during such a transfer. This is a reasonable telephony axis for a voice AI framework, but no citation demonstrates or documents this capability.

   ⚑ flag

   Bolna—none0/10

   No evidence in the pack describes call transfer functionality (warm or blind) to a human agent, or context handoff during a live call; the closest items relate to model switching, summaries, and telephony/SIP trunking but not transfer escalation.

   ⚑ flag

2. developerMy agent can send DTMF keypresses, navigate IVR menus, and detect or leave voicemail

   weight 1 · round drawn
   Pipecat—none0/10

   Pipecat clearly supports telephony transports (Twilio, Telnyx, Plivo, Exotel, SIP) for building call-handling bots, so this axis applies, but the evidence pack contains no mention of DTMF keypress sending, IVR menu navigation, or voicemail detection/leaving capabilities anywhere in the docs or community sources.

   • [claimed-docs] “Telephony bots have a different shape than WebRTC bots. The session doesn't start because a client sent your dispatcher an HTTP request — it…”
   • [claimed-docs] “the carrier (Twilio, Telnyx, Plivo, Exotel, or your SIP provider) is calling your webhook to tell you there's an inbound call”
   • [claimed-docs] “Any Transport: WebRTC, SIP, PSTN”
   • [claimed-docs] “python bot.py -t twilio -x your-name.ngrok.io”

   proof ↗⚑ flag

   Bolna—none0/10

   No evidence in the pack mentions DTMF keypress sending, IVR menu navigation, or voicemail detection/leaving; only unrelated telephony features like SIP trunking, call summaries, and workflows are documented.

   ⚑ flag

Campaigns

1. founderRun batch outbound call campaigns with scheduling and throughput controls

   weight 2 · round to Bolna
   Pipecat—none0/10

   Pipecat's telephony docs cover per-call webhook-driven session handling (inbound/outbound single calls via Twilio/Telnyx/etc.) and unlimited concurrency on Pipecat Cloud, but there is no evidence of batch campaign management, call scheduling, pacing/throughput controls, or dialer-list orchestration for outbound campaigns — this is a fair ask for a telephony-capable voice AI framework but no such capability is documented.

   • [claimed-docs] “Telephony bots have a different shape than WebRTC bots. The session doesn't start because a client sent your dispatcher an HTTP request — it…”
   • [claimed-docs] “the carrier (Twilio, Telnyx, Plivo, Exotel, or your SIP provider) is calling your webhook to tell you there's an inbound call”
   • [claimed-docs] “python bot.py -t twilio -x your-name.ngrok.io”
   • [claimed-docs] “Pipecat Cloud supports unlimited concurrency.”
   • [claimed-docs] “Any Transport: WebRTC, SIP, PSTN”

   proof ↗⚑ flag

   Bolna~partialprobed5/10

   The CLI explicitly manages 'batches' of calls alongside agents/phone numbers, and marketing copy claims support for 'thousands of inbound and outbound calls every minute,' plus a workflows API for multi-step outreach with waits/retries — together implying batch campaign and throughput capability. However, there's no explicit documentation of scheduling controls (e.g., time windows, campaign start/stop) or throughput/rate-limiting configuration for outbound campaigns specifically. Missing for 10: explicit scheduling/calendar controls for campaigns, documented throughput/rate-limit configuration knobs, and any hands-on/independent evidence of batch campaign execution.

   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [claimed-docs] “Power thousands of inbound and outbound calls every minute with human-like, multilingual intelligence”
   • [claimed-docs] “Build multi-step outreach sequences that combine voice agent calls, WhatsApp messages, API calls, waits and retries, driven entirely through…”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”

   proof ↗⚑ flag

Numbers

1. developerProvision phone numbers and run both inbound and outbound calls through the platform's API

   weight 3 · round to Bolna
   Pipecat~partialclaimed4/10

   Docs show Pipecat integrates with telephony carriers (Twilio, Telnyx, Plivo, Exotel, SIP) to receive inbound call webhooks and run bots over PSTN/SIP transports, and CLI examples show running a bot against Twilio (`python bot.py -t twilio -x ...`), covering the 'run calls' half of the story. However, there is no evidence Pipecat itself exposes an API to provision/purchase phone numbers — that is left to the carrier's own console/API, not documented as a Pipecat capability. Missing for 10: native phone-number provisioning API/CLI, outbound call initiation API details, and any first-party number-management workflow.

   • [claimed-docs] “Telephony bots have a different shape than WebRTC bots. The session doesn't start because a client sent your dispatcher an HTTP request — it…”
   • [claimed-docs] “the carrier (Twilio, Telnyx, Plivo, Exotel, or your SIP provider) is calling your webhook to tell you there's an inbound call”
   • [claimed-docs] “Any Transport: WebRTC, SIP, PSTN”
   • [claimed-docs] “python bot.py -t twilio -x your-name.ngrok.io”

   proof ↗⚑ flag

   Bolna~partialprobed6/10

   Bolna's API/CLI clearly support placing outbound calls and receiving inbound calls (quickstart shows placing a call and fetching transcript via API, CLI manages calls and phone numbers, marketing claims thousands of inbound/outbound calls per minute), and BYOT lets you attach SIP trunks/numbers. However there's no explicit documented endpoint for provisioning/purchasing new phone numbers through the API itself — only CLI mention of managing 'phone numbers' and bringing your own trunk. Missing for 10: explicit phone-number provisioning API endpoint/documentation, independent confirmation of end-to-end inbound+outbound flow.

   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”
   • [claimed-docs] “The Bolna CLI (bolna) is a single Go binary that lets you manage agents, calls, phone numbers, and batches directly from your terminal”
   • [claimed-docs] “Bring Your Own Telephony (BYOT) lets you connect any standards-compliant SIP trunk to the Bolna platform.”
   • [claimed-docs] “Power thousands of inbound and outbound calls every minute with human-like, multilingual intelligence”
   • [probe] “official CLI documented at https://www.bolna.ai/docs/cli/introduction”

   proof ↗⚑ flag

Sip

1. platform-engineerConnect my own carrier or PBX via SIP trunking (or import Twilio/Telnyx numbers) instead of being locked to bundled telephony

   weight 2 · round to Bolna
   Pipecat✓fullclaimed7/10

   Docs explicitly describe telephony bots being invoked by carrier webhooks including 'Twilio, Telnyx, Plivo, Exotel, or your SIP provider,' and highlight 'Any Transport: WebRTC, SIP, PSTN' plus a working CLI example (`python bot.py -t twilio -x ...ngrok.io`), showing genuine carrier/SIP flexibility rather than lock-in to one bundled provider. Missing for 10: concrete walkthrough of raw SIP trunk/PBX configuration (vs. just carrier webhooks), and independent/hands-on confirmation of a non-Twilio/Telnyx SIP trunk actually working in production.

   • [claimed-docs] “Telephony bots have a different shape than WebRTC bots. The session doesn't start because a client sent your dispatcher an HTTP request — it…”
   • [claimed-docs] “the carrier (Twilio, Telnyx, Plivo, Exotel, or your SIP provider) is calling your webhook to tell you there's an inbound call”
   • [claimed-docs] “Any Transport: WebRTC, SIP, PSTN”
   • [claimed-docs] “python bot.py -t twilio -x your-name.ngrok.io”

   proof ↗⚑ flag

   Bolna✓fullclaimed8/10

   Bolna explicitly documents 'Bring Your Own Telephony (BYOT)' allowing any standards-compliant SIP trunk to connect to the platform, plus IP whitelisting requirements for the connection, directly addressing carrier/PBX independence from bundled telephony. missing for 10: explicit step-by-step Twilio/Telnyx number import walkthrough and independent/hands-on verification of SIP trunk setup working end-to-end.

   • [claimed-docs] “Bring Your Own Telephony (BYOT) lets you connect any standards-compliant SIP trunk to the Bolna platform.”
   • [claimed-docs] “Whitelist all three IPs on your server or firewall”

   proof ↗⚑ flag

Analytics

1. ai-native userThe platform's AI reviews my calls for me — scoring quality, flagging failures, and analyzing resolution automatically

   weight 2 · round to Bolna
   Pipecat—none0/10

   Pipecat ships developer-facing dev-time Evals (describe expected conversation, run against real agent) plus metrics/transcripts/audio-recording primitives, but there is no evidence of an AI system that automatically reviews production calls, scores quality, flags failures, or analyzes resolution after the fact — Evals is a pre-deployment testing tool, not post-call analytics.

   • [claimed-docs] “Pipecat Evals is the framework's built-in system for testing agent behavior. You describe a conversation and the behavior you expect, and Pi…”
   • [claimed-docs] “You describe a conversation and the behavior you expect, and Pipecat runs it against your real agent (the same pipeline, the same services, …”
   • [claimed-docs] “Pipecat offers built-in metrics for both, which can be enabled with straightforward configuration options.”
   • [claimed-docs] “Pipecat's turn events make it easy to collect both user and assistant messages as they occur.”

   proof ↗⚑ flag

   Bolna~partialclaimed3/10

   Bolna offers post-call analysis primitives — configurable extraction-categories (bolna-docs-1) and toggleable call summaries (bolna-docs-2) — which could be used to build custom scoring/flagging, but there's no documented automated QA/quality-scoring, failure-flagging, or resolution-analysis feature out of the box. Missing for 10: dedicated call-scoring/QA dashboard, automatic failure detection, resolution-analysis reporting, and independent evidence these extraction fields are used for review purposes.

   • [claimed-docs] “POST /agent/{agent_id}/extraction-categories — create a category (name + model) and attach it to an agent”
   • [claimed-docs] “Call summaries are an agent-level toggle: call_summary_enabled (boolean, off by default) on the agent create and update APIs”

   proof ↗⚑ flag

2. founderSee call analytics — success rates, durations, outcomes, sentiment — in dashboards without building my own

   weight 2 · round drawn
   Pipecat—none0/10

   Pipecat exposes low-level building blocks (metrics, transcripts, audio recording, evals) that a developer could use to construct analytics, and a community debugging tool (Whisker) for pipeline tracing — but there is no evidence of a built-in dashboard surfacing success rates, call durations, outcomes, or sentiment without the founder building it themselves.

   • [claimed-docs] “Pipecat offers built-in metrics for both, which can be enabled with straightforward configuration options.”
   • [claimed-docs] “Pipecat's turn events make it easy to collect both user and assistant messages as they occur.”
   • [claimed-docs] “Pipecat's \`AudioBufferProcessor\` makes it easy to capture high-quality audio recordings of both the user and bot during interactions.”
   • [community] “With Whisker you can: View a live graph of your pipeline, watch frame processors flash in real time, select a processor to inspect its frame…”
   • [claimed-docs] “You describe a conversation and the behavior you expect, and Pipecat runs it against your real agent (the same pipeline, the same services, …”

   proof ↗⚑ flag

   Bolna—none0/10

   Evidence only shows API-level features like call summaries (call_summary_enabled) and extraction categories, but there is no mention of a dashboard UI presenting success rates, durrations, outcomes, or sentiment analytics — missing for 10: any dashboard/UI screenshot or docs describing aggregated call analytics views.

   • [claimed-docs] “POST /agent/{agent_id}/extraction-categories — create a category (name + model) and attach it to an agent”
   • [claimed-docs] “Call summaries are an agent-level toggle: call_summary_enabled (boolean, off by default) on the agent create and update APIs”

   proof ↗⚑ flag

Monitoring

1. platform-engineerMonitor live calls in production and get alerts when agents misbehave or error rates spike

   weight 1 · round to Pipecat
   Pipecat~partialcommunity4/10

   Pipecat provides building blocks for observability — built-in metrics (docs-5), turn-event transcripts (docs-4), audio recording (docs-3/21/29), and the community-highlighted Whisker tool that shows a live pipeline graph and frame-level debugger (pipecat-comm-3/4/5) — but these are development/debugging aids, not a production monitoring or alerting system. There is no evidence of dashboards for live production calls, error-rate-spike detection, or alert/notification integrations (e.g., PagerDuty, Slack alerts) for misbehaving agents. Missing for 10: production-grade dashboards for live call monitoring, automated error-rate/anomaly alerting, and integration with on-call/alerting systems.

   • [claimed-docs] “Pipecat offers built-in metrics for both, which can be enabled with straightforward configuration options.”
   • [claimed-docs] “Pipecat's turn events make it easy to collect both user and assistant messages as they occur.”
   • [community] “As someone who spends a lot of time looking at timestamped log lines to debug Pipecat pipelines, I'm a big fan of this work... For 1 and 3 […”
   • [community] “With Whisker you can: View a live graph of your pipeline, watch frame processors flash in real time, select a processor to inspect its frame…”
   • [community] “I had been thinking of working on something like this recently as a way to debug Pipecat pipelines. But the work Aleix has done goes far bey…”

   proof ↗⚑ flag

   Bolna—none0/10

   Evidence covers call summaries, extraction categories, transcripts, CLI, MCP, and SIP/telephony features, but nothing describes live-call monitoring dashboards, real-time observability, or alerting on agent misbehavior or error-rate spikes. No mention of metrics, alert thresholds, webhooks for anomaly detection, or a monitoring console for platform engineers. Missing for 10: real-time monitoring dashboard, alerting/notification system for errors or misbehavior, error-rate tracking, on-call/integration with observability tools.

   ⚑ flag

Testing

1. developerTest agents with simulated conversations or evals before putting them on real phone calls

   weight 2 · round to Pipecat
   Pipecat✓fullprobed8/10

   Pipecat Evals is a documented, built-in framework feature letting developers describe conversations/expected behavior and run them against the real agent pipeline before deployment, and the runtime probe confirms a working `pipecat eval` CLI subcommand exists alongside `init`/`cloud`. This directly addresses simulated-conversation testing before real phone calls, though evidence doesn't show telephony-specific eval scenarios or third-party validation of eval accuracy. Missing for 10: independent/community corroboration of Evals in practice, and explicit examples of testing telephony-specific call flows via evals.

   • [claimed-docs] “Pipecat Evals is the framework's built-in system for testing agent behavior. You describe a conversation and the behavior you expect, and Pi…”
   • [claimed-docs] “You describe a conversation and the behavior you expect, and Pipecat runs it against your real agent (the same pipeline, the same services, …”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Pipecat CLI (pypi pipecat-ai[cli]) ran keylessly via uvx — `pipecat --help` lists init (pr…”

   proof ↗⚑ flag

   Bolna—none0/10

   No evidence of any simulated conversation testing, evals, or pre-production testing framework for agents; the evidence pack only covers deployment, telephony, providers, pricing, and SDKs. Missing for 10: any mention of test/eval tooling, simulated call testing, or conversation quality scoring before live calls.

   ⚑ flag

Post call

1. developerExtract structured data from every call — outcomes, entities, dispositions — delivered via API or webhook after the call

   weight 2 · round to Bolna
   Pipecat~partialclaimed4/10

   Pipecat provides building blocks that a developer could use to build this — Flows functions can 'process data by interfacing with external systems and APIs' (function calling) and turn events/transcripts capture user and assistant messages, plus telephony webhooks for call events — but there is no documented turnkey feature for automatic post-call structured extraction (outcomes/entities/dispositions) delivered via a dedicated API or webhook. Missing for 10: a built-in post-call summary/disposition-extraction pipeline, a documented structured-output schema for call outcomes, and an out-of-box webhook delivery mechanism specifically for post-call analytics (only inbound-call webhooks and generic function-calling/transcript primitives are documented).

   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: 1. Process data ... 2. Progress the conversation by transitioning between nodes”
   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: Process data by interfacing with external systems and APIs...Progress the conversation by…”
   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: 1. Process data by interfacing with external systems and APIs... 2. Progress the conversa…”
   • [claimed-docs] “Flows auto-derives the function's metadata — name, description, parameter properties (with their descriptions), and which parameters are req…”
   • [claimed-docs] “Pipecat's turn events make it easy to collect both user and assistant messages as they occur.”
   • [claimed-docs] “Telephony bots have a different shape than WebRTC bots. The session doesn't start because a client sent your dispatcher an HTTP request — it…”
   • [claimed-docs] “the carrier (Twilio, Telnyx, Plivo, Exotel, or your SIP provider) is calling your webhook to tell you there's an inbound call”

   proof ↗⚑ flag

   Bolna~partialclaimed6/10

   Bolna provides extraction-categories API to attach custom entity/data extraction to agents and a call_summary_enabled toggle for summaries, plus transcript fetch via API — covering entities, summaries, and outcomes. However, there's no explicit documentation of a unified structured 'disposition' field, no clear webhook delivery mechanism for post-call structured payloads (only API fetch is shown), and no example of the combined extraction+summary+disposition JSON schema. missing for 10: webhook-based delivery of extraction results, documented disposition/outcome field, end-to-end example combining all three data types in one payload.

   • [claimed-docs] “POST /agent/{agent_id}/extraction-categories — create a category (name + model) and attach it to an agent”
   • [claimed-docs] “Call summaries are an agent-level toggle: call_summary_enabled (boolean, off by default) on the agent create and update APIs”
   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”

   proof ↗⚑ flag

Tools

1. ai-native userMy voice agent can plug in MCP servers as tool sources so one integration grants it whole toolsets mid-call

   weight 2 · round drawn
   Pipecat—none0/10

   The evidence only shows Pipecat's context-hub *acting as* an MCP server for coding-agent tooling (pipecat-docs-11/38), which is the opposite direction from what the story asks — a voice agent consuming external MCP servers as tool sources mid-call. Function/tool calling is documented via Pipecat Flows (pipecat-docs-6/22/30/39), but no evidence shows the voice agent connecting to or importing toolsets from external MCP servers during a call.

   • [claimed-docs] “pipecat context-hub install registers the hub as an MCP server with your coding agent and builds the local index”
   • [claimed-docs] “pipecat context-hub install` registers the hub as an MCP server with your coding agent and builds the local index”
   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: 1. Process data ... 2. Progress the conversation by transitioning between nodes”
   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: Process data by interfacing with external systems and APIs...Progress the conversation by…”

   proof ↗⚑ flag

   Bolna—none0/10

   Evidence only shows Bolna exposing its OWN MCP server so external clients (Claude, Cursor, Windsurf) can manage a Bolna account (bolna-docs-17, bolna-probe-3) — the reverse direction of the story, which asks whether a Bolna voice agent can consume external MCP servers as tool sources mid-call. No documentation shows Bolna agents acting as an MCP client or importing toolsets from third-party MCP servers during a call. missing for 10: any evidence of Bolna voice agents connecting to external MCP servers as tool sources, mid-call toolset loading via MCP.

   • [claimed-docs] “Connect Claude, Cursor, Windsurf, or any MCP client to your Bolna account with the Bolna MCP server.”
   • [probe] “official MCP server documented at https://www.bolna.ai/docs/build-with-ai/mcp”

   proof ↗⚑ flag

2. developerMy agent can call external APIs and custom functions mid-conversation and speak the result without awkward dead air

   weight 3 · round to Pipecat
   Pipecat✓fullclaimed8/10

   Pipecat Flows functions explicitly support 'processing data by interfacing with external systems and APIs' mid-conversation and auto-derive function schemas from code, while interruption handling and turn detection docs describe how the pipeline manages timing/dead-air around such calls. Missing for 10: no concrete hands-on example/demo showing latency-masking (e.g., filler speech) during a live API call, and no independent benchmark of perceived dead-air during function execution.

   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: 1. Process data ... 2. Progress the conversation by transitioning between nodes”
   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: Process data by interfacing with external systems and APIs...Progress the conversation by…”
   • [claimed-docs] “Functions in Pipecat Flows serve two key purposes: 1. Process data by interfacing with external systems and APIs... 2. Progress the conversa…”
   • [claimed-docs] “Flows auto-derives the function's metadata — name, description, parameter properties (with their descriptions), and which parameters are req…”
   • [claimed-docs] “When the user starts speaking while the bot is talking, the bot stops immediately, in-flight work is cancelled, and the pipeline is ready fo…”
   • [claimed-docs] “Interruptions (also called barge-in) let the user talk over the bot. When the user starts speaking while the bot is talking, the bot stops i…”
   • [claimed-docs] “Smart Turn Detection uses an advanced machine learning model to determine when a user has finished speaking and your bot should respond.”

   proof ↗⚑ flag

   Bolna—none0/10

   The evidence pack covers extraction categories, call summaries, workflows, and custom LLM providers, but nothing describes an agent invoking external APIs or custom functions mid-call and voicing the result seamlessly. Missing for 10: documentation of a function-calling/tool-use API, examples of mid-call API invocation, and any mention of latency-masking/filler techniques to avoid dead air.

   ⚑ flag

Recording

1. platform-engineerRetrieve full call recordings and transcripts programmatically for every call

   weight 2 · round drawn
   Pipecat~partialclaimed5/10

   Pipecat provides building blocks — AudioBufferProcessor for capturing audio recordings and turn-event based transcript collection — that a platform engineer could wire into their own storage/retrieval system, but there's no documented built-in centralized recordings/transcripts store or query API for retrieving them programmatically across all calls. Missing for 10: a first-party recordings/transcripts storage service or retrieval API, evidence of per-call metadata/indexing, and any hands-on confirmation of retrieving historical call data at scale.

   • [claimed-docs] “Pipecat's \`AudioBufferProcessor\` makes it easy to capture high-quality audio recordings of both the user and bot during interactions.”
   • [claimed-docs] “Pipecat's AudioBufferProcessor makes it easy to capture high-quality audio recordings of both the user and bot during interactions.”
   • [claimed-docs] “Pipecat's `AudioBufferProcessor` makes it easy to capture high-quality audio recordings of both the user and bot during interactions.”
   • [claimed-docs] “Pipecat's turn events make it easy to collect both user and assistant messages as they occur.”

   proof ↗⚑ flag

   Bolna~partialclaimed5/10

   Docs confirm fetching call transcripts via API (quickstart mentions 'fetch the transcript') and call summaries can be toggled, but there is no explicit documentation of a dedicated recordings-retrieval endpoint or bulk/programmatic export for all calls. missing for 10: explicit call-recording download/API endpoint, confirmation that recordings are retained and accessible for every call, and independent verification of transcript completeness/format.

   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”
   • [claimed-docs] “Call summaries are an agent-level toggle: call_summary_enabled (boolean, off by default) on the agent create and update APIs”
   • [claimed-docs] “POST /agent/{agent_id}/extraction-categories — create a category (name + model) and attach it to an agent”

   proof ↗⚑ flag

Transcription

1. developerGet accurate real-time transcription with control over the STT provider, language models, or key terms

   weight 2 · round to Pipecat
   Pipecat~partialcommunity6/10

   Docs and community evidence confirm Pipecat lets developers swap STT providers and language models with one line of code (200+ services, local Whisper/Ollama), and it exposes STT-specific latency metrics (TTFS, P99) for tuning accuracy/speed tradeoffs. However, there is no evidence of support for passing custom vocabulary or 'key terms'/boost-word lists to STT providers, and no independent benchmark validating transcription accuracy claims. Missing for 10: explicit key-terms/vocabulary-boost configuration support, and independent/hands-on accuracy validation.

   • [claimed-docs] “Swap speech, language, and vision services from any of 200+ integrated providers and services — usually one line of code.”
   • [claimed-docs] “Pipecat ships with measured P99 latency values for each supported service so that turn detection can account for this delay automatically.”
   • [claimed-docs] “Time To Final Segment (TTFS) measures how long it takes from the moment a user stops speaking until the STT service delivers the final trans…”
   • [community] “Local inference is already supported via Pipecat, you can use ollama or any custom OpenAI endpoint. Local STT is also supported via whisper,…”
   • [community] “Yes, Pipecat already supports that natively, so this can be done easily with ollama... Also, check out any provider they support, and it can…”

   proof ↗⚑ flag

   Bolna~partialclaimed5/10

   Docs confirm STT provider choice (Deepgram, Azure, ElevenLabs) and full LLM control including custom OpenAI-compatible endpoints, plus transcript retrieval via API, giving developers real provider/model flexibility. However there is no evidence of key-term/vocabulary boosting or accuracy tuning controls, nor any real-time transcription accuracy benchmarks. Missing for 10: key-term/keyword-boost configuration, accuracy/latency benchmarks for real-time transcription, and independent validation of transcription quality.

   • [claimed-docs] “Bolna supports Deepgram, Azure, ElevenLabs, and more.”
   • [claimed-docs] “For custom llm simply keep provider in the llm_agent key as custom and add a openai compatible base_url”
   • [claimed-docs] “Make your first Voice AI call with the Bolna API — verify your key, get an agent, place a call, and fetch the transcript in about five minut…”

   proof ↗⚑ flag

Voices

1. founderClone a custom brand voice and use it for my agents, with a documented consent process

   weight 2 · round drawn
   Pipecat—none0/10

   Pipecat's evidence covers swapping among 200+ TTS/STT providers and general voice pipeline features, but nothing addresses custom voice cloning or any documented consent process for cloning a brand voice — this is a fair question since Pipecat is a voice-AI framework, but no evidence supports it being delivered.

   • [claimed-docs] “Swap speech, language, and vision services from any of 200+ integrated providers and services — usually one line of code.”
   • [claimed-docs] “Open source Python framework for building voice and multimodal AI pipelines. Orchestrate 150+ AI services with ultra-low latency.”

   proof ↗⚑ flag

   Bolna—none0/10

   Evidence shows Bolna lets founders choose among third-party voices/accents/styles (bolna-docs-8) and integrates providers like ElevenLabs (bolna-docs-6), but there is no mention of a voice-cloning feature for a custom brand voice, nor any documented consent process for cloning. Missing for 10: voice cloning capability, consent/verification workflow documentation, any policy on brand voice usage.

   • [claimed-docs] “You can choose different voices, accents, and speaking styles to match your brand.”
   • [claimed-docs] “Bolna supports Deepgram, Azure, ElevenLabs, and more.”

   proof ↗⚑ flag

2. developerChoose from a broad voice library or plug in multiple TTS providers to get the voice I want

   weight 2 · round to Pipecat
   Pipecat✓fullcommunity8/10

   Docs and community evidence confirm Pipecat supports swapping speech services (TTS/STT) across 200+ integrated providers with typically one line of code, plus community confirmation of easy onboarding of any provider and local TTS/STT options (ollama, whisper). Missing for 10: an explicit enumerated 'voice library' list or curated voice catalog UI, and independent benchmark of ease/quality across providers beyond vendor/community anecdotes.

   • [claimed-docs] “Swap speech, language, and vision services from any of 200+ integrated providers and services — usually one line of code.”
   • [claimed-docs] “Open source Python framework for building voice and multimodal AI pipelines. Orchestrate 150+ AI services with ultra-low latency.”
   • [community] “Local inference is already supported via Pipecat, you can use ollama or any custom OpenAI endpoint. Local STT is also supported via whisper,…”
   • [community] “Yes, Pipecat already supports that natively, so this can be done easily with ollama... Also, check out any provider they support, and it can…”
   • [claimed-docs] “Pipecat ships with measured P99 latency values for each supported service so that turn detection can account for this delay automatically.”

   proof ↗⚑ flag

   Bolna~partialclaimed6/10

   Docs confirm multiple TTS providers (Deepgram, Azure, ElevenLabs, and more) plus voice/accent/style customization, satisfying the 'plug in providers' part of the story. However, there's no evidence of a broad pre-built voice library or catalog to browse/select from, only provider integration. Missing for 10: evidence of a large built-in voice library/catalog, provider-count breadth beyond three named examples, independent/hands-on confirmation of voice quality or selection UX.

   • [claimed-docs] “Bolna supports Deepgram, Azure, ElevenLabs, and more.”
   • [claimed-docs] “You can choose different voices, accents, and speaking styles to match your brand.”

   proof ↗⚑ flag