Bland vs Deepgram Voice Agent
Bland wins · 29–13 (19 drawn)
Agent building — building agents — abstractions, tool wiring, control flowAgent building
Building agents — abstractions, tool wiring, control flow
Agent ops
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 BlandBland's docs show all three provisioning steps available programmatically: pathway/agent creation via API (bland-docs-1, bland-docs-18), phone number acquisition/porting/Twilio and SIP attachment (bland-docs-3, bland-docs-16, bland-docs-17), and call placement via API or batch calls (bland-docs-6, bland-docs-23). Both the CLI ('make calls, build and test pathways, configure phone numbers' — bland-docs-12) and the MCP server ('place and inspect calls, build and validate pathways, manage agents' — bland-docs-11/20/27) explicitly cover the full create-agent/attach-number/place-call lifecycle without the dashboard, and runtime probes confirm both the CLI and hosted MCP endpoint are live and functional (bland-probe-rt-1, bland-probe-rt-2). Missing for 10: a single consolidated end-to-end tutorial/example walking through create→attach→call in one flow, and independent (non-vendor) confirmation of the full pipeline working end-to-end.
- [claimed-docs] “See the Pathways API reference to create and manage pathways programmatically.”
- [claimed-docs] “Users can connect their own Twilio account to Bland, easily bring over your existing phone numbers to use within the platform.”
- [claimed-docs] “Batch calls let you initiate high-volume call campaigns by uploading a list of recipients via CSV.”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “Manage your entire Bland account from the terminal: make calls, build and test pathways, configure phone numbers, and more.”
- [claimed-docs] “Number porting to bring existing numbers to Bland”
- [claimed-docs] “Bland supports inbound and outbound SIP. Point calls from your carrier or PBX at Bland to be answered by an agent, or have Bland place calls…”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [probe] “PROBE runtime (recorded 2026-09-05): `npx -y bland-cli --version` printed `0.6.2` keylessly — the official npm CLI (bland-cli, with dev term…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the hosted MCP endpoint https://api.bland.ai/v1/mcp returned HTTP 4…”
Deepgram documents agent creation via reusable agent configs (UUID-based), telephony connectivity for inbound/outbound calls, and a CLI with a built-in MCP server giving AI coding tools API access — the building blocks for programmatic provisioning exist. However, the evidence shows phone-call handling is done via a Twilio bridge (server code required) rather than a native Deepgram 'attach number/place call' API, and no doc shows the CLI or MCP server actually exposing agent-create + number-attach + call-place as a single end-to-end flow. Missing for 10: explicit CLI/MCP commands for provisioning a phone number and placing a call, and confirmation that this full workflow avoids external glue code/dashboard steps.
- [claimed-docs] “Reusable Agent Configurations allow you to define and persist the agent block of your Settings message using the Deepgram API. Once created,…”
- [claimed-docs] “Telephony: connect voice agents to phone networks for inbound and outbound calls.”
- [claimed-docs] “The dg CLI includes a built-in MCP (Model Context Protocol) server that gives AI coding tools direct access to Deepgram APIs.”
- [claimed-docs] “Twilio streams the call audio to your server, and your server bridges that audio to the Deepgram Voice Agent API, a single WebSocket that ru…”
- [probe] “official MCP server documented at https://developers.deepgram.com/developer-tools/agentic-tools”
- [probe] “official CLI documented at https://developers.deepgram.com/developer-tools/cli/getting-started”
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 to BlandBland's MCP server lets external AI coding agents 'build and validate pathways ... through natural language' (bland-docs-11/20/27), and the testbed/evals tools support iterating on and grading prompts, which loosely supports AI-assisted authoring. However there is no evidence of a built-in, first-party generative feature where Bland's own platform AI drafts a full pathway/flow/test-cases from a plain-language description inside the product itself — the closest capability requires an external AI agent connecting via MCP. Missing for 10: a native 'describe your agent, we generate the pathway/prompts/tests' feature, in-product prompt-improvement AI, and independent/hands-on confirmation of AI-generated flows.
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The testbed lets you take any call ... isolate a specific node interaction, edit the prompt, and run it multiple times to see how the output…”
- [claimed-docs] “The testbed lets you take any call — whether it's a historical call from call logs or a test chat from the pathway editor — isolate a specif…”
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges.”
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges. You define eval agents, each of which grades one dimension of a call”
Deepgram Voice Agentnone0/10Evidence covers building agents manually (prompting, function calling, reusable configs, MCP server for coding tools) but there is no mention of the platform's own AI generating or improving prompts, flows, or test cases from a description; the MCP server exposes Deepgram APIs to external coding assistants rather than being an AI author within the platform itself.
- [claimed-docs] “Prompting: write system prompts that shape live-call behavior.”
- [claimed-docs] “Reusable Agent Configurations allow you to define and persist the agent block of your Settings message using the Deepgram API. Once created,…”
- [claimed-docs] “The dg CLI includes a built-in MCP (Model Context Protocol) server that gives AI coding tools direct access to Deepgram APIs.”
- [probe] “official MCP server documented at https://developers.deepgram.com/developer-tools/agentic-tools”
Build
developerBuild a working phone voice agent — prompt, voice, and phone number — and take my first live call within an hour
weight 3 · round to BlandDocs cover the whole first-call workflow: creating a pathway/prompt (bland-docs-18, bland-docs-26, bland-docs-30), voice cloning/selection (bland-docs-10), phone number setup via own Twilio or new inbound numbers (bland-docs-3, bland-docs-24), and dispatching outbound calls (bland-docs-23), plus a CLI and MCP server confirmed live at runtime (bland-probe-rt-1, bland-probe-rt-2) that let a developer configure and place calls quickly. Missing for 10: no independent hands-on account of a developer actually completing a first call within an hour, and one community comment notes cost concerns rather than time-to-first-call, so onboarding speed is only documented, not externally verified.
- [claimed-docs] “Conversational pathways are our new way of prompting Bland that has led to major breakthroughs in realism. Give your agent instructions on h…”
- [claimed-docs] “Conversational pathways are our new way of prompting Bland that has led to major breakthroughs in realism.”
- [claimed-docs] “Give your agent instructions on how it should respond at specific points of the conversation. Choose between prompting or fixed sentences. E…”
- [claimed-docs] “A clone needs one clean sample of about ten seconds. Quality of the sample sets the ceiling on quality of the voice”
- [claimed-docs] “Users can connect their own Twilio account to Bland, easily bring over your existing phone numbers to use within the platform.”
- [claimed-docs] “Create inbound phone numbers for customer support, etc.”
- [claimed-docs] “Dispatch AI phone calls to call customers, leads, and to streamline operations.”
- [claimed-docs] “The API integration lets you connect your AI agent to any HTTP endpoint.”
- [probe] “PROBE runtime (recorded 2026-09-05): `npx -y bland-cli --version` printed `0.6.2` keylessly — the official npm CLI (bland-cli, with dev term…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the hosted MCP endpoint https://api.bland.ai/v1/mcp returned HTTP 4…”
Deepgram provides all core building blocks — prompting, voice/LLM selection, telephony via Twilio bridging, and a single WebSocket API — that together could plausibly get a developer to a first live call quickly. However, the telephony path requires standing up your own server to bridge Twilio audio to the Voice Agent WebSocket, which is nontrivial integration work rather than a turnkey 'phone number in one hour' flow, and there's no first-party quickstart or time-to-first-call benchmark cited. missing for 10: an end-to-end quickstart/tutorial demonstrating full setup within an hour, evidence of a managed/no-code telephony number provisioning path, and independent hands-on confirmation of setup speed.
- [claimed-docs] “Deepgram's Voice Agent API collapses that stack into a single, unified API. You open one WebSocket connection, send audio in, and receive au…”
- [claimed-docs] “Telephony: connect voice agents to phone networks for inbound and outbound calls.”
- [claimed-docs] “Prompting: write system prompts that shape live-call behavior.”
- [claimed-docs] “Supported LLM providers | Parameter | open_ai | anthropic | aws_bedrock | google | groq | nvidia”
- [claimed-docs] “Twilio streams the call audio to your server, and your server bridges that audio to the Deepgram Voice Agent API, a single WebSocket that ru…”
- [claimed-docs] “That includes barge-in, the ability to talk over the agent and have it stop instantly.”
developerRun conversations in multiple languages, including detecting and switching language mid-call
weight 2 · round to Deepgram Voice AgentBlandnone0/10The evidence pack contains no mention of multi-language support, language detection, or mid-call language switching anywhere in Bland's docs; only pathways, TTS voice cloning, and infrastructure features are documented. Missing for 10: any documentation of multilingual conversation support, automatic language detection, or dynamic language switching mid-call.
Deepgram's docs confirm multilingual voice agent support, noting that STT and TTS model choices must be configured for the target language (deepgram-docs-10), but the evidence pack does not explicitly document automatic language detection or dynamic switching mid-call — only static multilingual configuration is described. Missing for 10: explicit documentation of automatic language detection, mid-call language switching mechanics, and independent/hands-on confirmation of this behavior in production.
- [claimed-docs] “A multilingual voice agent has two model decisions: which STT model transcribes the user, and which TTS model speaks the agent.”
founderDesign multi-step conversation flows in a visual builder with branching, states, and handoffs without writing code
weight 2 · round to BlandBland's 'Conversational Pathways' feature is explicitly a node-based flow builder where founders give instructions at specific conversation points, test individual node interactions in a pathway editor/testbed, and publish drafts separately from production—matching branching/states/handoffs without code (bland-docs-18, 26, 30, 28, 19). Missing for 10: explicit confirmation of a drag-and-drop visual canvas UI (docs describe 'nodes' and 'pathway editor' but no screenshot/UI walkthrough) and independent hands-on corroboration beyond vendor docs.
- [claimed-docs] “Conversational pathways are our new way of prompting Bland that has led to major breakthroughs in realism. Give your agent instructions on h…”
- [claimed-docs] “Conversational pathways are our new way of prompting Bland that has led to major breakthroughs in realism.”
- [claimed-docs] “Give your agent instructions on how it should respond at specific points of the conversation. Choose between prompting or fixed sentences. E…”
- [claimed-docs] “The testbed lets you take any call — whether it's a historical call from call logs or a test chat from the pathway editor — isolate a specif…”
- [claimed-docs] “When you edit a pathway, you are working on a draft. Live calls are not affected. They keep using the published production version.”
- [claimed-docs] “See the Pathways API reference to create and manage pathways programmatically.”
Deepgram Voice Agentnone0/10All evidence describes a code/API-first architecture (WebSocket connections, JSON Settings messages, system prompts, function calling, CLI/SDK) rather than a visual no-code builder; there is no mention of a drag-and-drop flow designer, branching UI, or state-machine editor. missing for 10: any visual builder UI, no-code branching/state design, or drag-and-drop handoff configuration.
- [claimed-docs] “Deepgram's Voice Agent API collapses that stack into a single, unified API. You open one WebSocket connection, send audio in, and receive au…”
- [claimed-docs] “Multi-Agent Architecture: orchestrate multiple specialized agents that hand off based on context, intent, or domain.”
- [claimed-docs] “Reusable Agent Configurations allow you to define and persist the agent block of your Settings message using the Deepgram API. Once created,…”
- [claimed-docs] “Prompting: write system prompts that shape live-call behavior.”
- [claimed-docs] “Supported LLM providers | Parameter | open_ai | anthropic | aws_bedrock | google | groq | nvidia”
Personalization
developerInject dynamic variables and per-caller context at call time so each conversation is personalized
weight 2 · round to Deepgram Voice AgentEvidence shows personalization mechanisms exist—Memory for per-caller context (bland-docs-9), batch calls that likely carry per-recipient data (bland-docs-6), and pathway webhooks/API integrations that could fetch live data (bland-docs-4, bland-docs-30)—but there is no explicit documentation of a 'dynamic variables' injection API or call-time variable substitution mechanism. missing for 10: explicit dynamic-variable/request_data injection documentation, examples of per-call variable interpolation into prompts, independent confirmation of personalization working in practice.
- [claimed-docs] “Memory lets Bland agents remember people across conversations, including calls, SMS, and other channels, so each interaction feels continuou…”
- [claimed-docs] “Batch calls let you initiate high-volume call campaigns by uploading a list of recipients via CSV.”
- [claimed-docs] “The API integration lets you connect your AI agent to any HTTP endpoint.”
- [claimed-docs] “Give your agent instructions on how it should respond at specific points of the conversation. Choose between prompting or fixed sentences. E…”
Deepgram supports prompting, reusable agent configs (passed at call time via UUID), function calling, and mid-call message injection, which together allow injecting per-call context/variables into agent behavior; A/B testing of configs also implies runtime parameterization. However there is no explicit documented mechanism for templated dynamic variables (e.g., {{caller_name}}) or a dedicated per-caller context API akin to other platforms. missing for 10: explicit dynamic variable templating syntax, dedicated per-caller metadata injection API, hands-on example of personalizing a call with caller-specific data.
- [claimed-docs] “Reusable Agent Configurations allow you to define and persist the agent block of your Settings message using the Deepgram API. Once created,…”
- [claimed-docs] “Prompting: write system prompts that shape live-call behavior.”
- [claimed-docs] “Inject agent message | Mid-call | InjectAgentMessage | Makes the agent speak a specific line”
- [claimed-docs] “A/B testing voices or prompts — Run two configurations in parallel and measure conversion, CSAT, or containment rate to pick a winner—no cod…”
- [claimed-docs] “In the context of Deepgram Voice Agents, function calling enables your agent to perform tasks during a live conversation.”
developerGround the agent on my documents with a built-in knowledge base or RAG so it answers from my content
weight 2 · round drawnBlandnone0/10Bland is a voice AI/phone agent platform; evidence covers pathways, memory, tools, MCP, CLI, etc., but nowhere mentions a document knowledge base or RAG capability for grounding agent responses in uploaded content. Since a voice/conversational agent platform could plausibly ship this (many competitors do), absence of evidence makes this 'none' rather than 'na'.
Deepgram Voice Agentnone0/10The evidence pack covers architecture, function calling, multi-agent handoff, telephony, prompting, and LLM providers, but nowhere documents a built-in knowledge base or RAG feature for grounding the agent on user documents. Function calling ([deepgram-docs-2]) could theoretically be wired to an external retrieval system, but that is not the same as a built-in KB/RAG capability, and no such feature is described.
- [claimed-docs] “In the context of Deepgram Voice Agents, function calling enables your agent to perform tasks during a live conversation.”
- [claimed-docs] “Multi-Agent Architecture: orchestrate multiple specialized agents that hand off based on context, intent, or domain.”
- [claimed-docs] “Prompting: write system prompts that shape live-call behavior.”
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to Deepgram Voice AgentBland has a confirmed live llms.txt at docs.bland.ai/llms.txt (HTTP 200) providing agent-oriented documentation, plus an official MCP server and CLI explicitly designed for AI coding agents to interact with the platform via natural language. missing for 10: independent third-party confirmation that agents actually consume llms.txt successfully in practice, and broader agent-oriented docs beyond the single llms.txt file.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.bland.ai/llms.txt # Bland Documentation Bland is an enterprise voice AI platform for high-volume, …”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [probe] “official MCP server documented at https://docs.bland.ai/integrations/mcp/overview”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the hosted MCP endpoint https://api.bland.ai/v1/mcp returned HTTP 4…”
Direct probe confirms llms.txt exists at developers.deepgram.com/llms.txt (HTTP 200) with explicit AI-agent instructions, and docs pages support .md suffix for clean markdown retrieval, both verified by live probes. missing for 10: no independent third-party confirmation of an agent actually consuming this in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.deepgram.com/llms.txt # Deepgram's Docs ## Instructions for AI Agents - For clean Markdown …”
- [probe] “PROBE docs-md: HTTP 200 at https://developers.deepgram.com/docs/voice-agent.md > For clean Markdown of any page, append .md to the page URL.…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to BlandBland offers a full programmatic/REST API for pathways, calls, batch calls, webhooks, and evals, plus an official CLI (verified runtime installable keylessly via npx) for terminal-based automation, enabling headless/CI usage. missing for 10: no explicit CI/CD pipeline example (e.g., GitHub Actions) or independent case study confirming CI usage beyond docs and CLI probe.
- [claimed-docs] “See the Pathways API reference to create and manage pathways programmatically.”
- [claimed-docs] “Batch calls let you initiate high-volume call campaigns by uploading a list of recipients via CSV.”
- [claimed-docs] “Manage your entire Bland account from the terminal: make calls, build and test pathways, configure phone numbers, and more.”
- [probe] “official CLI documented at https://docs.bland.ai/sdks/cli”
- [probe] “PROBE runtime (recorded 2026-09-05): `npx -y bland-cli --version` printed `0.6.2` keylessly — the official npm CLI (bland-cli, with dev term…”
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges.”
The Voice Agent is a WebSocket API (no GUI dependency) and Deepgram ships a terminal-based `dg` CLI for scripting Deepgram operations (transcribe, synthesize, manage account) which is inherently automatable/CI-friendly, and temporary tokens support secure automated auth. However, there is no explicit documentation of running the Voice Agent itself headlessly in CI pipelines, no CI/CD examples, and the CLI's primary use-cases described are transcription/synthesis rather than orchestrating full voice-agent sessions programmatically. Missing for 10: dedicated CI/headless automation guide for Voice Agent sessions, example CI pipeline configs, and confirmation the CLI can drive the Agent API end-to-end rather than just STT/TTS.
- [claimed-docs] “Deepgram's Voice Agent API collapses that stack into a single, unified API. You open one WebSocket connection, send audio in, and receive au…”
- [claimed-docs] “The dg CLI lets you transcribe files, stream live audio, synthesize speech, analyze text, and manage your Deepgram account from the terminal…”
- [claimed-docs] “Unlike traditional API keys, temporary tokens are ideal for real-time applications requiring secure, temporary access to Deepgram's services…”
- [probe] “official CLI documented at https://developers.deepgram.com/developer-tools/cli/getting-started”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round drawnBlandnone0/10Bland's evidence only documents it exposing an outbound MCP server so that external AI coding agents can call Bland's own tools (docs-11, docs-20, docs-27, probe-rt-2) — the reverse direction of this story. There is no evidence that Bland itself can consume/plug in third-party MCP servers as a client; its tool integration story is limited to custom HTTP API endpoints and webhooks (bland-docs-4, bland-docs-25).
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The API integration lets you connect your AI agent to any HTTP endpoint.”
- [claimed-docs] “Connect external APIs and take live actions during phone calls.”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the hosted MCP endpoint https://api.bland.ai/v1/mcp returned HTTP 4…”
Deepgram Voice Agentnone0/10Deepgram Voice Agent supports function calling for custom tool use, but there is no evidence the Voice Agent can act as an MCP client to consume external MCP servers' tools. The only MCP-related evidence is a built-in MCP *server* in the `dg` CLI that lets coding tools access Deepgram's APIs — the opposite direction of the story.
- [claimed-docs] “In the context of Deepgram Voice Agents, function calling enables your agent to perform tasks during a live conversation.”
- [claimed-docs] “The dg CLI includes a built-in MCP (Model Context Protocol) server that gives AI coding tools direct access to Deepgram APIs.”
- [probe] “official MCP server documented at https://developers.deepgram.com/developer-tools/agentic-tools”
ai-native userConnect an agent via an official MCP server
weight 3 · round to BlandBland ships an official MCP server (docs and runtime probe confirm it's live and gated by API key) that lets AI coding agents place/inspect calls, build pathways, manage agents, query analytics, run evals, and search docs — directly fulfilling the story. Missing for 10: independent third-party hands-on review of the MCP server beyond vendor docs/probe.
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [probe] “official MCP server documented at https://docs.bland.ai/integrations/mcp/overview”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the hosted MCP endpoint https://api.bland.ai/v1/mcp returned HTTP 4…”
Deepgram ships an official MCP server (bundled in the dg CLI) that lets AI coding tools/agents connect directly to Deepgram's APIs, confirmed both in docs and via a dedicated agentic-tools page. This directly satisfies the story of connecting an agent to Deepgram via an official MCP server. Missing for 10: independent/hands-on verification that the MCP server works reliably in practice, and more detail on which Voice Agent capabilities specifically are exposed through it.
- [claimed-docs] “The dg CLI includes a built-in MCP (Model Context Protocol) server that gives AI coding tools direct access to Deepgram APIs.”
- [probe] “official MCP server documented at https://developers.deepgram.com/developer-tools/agentic-tools”
- [claimed-docs] “The dg CLI lets you transcribe files, stream live audio, synthesize speech, analyze text, and manage your Deepgram account from the terminal…”
ai-native userUse an official CLI
weight 2 · round to BlandBland ships an official CLI (bland-cli) documented to manage the entire account from the terminal, and a runtime probe confirms it installs and runs via npx keylessly. missing for 10: independent third-party review/usage reports of the CLI beyond the official docs and one probe run.
- [claimed-docs] “Manage your entire Bland account from the terminal: make calls, build and test pathways, configure phone numbers, and more.”
- [probe] “official CLI documented at https://docs.bland.ai/sdks/cli”
- [probe] “PROBE runtime (recorded 2026-09-05): `npx -y bland-cli --version` printed `0.6.2` keylessly — the official npm CLI (bland-cli, with dev term…”
Deepgram ships an official 'dg' CLI for transcribing files, streaming audio, synthesizing speech, and managing accounts from the terminal, and it even embeds an MCP server for AI coding tools, directly supporting agentic/AI-native workflows. Missing for 10: independent/hands-on corroboration beyond first-party docs and more detail on CLI coverage of Voice Agent-specific features.
- [claimed-docs] “The dg CLI lets you transcribe files, stream live audio, synthesize speech, analyze text, and manage your Deepgram account from the terminal…”
- [claimed-docs] “The dg CLI includes a built-in MCP (Model Context Protocol) server that gives AI coding tools direct access to Deepgram APIs.”
- [probe] “official CLI documented at https://developers.deepgram.com/developer-tools/cli/getting-started”
- [probe] “official MCP server documented at https://developers.deepgram.com/developer-tools/agentic-tools”
ai-native userDrive the product through a documented public API
weight 3 · round drawnBland documents a comprehensive public API (pathways, calls, tools, webhooks, evals, batch calls) plus SDKs, CLI, and an official MCP server, and runtime probes confirm the CLI installs and the hosted MCP endpoint is live and gated as documented, showing agentic programmatic control. Missing for 10: a formally published OpenAPI/Swagger spec (probe found 404s at standard OpenAPI paths), so machine-readable spec discoverability is unconfirmed.
- [claimed-docs] “See the Pathways API reference to create and manage pathways programmatically.”
- [claimed-docs] “The API integration lets you connect your AI agent to any HTTP endpoint.”
- [claimed-docs] “Batch calls let you initiate high-volume call campaigns by uploading a list of recipients via CSV.”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “Manage your entire Bland account from the terminal: make calls, build and test pathways, configure phone numbers, and more.”
- [probe] “official MCP server documented at https://docs.bland.ai/integrations/mcp/overview”
- [probe] “official CLI documented at https://docs.bland.ai/sdks/cli”
- [probe] “PROBE runtime (recorded 2026-09-05): `npx -y bland-cli --version` printed `0.6.2` keylessly — the official npm CLI (bland-cli, with dev term…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the hosted MCP endpoint https://api.bland.ai/v1/mcp returned HTTP 4…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.bland.ai/openapi.json, https://docs.bland.ai/swagger.json, https://docs.bland.ai/api/op…”
Deepgram publishes a documented public API (WebSocket-based Voice Agent API plus OpenAPI spec confirmed live), extensive docs covering endpoints, function calling, LLM providers, telephony, and auth, and even a CLI/MCP server for programmatic/agentic access, making it clearly drivable by an AI-native user. Missing for 10: independent third-party corroboration of API usage beyond vendor docs.
- [claimed-docs] “Deepgram's Voice Agent API collapses that stack into a single, unified API. You open one WebSocket connection, send audio in, and receive au…”
- [probe] “PROBE openapi: HTTP 200 at https://developers.deepgram.com/openapi.json — contains "openapi" key”
- [claimed-docs] “The dg CLI lets you transcribe files, stream live audio, synthesize speech, analyze text, and manage your Deepgram account from the terminal…”
- [claimed-docs] “The dg CLI includes a built-in MCP (Model Context Protocol) server that gives AI coding tools direct access to Deepgram APIs.”
- [probe] “official CLI documented at https://developers.deepgram.com/developer-tools/cli/getting-started”
- [claimed-docs] “Unlike traditional API keys, temporary tokens are ideal for real-time applications requiring secure, temporary access to Deepgram's services…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to Deepgram Voice AgentBlandnone0/10Evidence shows generic API-key auth and JWT-based webhook verification (bland-docs-15), but nothing about issuing scoped or least-privilege credentials specific to an agent's permissions (e.g., role-based API keys, scoped tokens limiting call/pathway/account access). Missing for 10: documentation of scoped API key creation, permission levels, or per-agent credential restriction.
- [claimed-docs] “JWT signatures eliminate these risks through asymmetric cryptography - you verify requests using our public JWKS endpoint without storing an…”
Deepgram documents temporary, short-lived tokens as an alternative to traditional API keys for secure, limited-duration access (deepgram-docs-14), which partially satisfies a least-privilege credential story, but there is no evidence of granular scopes/permissions (e.g., restricting a key to specific endpoints or agent capabilities) or role-based access control for agents. Missing for 10: documented scope/permission granularity, per-agent key restriction, and evidence of enforcement/verification of least-privilege in practice.
- [claimed-docs] “Unlike traditional API keys, temporary tokens are ideal for real-time applications requiring secure, temporary access to Deepgram's services…”
ai-native userBuild against official SDKs
weight 2 · round to BlandBland documents a Web Agent SDK for embedding voice agents (React/Vanilla JS/Node), a CLI, and a REST API used throughout tutorials, giving AI-native developers concrete building blocks; runtime probes confirm the CLI installs and runs. However, no dedicated 'official SDK' page for server-side languages (Python/Node backend SDK) is evidenced, and openapi/swagger spec endpoints all 404, suggesting the API reference isn't machine-consumable in a standard SDK-generation format. Missing for 10: a clearly documented multi-language backend SDK (Python/Node) beyond the browser widget SDK, and a working OpenAPI spec for auto-generating clients.
- [claimed-docs] “Embed a Bland voice agent into any web application (React, Vanilla JS, or Node). The SDK handles secure authentication between your server a…”
- [claimed-docs] “Manage your entire Bland account from the terminal: make calls, build and test pathways, configure phone numbers, and more.”
- [probe] “official CLI documented at https://docs.bland.ai/sdks/cli”
- [probe] “PROBE runtime (recorded 2026-09-05): `npx -y bland-cli --version` printed `0.6.2` keylessly — the official npm CLI (bland-cli, with dev term…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.bland.ai/openapi.json, https://docs.bland.ai/swagger.json, https://docs.bland.ai/api/op…”
- [claimed-docs] “See the Pathways API reference to create and manage pathways programmatically.”
Evidence shows an official 'Browser Agent SDK' with composable packages, plus an OpenAPI spec, CLI, and MCP server for developer tooling, indicating some official SDK/build tooling exists. However, evidence does not mention broader server-side/language SDKs (Python, Node, Go, etc.) commonly expected for building agentic applications, nor independent corroboration of SDK quality. Missing for 10: multi-language SDK documentation, independent/hands-on developer reports, broader agentic build examples beyond browser.
- [claimed-docs] “Browser Agent SDK: add voice AI to any web application via four composable packages.”
- [probe] “PROBE openapi: HTTP 200 at https://developers.deepgram.com/openapi.json — contains "openapi" key”
- [probe] “official CLI documented at https://developers.deepgram.com/developer-tools/cli/getting-started”
- [probe] “official MCP server documented at https://developers.deepgram.com/developer-tools/agentic-tools”
ai-native userSubscribe to events via webhooks
weight 2 · round to BlandBland documents post-call webhooks (automatic HTTP notifications sent after a call completes) and pathway-level webhook execution at specific conversation points, showing genuine event-driven webhook support tied to call lifecycle. However, evidence only covers call-related events (completion, in-call triggers) — missing for 10: a general-purpose event subscription/webhook management API covering other account events (e.g., evals, batch campaign status, pathway publishes), and any independent confirmation of webhook reliability/configuration options.
- [claimed-docs] “Post-call webhooks are HTTP notifications that Bland AI automatically sends to your server after a phone call completes.”
- [claimed-docs] “Give your agent instructions on how it should respond at specific points of the conversation. Choose between prompting or fixed sentences. E…”
Deepgram Voice Agentnone0/10The evidence pack shows Deepgram Voice Agent operates via a persistent WebSocket connection for real-time audio streaming, not webhook-based event subscription; no documentation mentions webhooks for event notifications (e.g., call completion, transcript ready, errors). Absence of evidence for an applicable capability yields 'none'.
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to BlandBland offers LLM-judge Evals to grade call quality and an MCP integration that can 'query analytics' on your account data, which are AI-generated evaluative outputs derived from your call data, but there's no dedicated insights/suggestions dashboard or proactive recommendation feature described. Missing for 10: a native analytics/insights UI, evidence of proactive suggestions surfaced to users, and independent confirmation of these AI-generated insights in practice.
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges.”
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges. You define eval agents, each of which grades one dimension of a call”
- [claimed-docs] “Memory lets Bland agents remember people across conversations, including calls, SMS, and other channels, so each interaction feels continuou…”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
Deepgram Voice Agentnone0/10The evidence pack covers Deepgram Voice Agent's API capabilities (function calling, multi-agent orchestration, telephony, LLM providers, prompting) but contains no mention of an in-product analytics dashboard, conversation insights, or AI-generated suggestions derived from a user's own data. While such a feature (e.g., call analytics/insights) is plausible for a voice AI platform, no evidence shows Deepgram surfaces this.
ai-native userSet up automations that run autonomously in the background
weight 2 · round to BlandBland supports batch calls, webhooks, pathways, and scheduled/triggered call campaigns that run without manual intervention, which constitute a form of autonomous background automation for voice workflows. However, this is scoped to phone-call automation only, not general-purpose background task/agent scheduling. missing for 10: evidence of a generic scheduler/cron-like trigger system, independent hands-on validation of unattended background runs, and confirmation of failure handling/monitoring for long-running autonomous automations.
- [claimed-docs] “Batch calls let you initiate high-volume call campaigns by uploading a list of recipients via CSV.”
- [claimed-docs] “Post-call webhooks are HTTP notifications that Bland AI automatically sends to your server after a phone call completes.”
- [claimed-docs] “Conversational pathways are our new way of prompting Bland that has led to major breakthroughs in realism. Give your agent instructions on h…”
- [claimed-docs] “Give your agent instructions on how it should respond at specific points of the conversation. Choose between prompting or fixed sentences. E…”
- [claimed-docs] “Dispatch AI phone calls to call customers, leads, and to streamline operations.”
- [claimed-docs] “Connect external APIs and take live actions during phone calls.”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to BlandBland's core product is a built-in AI voice agent that users delegate tasks to (placing/answering calls, executing pathways, calling APIs, remembering context) rather than a separate feature bolted on — e.g., 'Dispatch AI phone calls to call customers, leads, and to streamline operations' and pathway/tool/memory docs show rich task delegation to the built-in agent. Missing for 10: independent/hands-on evidence of real-world task delegation outcomes beyond vendor docs.
- [claimed-docs] “Dispatch AI phone calls to call customers, leads, and to streamline operations.”
- [claimed-docs] “Conversational pathways are our new way of prompting Bland that has led to major breakthroughs in realism. Give your agent instructions on h…”
- [claimed-docs] “Connect external APIs and take live actions during phone calls.”
- [claimed-docs] “Memory lets Bland agents remember people across conversations, including calls, SMS, and other channels, so each interaction feels continuou…”
- [claimed-docs] “Give your agent instructions on how it should respond at specific points of the conversation. Choose between prompting or fixed sentences. E…”
ai-native userOperate the product with natural-language commands
weight 2 · round drawnBland offers an official MCP server that lets AI agents operate the entire account (calls, pathways, agents, analytics, evals) via natural language, plus an official CLI, both confirmed live via runtime probes. missing for 10: independent/hands-on third-party review of the MCP/CLI natural-language experience beyond vendor docs and probes.
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [probe] “official MCP server documented at https://docs.bland.ai/integrations/mcp/overview”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the hosted MCP endpoint https://api.bland.ai/v1/mcp returned HTTP 4…”
- [claimed-docs] “Manage your entire Bland account from the terminal: make calls, build and test pathways, configure phone numbers, and more.”
- [probe] “official CLI documented at https://docs.bland.ai/sdks/cli”
- [probe] “PROBE runtime (recorded 2026-09-05): `npx -y bland-cli --version` printed `0.6.2` keylessly — the official npm CLI (bland-cli, with dev term…”
Deepgram Voice Agent is fundamentally a conversational system: users interact via natural spoken language, and the agent supports function calling to perform tasks, live prompting to shape behavior, and mid-call message injection—all driven by natural-language conversation rather than rigid commands. This is core, well-documented functionality (docs-2, docs-7, docs-11) directly matching the story's intent for an ai-native/agentic persona. Missing for 10: independent/hands-on validation of natural-language command accuracy and no evidence of complex multi-turn command chaining reliability from third-party sources.
- [claimed-docs] “In the context of Deepgram Voice Agents, function calling enables your agent to perform tasks during a live conversation.”
- [claimed-docs] “Prompting: write system prompts that shape live-call behavior.”
- [claimed-docs] “Inject agent message | Mid-call | InjectAgentMessage | Makes the agent speak a specific line”
- [claimed-docs] “Multi-Agent Architecture: orchestrate multiple specialized agents that hand off based on context, intent, or domain.”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnBlandnone0/10Docs reference an API reference for pathways but no evidence of an interactive playground with runnable examples; a probe for OpenAPI/Swagger specs at standard paths returned 404s, suggesting no such interactive reference exists.
- [claimed-docs] “See the Pathways API reference to create and manage pathways programmatically.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.bland.ai/openapi.json, https://docs.bland.ai/swagger.json, https://docs.bland.ai/api/op…”
Deepgram Voice Agentnone0/10Evidence shows an OpenAPI spec exists and docs pages are available as clean Markdown, but there is no evidence of an interactive API reference with runnable/try-it-now examples (e.g., embedded playground, live code execution, or Swagger/Postman-style explorer). Missing for 10: interactive explorer UI, runnable/executable code snippets, live request/response testing.
- [probe] “PROBE openapi: HTTP 200 at https://developers.deepgram.com/openapi.json — contains "openapi" key”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.deepgram.com/llms.txt # Deepgram's Docs ## Instructions for AI Agents - For clean Markdown …”
- [probe] “PROBE docs-md: HTTP 200 at https://developers.deepgram.com/docs/voice-agent.md > For clean Markdown of any page, append .md to the page URL.…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to Deepgram Voice AgentBlandnone0/10A direct probe found no OpenAPI/Swagger spec at any expected location (all 404s), and no evidence pack item shows a downloadable machine-readable API spec despite extensive API documentation.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.bland.ai/openapi.json, https://docs.bland.ai/swagger.json, https://docs.bland.ai/api/op…”
A probe confirms Deepgram publishes a machine-readable OpenAPI spec at openapi.json containing the 'openapi' key, directly satisfying the story. Missing for 10: no first-party docs page explicitly announcing/describing the OpenAPI spec's coverage or versioning.
- [probe] “PROBE openapi: HTTP 200 at https://developers.deepgram.com/openapi.json — contains "openapi" key”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round to BlandBland provides draft/staging pathway editing where live production calls are unaffected, plus a testbed for isolated node testing, canary deployments, and staged version adoption — all functioning as sandbox-like mechanisms distinct from production. However, there's no explicit 'sandbox environment' or dedicated test account/data isolation concept described, and testing still appears to involve real calls/production infrastructure rather than a fully isolated non-production environment. missing for 10: a dedicated sandbox/test-mode account distinct from production billing and phone infrastructure, explicit documentation of synthetic/non-production test data, and independent confirmation that testbed/draft testing never touches real production call data or costs.
- [claimed-docs] “You can also promote a version to staging to test it before it goes live, or send an individual call against a specific”
- [claimed-docs] “When you edit a pathway, you are working on a draft. Live calls are not affected. They keep using the published production version.”
- [claimed-docs] “The testbed lets you take any call ... isolate a specific node interaction, edit the prompt, and run it multiple times to see how the output…”
- [claimed-docs] “The testbed lets you take any call — whether it's a historical call from call logs or a test chat from the pathway editor — isolate a specif…”
- [claimed-docs] “Bland supports canary deployments — a way to run a new release on a separate set of containers alongside your production infrastructure and …”
- [claimed-docs] “This is how you A/B test a new agent release against your live production version, with real calls, before committing to a full rollout.”
Deepgram Voice Agentnone0/10No evidence pack item mentions a sandbox environment, test/dev API keys, or a way to test without touching production data or usage; only production endpoints, EU endpoint, and opt-out flags are documented. Missing for 10: sandbox/test-mode environment, documentation of non-production keys or test credits, any guidance on isolating test traffic from production data.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round to BlandBland documents infrastructure versioning concepts (staged/canary rollouts, choosing when to adopt a new release, draft vs. production pathway versions) but there is no evidence of a documented API versioning scheme (e.g., v1/v2 endpoints) or an explicit deprecation policy for its APIs, and the OpenAPI spec probe returned 404s. missing for 10: documented API version numbering/endpoints, an explicit deprecation/sunset policy for APIs, published OpenAPI spec, and independent confirmation of versioning practices.
- [claimed-docs] “You choose when to adopt a new release. Your infrastructure stays on the version you've selected until you decide to move forward.”
- [claimed-docs] “Bland supports canary deployments — a way to run a new release on a separate set of containers alongside your production infrastructure and …”
- [claimed-docs] “You choose when to adopt a new release... Bland supports canary deployments — a way to run a new release on a separate set of containers alo…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.bland.ai/openapi.json, https://docs.bland.ai/swagger.json, https://docs.bland.ai/api/op…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to BlandBatch calls let users upload a CSV of recipients to initiate high-volume call campaigns, directly enabling bulk operations across many items, and the CLI/MCP server extend programmatic/bulk management of pathways, agents, and calls. Missing for 10: independent/hands-on verification of batch call performance at scale, and documentation of bulk operations beyond calls (e.g., bulk pathway or number management).
- [claimed-docs] “Batch calls let you initiate high-volume call campaigns by uploading a list of recipients via CSV.”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “Manage your entire Bland account from the terminal: make calls, build and test pathways, configure phone numbers, and more.”
- [probe] “PROBE runtime (recorded 2026-09-05): `npx -y bland-cli --version` printed `0.6.2` keylessly — the official npm CLI (bland-cli, with dev term…”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to BlandBland's pathways let users define conditional logic that executes webhooks/API calls at specific conversation nodes, and post-call webhooks automatically fire HTTP notifications when a call-completion event occurs — this is a documented rules-trigger-action-on-event mechanism. missing for 10: independent/hands-on verification of the webhook triggering in production, and evidence of event types beyond call-based ones (e.g., generic account-level event automation).
- [claimed-docs] “Post-call webhooks are HTTP notifications that Bland AI automatically sends to your server after a phone call completes.”
- [claimed-docs] “Give your agent instructions on how it should respond at specific points of the conversation. Choose between prompting or fixed sentences. E…”
- [claimed-docs] “Connect external APIs and take live actions during phone calls.”
- [claimed-docs] “Conversational pathways are our new way of prompting Bland that has led to major breakthroughs in realism. Give your agent instructions on h…”
Deepgram Voice Agent supports function calling that lets the agent trigger actions during a live conversation, and features like InjectAgentMessage and multi-agent handoff suggest some event-driven behavior, but this is developer-defined logic (via function calling code) rather than a declarative rules engine for automatically triggering actions on arbitrary events. missing for 10: a documented rules/trigger engine (if-this-then-that style), event subscription system, or automation workflow builder distinct from manual function-calling code.
- [claimed-docs] “In the context of Deepgram Voice Agents, function calling enables your agent to perform tasks during a live conversation.”
- [claimed-docs] “Multi-Agent Architecture: orchestrate multiple specialized agents that hand off based on context, intent, or domain.”
- [claimed-docs] “Inject agent message | Mid-call | InjectAgentMessage | Makes the agent speak a specific line”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnBlandnone0/10Bland's docs cover batch calls, pathways, webhooks, and API integrations, but nothing describes scheduling recurring jobs or workflows (e.g., cron-like triggers for calls or campaigns) — batch calls are one-off CSV uploads, not recurring schedules.
- [claimed-docs] “Batch calls let you initiate high-volume call campaigns by uploading a list of recipients via CSV.”
- [claimed-docs] “Dispatch AI phone calls to call customers, leads, and to streamline operations.”
ai-native userVersion, review, and roll back my automations
weight 1 · round to BlandBland pathways support draft/staging/production versioning, A/B testing new releases against live production, and canary/staged rollout with adoption control (bland-docs-2, bland-docs-14, bland-docs-19, bland-docs-21, bland-docs-29, bland-docs-31), plus a testbed and evals for reviewing behavior before shipping (bland-docs-7, bland-docs-8, bland-docs-22, bland-docs-28). However, there is no explicit documentation of an automated 'rollback' mechanism to revert a live pathway/release to a prior version — only forward-adoption and canary controls are described. Missing for 10: explicit rollback/revert-to-previous-version capability, version history/diff view, and independent confirmation of rollback in practice.
- [claimed-docs] “You can also promote a version to staging to test it before it goes live, or send an individual call against a specific”
- [claimed-docs] “You choose when to adopt a new release. Your infrastructure stays on the version you've selected until you decide to move forward.”
- [claimed-docs] “When you edit a pathway, you are working on a draft. Live calls are not affected. They keep using the published production version.”
- [claimed-docs] “This is how you A/B test a new agent release against your live production version, with real calls, before committing to a full rollout.”
- [claimed-docs] “Bland supports canary deployments — a way to run a new release on a separate set of containers alongside your production infrastructure and …”
- [claimed-docs] “You choose when to adopt a new release... Bland supports canary deployments — a way to run a new release on a separate set of containers alo…”
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges.”
- [claimed-docs] “The testbed lets you take any call ... isolate a specific node interaction, edit the prompt, and run it multiple times to see how the output…”
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges. You define eval agents, each of which grades one dimension of a call”
- [claimed-docs] “The testbed lets you take any call — whether it's a historical call from call logs or a test chat from the pathway editor — isolate a specif…”
Deepgram's Reusable Agent Configurations let you persist a named agent config and reference it by UUID, and support A/B testing two configs in parallel, which is adjacent to versioning, but there is no documented version history, diff/review workflow, or explicit rollback mechanism. missing for 10: version history tracking, review/approval workflow, explicit rollback capability, changelog or diffing between config versions.
- [claimed-docs] “Reusable Agent Configurations allow you to define and persist the agent block of your Settings message using the Deepgram API. Once created,…”
- [claimed-docs] “A/B testing voices or prompts — Run two configurations in parallel and measure conversion, CSAT, or containment rate to pick a winner—no cod…”
Compliance trust — stories about compliance trust in this arenaCompliance trust
Stories about compliance trust in this arena
Compliance
founderMeet call-recording consent and disclosure obligations with per-call recording controls and configurable data retention
weight 2 · round to Deepgram Voice AgentBlandnone0/10The evidence pack contains no mention of call recording consent/disclosure features, per-call recording toggles, or configurable data retention policies anywhere in Bland's docs; while this is a fair compliance axis for a voice AI platform, nothing in the pack substantiates it.
Deepgram documents general data-privacy controls (per-request opt-out from retention via mip_opt_out, EU-region processing endpoint) that touch on data retention/residency, but there is no explicit documentation of per-call recording toggles, consent/disclosure workflows, or configurable retention windows tied to call recordings specifically. Missing for 10: explicit per-call recording enable/disable controls, documented retention period configuration for stored call audio/transcripts, and consent/disclosure feature support.
- [claimed-docs] “Opt out per request with mip_opt_out=true. Opted-out requests are not retained”
- [claimed-docs] “For customers requiring data processing within the European Union, Deepgram provides an EU-specific endpoint at api.eu.deepgram.com.”
platform-engineerRun regulated workloads with HIPAA/BAA support, SOC 2, and data-residency options
weight 2 · round to Deepgram Voice AgentBlandnone0/10The evidence pack contains no mention of HIPAA, BAA, SOC 2 certification, or data-residency options anywhere in the docs or probes; only a generic tagline calling Bland an 'enterprise' platform for 'regulated' workflows without specifics. Missing for 10: HIPAA/BAA documentation, SOC 2 report or certification evidence, data-residency/region controls, and any compliance attestations.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.bland.ai/llms.txt # Bland Documentation Bland is an enterprise voice AI platform for high-volume, …”
Evidence shows EU data-residency endpoint and an opt-out from data retention/training, indicating some compliance/trust infrastructure, but there is no mention of HIPAA/BAA support or SOC 2 certification anywhere in the pack. missing for 10: HIPAA/BAA documentation, SOC 2 attestation evidence, broader regional residency options beyond EU.
- [claimed-docs] “Opt out per request with mip_opt_out=true. Opted-out requests are not retained”
- [claimed-docs] “For customers requiring data processing within the European Union, Deepgram provides an EU-specific endpoint at api.eu.deepgram.com.”
Deployment scale — stories about deployment scale in this arenaDeployment scale
Stories about deployment scale in this arena
Scale
platform-engineerSee documented concurrency limits and scale to many simultaneous calls without manual capacity begging
weight 2 · round to BlandDocs mention batch calling for high-volume campaigns and enterprise infrastructure controls (canary releases, staged rollout), implying some capacity for scale, but there is no documented concurrency limit, rate ceiling, or auto-scaling guarantee, and no evidence that capacity increases don't require contacting sales/support. Missing for 10: explicit concurrent-call limits, auto-scaling documentation, and evidence that scaling doesn't require manual requests to Bland.
- [claimed-docs] “Batch calls let you initiate high-volume call campaigns by uploading a list of recipients via CSV.”
- [claimed-docs] “Bland supports canary deployments — a way to run a new release on a separate set of containers alongside your production infrastructure and …”
- [claimed-docs] “You choose when to adopt a new release... Bland supports canary deployments — a way to run a new release on a separate set of containers alo…”
Deepgram Voice Agentnone0/10No evidence pack item mentions concurrency limits, rate limits, per-account call caps, scaling guidance, or capacity request processes for the Voice Agent API; the docs cover architecture, features, and integrations but nothing about scale/concurrency documentation.
Self host
platform-engineerSelf-host the voice agent runtime from open-source code on my own infrastructure
weight 3 · round drawnBlandnone0/10Bland is presented throughout as a hosted enterprise SaaS platform (managed infrastructure, release adoption controls, canary deployments on Bland's own containers) with no mention of open-source code or a self-hostable runtime; a community post even shows a user asking for an open-source alternative because Bland itself isn't one.
- [claimed-docs] “You choose when to adopt a new release. Your infrastructure stays on the version you've selected until you decide to move forward.”
- [claimed-docs] “Bland supports canary deployments — a way to run a new release on a separate set of containers alongside your production infrastructure and …”
- [community] “I want to experiment with building my own phone agent. Currently experimented with bland.ai but it gets expensive. Any open source alternati…”
Deepgram Voice Agentnone0/10Deepgram Voice Agent is a hosted, cloud-only API accessed via WebSocket; nothing in the evidence indicates open-source runtime code that can be self-hosted on customer infrastructure. All references point to Deepgram-hosted endpoints (api.deepgram.com, api.eu.deepgram.com) and a CLI/SDK for calling the cloud service, not deploying the runtime itself.
- [claimed-docs] “Deepgram's Voice Agent API collapses that stack into a single, unified API. You open one WebSocket connection, send audio in, and receive au…”
- [claimed-docs] “For customers requiring data processing within the European Union, Deepgram provides an EU-specific endpoint at api.eu.deepgram.com.”
- [claimed-docs] “Twilio streams the call audio to your server, and your server bridges that audio to the Deepgram Voice Agent API, a single WebSocket that ru…”
Latency turntaking — stories about latency turntaking in this arenaLatency turntaking
Stories about latency turntaking in this arena
Latency
platform-engineerSee documented end-to-end voice latency numbers or tuning guidance backing the platform's speed claims
weight 3 · round drawnBlandnone0/10No evidence pack items mention latency numbers, benchmarks, or tuning guidance for end-to-end voice response time; documentation covers pathways, SIP, MCP, CLI, and enterprise features but nothing about speed/latency metrics or optimization guidance.
Deepgram Voice Agentnone0/10The evidence pack covers architecture, features (barge-in, telephony, function calling, multi-agent), and CLI/SDK tooling, but contains no documented latency numbers (e.g., ms end-to-end) or tuning guidance for reducing turn-taking latency. missing for 10: quantified latency benchmarks, latency tuning/configuration guidance, any performance dashboard or whitepaper on speed claims.
- [claimed-docs] “Deepgram's Voice Agent API collapses that stack into a single, unified API. You open one WebSocket connection, send audio in, and receive au…”
- [claimed-docs] “That includes barge-in, the ability to talk over the agent and have it stop instantly.”
- [claimed-docs] “Twilio streams the call audio to your server, and your server bridges that audio to the Deepgram Voice Agent API, a single WebSocket that ru…”
Turn taking
developerRely on the agent to handle interruptions (barge-in) gracefully — stopping speech, updating context, and recovering the turn
weight 3 · round to Deepgram Voice AgentBlandnone0/10The evidence pack covers pathways, webhooks, batch calls, evals, MCP/CLI integrations, and infrastructure features, but contains no mention of barge-in, interruption handling, stopping TTS mid-utterance, or turn recovery logic — a core voice-agent capability that would be a fair and expected axis for this product type. missing for 10: any documentation or claim about detecting user interruptions, halting agent speech, updating context after a barge-in, and resuming/recovering the conversational turn.
Docs explicitly claim barge-in support where users can talk over the agent and it stops instantly, plus mid-call context tools like InjectAgentMessage for updating conversation state. However, evidence lacks detail on how turn recovery/context updating works technically after interruption, and there's no independent/hands-on corroboration of graceful recovery in practice. missing for 10: technical details on context-state recovery post-interruption, independent verification of barge-in reliability, edge-case handling (e.g., rapid interruptions, latency of stop).
- [claimed-docs] “That includes barge-in, the ability to talk over the agent and have it stop instantly.”
- [claimed-docs] “Inject agent message | Mid-call | InjectAgentMessage | Makes the agent speak a specific line”
- [claimed-docs] “Deepgram's Voice Agent API collapses that stack into a single, unified API. You open one WebSocket connection, send audio in, and receive au…”
developerEnable noise suppression or audio filtering so the agent stays coherent on noisy real-world calls
weight 1 · round drawnBlandnone0/10No evidence pack item mentions noise suppression, audio filtering, or handling of noisy real-world call environments; documentation covers pathways, integrations, MCP, CLI, SIP, and enterprise release features but nothing about audio quality/noise handling.
developerUse model-based end-of-turn detection beyond simple VAD silence timeouts so the agent doesn't talk over slow speakers
weight 2 · round drawnBlandnone0/10The evidence pack contains no mention of turn-taking, end-of-turn detection, VAD, or interruption handling mechanisms of any kind — nothing addresses how Bland decides when a speaker has finished talking. This is a fair and applicable axis for a voice AI platform, but no capability is documented; missing for 10: any mention of end-of-turn/turn-taking model, VAD configuration, or handling of slow speakers/pauses.
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to BlandBland's docs show extensive programmatic control mirroring UI features: pathway creation/versioning, testbed, evals, batch calls, webhooks, SIP/phone number management, and a CLI/MCP server that explicitly lets users 'manage your entire Bland account from the terminal' and perform the same actions (calls, pathways, agents, analytics) as the UI. This breadth strongly supports API parity, though there's no explicit first-party statement guaranteeing 100% feature parity and no discoverable OpenAPI spec (all candidate URLs 404), so full parity isn't independently confirmed. Missing for 10: an explicit parity guarantee/documentation and a machine-readable OpenAPI spec, plus independent hands-on confirmation that every UI action has an API equivalent.
- [claimed-docs] “See the Pathways API reference to create and manage pathways programmatically.”
- [claimed-docs] “Manage your entire Bland account from the terminal: make calls, build and test pathways, configure phone numbers, and more.”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The testbed lets you take any call ... isolate a specific node interaction, edit the prompt, and run it multiple times to see how the output…”
- [claimed-docs] “Batch calls let you initiate high-volume call campaigns by uploading a list of recipients via CSV.”
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges.”
- [probe] “official CLI documented at https://docs.bland.ai/sdks/cli”
- [probe] “PROBE runtime (recorded 2026-09-05): `npx -y bland-cli --version` printed `0.6.2` keylessly — the official npm CLI (bland-cli, with dev term…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.bland.ai/openapi.json, https://docs.bland.ai/swagger.json, https://docs.bland.ai/api/op…”
Deepgram is fundamentally API-first — the Voice Agent is a WebSocket API with full configuration (prompting, function calling, multi-agent, telephony, reusable configs) exposed programmatically, and even the CLI/MCP server let AI-native users manage things from the terminal or via agentic tools rather than a GUI. However, evidence doesn't show a full-featured UI to compare against (e.g., a dashboard/console) nor confirm that every console feature (like A/B testing dashboards, analytics views) has a documented API equivalent. missing for 10: explicit mapping of console/UI-only features (analytics dashboards, A/B test result views) to API endpoints, and confirmation no UI-exclusive functionality exists.
- [claimed-docs] “Deepgram's Voice Agent API collapses that stack into a single, unified API. You open one WebSocket connection, send audio in, and receive au…”
- [claimed-docs] “Reusable Agent Configurations allow you to define and persist the agent block of your Settings message using the Deepgram API. Once created,…”
- [claimed-docs] “The dg CLI lets you transcribe files, stream live audio, synthesize speech, analyze text, and manage your Deepgram account from the terminal…”
- [claimed-docs] “The dg CLI includes a built-in MCP (Model Context Protocol) server that gives AI coding tools direct access to Deepgram APIs.”
- [claimed-docs] “A/B testing voices or prompts — Run two configurations in parallel and measure conversion, CSAT, or containment rate to pick a winner—no cod…”
- [probe] “PROBE openapi: HTTP 200 at https://developers.deepgram.com/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://developers.deepgram.com/developer-tools/agentic-tools”
- [probe] “official CLI documented at https://developers.deepgram.com/developer-tools/cli/getting-started”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnBlandnone0/10No evidence of a data export feature or open-format export of account data (pathways, call logs, memories, etc.); the docs cover CLI, MCP, and SDK integrations but nothing about exporting user data for portability/exit.
Deepgram Voice Agentnone0/10No evidence describes any data export, account data portability, or open-format export/deletion workflow letting a user take their data and leave; docs cover retention opt-out and EU processing but not export tooling. missing for 10: data export mechanism, open-format export documentation, account closure/data portability guarantees.
ai-native userRead the product's source under an open license
weight 2 · round drawnBlandnone0/10Bland is a closed, commercial SaaS voice AI platform; there is no evidence of any open-source license or public source code repository. A community comment explicitly asks for an open-source alternative, implying Bland itself is not open source. This is an applicable axis (a product could publish open-source components) but no evidence supports it.
- [community] “I want to experiment with building my own phone agent. Currently experimented with bland.ai but it gets expensive. Any open source alternati…”
Deepgram Voice Agentnone0/10Deepgram Voice Agent is a proprietary cloud API/SDK product; no evidence anywhere in the pack points to an open-source license or public source repository for the core Voice Agent service. Only API docs, CLI, and SDK usage are documented, none of which imply open-licensed source availability.
ai-native userSelf-host the core product
weight 3 · round drawnBlandnone0/10Bland is documented as a hosted enterprise voice AI platform (call dispatch, pathways, SIP, MCP, CLI) with no mention of an on-prem/self-hosted deployment option; 'enterprise' release controls (docs-14, docs-29, docs-31) only govern version adoption timing on Bland's own infrastructure, not customer self-hosting. A community post explicitly looks for an open-source self-hostable alternative because Bland itself doesn't offer this.
- [claimed-docs] “You choose when to adopt a new release. Your infrastructure stays on the version you've selected until you decide to move forward.”
- [claimed-docs] “Bland supports canary deployments — a way to run a new release on a separate set of containers alongside your production infrastructure and …”
- [claimed-docs] “You choose when to adopt a new release... Bland supports canary deployments — a way to run a new release on a separate set of containers alo…”
- [community] “I want to experiment with building my own phone agent. Currently experimented with bland.ai but it gets expensive. Any open source alternati…”
Deepgram Voice Agentnone0/10Deepgram Voice Agent is a cloud API/SaaS product; all evidence points to hosted WebSocket endpoints, EU regional endpoints, and cloud-based configuration — there is no mention of a self-hostable or on-premises deployment package for the core voice agent model/inference stack. missing for 10: any self-hosting/on-prem deployment option, downloadable model weights or container, docs on running the core service outside Deepgram's cloud.
- [claimed-docs] “Deepgram's Voice Agent API collapses that stack into a single, unified API. You open one WebSocket connection, send audio in, and receive au…”
- [claimed-docs] “For customers requiring data processing within the European Union, Deepgram provides an EU-specific endpoint at api.eu.deepgram.com.”
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans
Plan structure and value — what each tier costs and what it unlocks
Pricing
founderSee published per-minute or usage pricing and estimate cost per call before committing
weight 2 · round drawnBlandnone0/10No evidence pack item shows published per-minute or usage pricing, a pricing page, or any cost calculator; the only pricing-adjacent mention is a community complaint that Bland 'gets expensive' with no figures. Missing for 10: published price list, per-minute rate documentation, cost calculator or estimator tool.
- [community] “I want to experiment with building my own phone agent. Currently experimented with bland.ai but it gets expensive. Any open source alternati…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round to Deepgram Voice AgentBlandnone0/10No evidence in the pack mentions data residency, regional hosting options, or geographic storage controls for Bland; enterprise/infra docs discuss release versioning and SIP/canary deployments but not region selection. Missing for 10: any mention of data residency options, region-specific hosting, or compliance-driven storage location controls.
Deepgram documents an EU-specific endpoint (api.eu.deepgram.com) for customers requiring EU data processing, and a per-request opt-out for model improvement data retention, showing some regional/data-handling control. However, this is limited to EU vs. default (US) with no evidence of broader region selection (e.g., APAC, other jurisdictions) or a general residency configuration option across the platform. Missing for 10: documented list of all available regions, self-serve region selection in dashboard/API config, and independent confirmation of residency guarantees beyond docs.
- [claimed-docs] “For customers requiring data processing within the European Union, Deepgram provides an EU-specific endpoint at api.eu.deepgram.com.”
- [claimed-docs] “Opt out per request with mip_opt_out=true. Opted-out requests are not retained”
ai-native userPrevent my data from being used to train AI models
weight 3 · round to Deepgram Voice AgentBlandnone0/10No evidence in the pack addresses data-training opt-out or AI-training privacy policies for Bland; nothing about training-data usage or opt-out controls is mentioned across any of the docs or probes.
Deepgram documents a per-request opt-out (mip_opt_out=true) from its Model Improvement Program, with opted-out requests not retained, directly addressing training-data use. However, the evidence only shows a per-request flag rather than an account-wide default-off setting, and there's no independent verification that opt-out requests are truly excluded from training. Missing for 10: account/org-level opt-out default, third-party audit or independent confirmation of non-training use, and clarity on default behavior when the flag is omitted.
- [claimed-docs] “Opt out per request with mip_opt_out=true. Opted-out requests are not retained”
ai-native userControl data retention and deletion
weight 2 · round to Deepgram Voice AgentBlandnone0/10No evidence pack items address data retention policies, data deletion controls, or privacy/compliance settings for call recordings, transcripts, or memory data. This axis clearly applies to an enterprise voice AI platform handling call data, but nothing in the evidence documents retention periods, deletion APIs, or GDPR/CCPA-style data controls. Missing for 10: retention policy docs, data deletion API/endpoint, compliance certifications, memory/data purge mechanism.
Deepgram documents a per-request opt-out (mip_opt_out=true) that prevents retention, and references data-privacy compliance including an EU-specific endpoint, giving users some retention control. However, there is no documented self-service deletion mechanism for already-retained data, no stated retention periods, and no dashboard/API for managing or purging stored voice data. Missing for 10: explicit data deletion API/console, documented retention duration policy, and confirmation of deletion for non-opted-out data.
- [claimed-docs] “Opt out per request with mip_opt_out=true. Opted-out requests are not retained”
- [claimed-docs] “For customers requiring data processing within the European Union, Deepgram provides an EU-specific endpoint at api.eu.deepgram.com.”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round to Deepgram Voice AgentBlandnone0/10No evidence pack items mention telemetry, analytics opt-out, or usage-tracking controls for Bland's own platform; this is a fair question for an enterprise SaaS product but is simply unaddressed in the evidence.
Deepgram documents an opt-out mechanism (mip_opt_out=true) for model improvement/data retention on a per-request basis, which is a form of telemetry/usage-data opt-out, but this is narrowly scoped to training data retention rather than general telemetry/usage tracking (e.g., analytics, product usage metrics). Missing for 10: documentation of a broader telemetry/usage-tracking opt-out setting, confirmation this covers all usage data beyond model-improvement retention, and independent verification that opting out has no side effects.
- [claimed-docs] “Opt out per request with mip_opt_out=true. Opted-out requests are not retained”
Telephony — stories about telephony in this arenaTelephony
Stories about telephony in this arena
Call control
developerEscalate a live call to a human with warm or blind transfer, passing context along
weight 2 · round drawnBlandnone0/10The evidence pack covers pathways, webhooks, SIP, MCP, CLI, and other Bland features, but contains no mention of call transfer (warm or blind) or handing off a live call to a human agent with context. This is a standard telephony capability that could plausibly be documented, so absence of evidence yields 'none' rather than 'na'.
Deepgram Voice Agentnone0/10Evidence covers telephony connectivity, function calling, multi-agent handoff between AI agents, and mid-call message injection, but nothing documents a warm/blind transfer to a human agent (e.g., SIP REFER, call transfer function, or context handoff to a live operator).
developerMy agent can send DTMF keypresses, navigate IVR menus, and detect or leave voicemail
weight 1 · round drawnBlandnone0/10The evidence pack covers pathways, SIP, webhooks, evals, and MCP/CLI tooling, but nowhere mentions DTMF keypress sending, IVR menu navigation, or voicemail detection/leaving — capabilities that are plausible for a voice telephony platform but are simply undocumented here.
Campaigns
founderRun batch outbound call campaigns with scheduling and throughput controls
weight 2 · round to BlandBland's docs explicitly describe batch calls for uploading CSV recipient lists to run high-volume outbound campaigns, backed by scheduling/throughput-related infrastructure like SIP integration, phone number management, and analytics/evals to monitor campaign performance. Missing for 10: explicit documentation of scheduling controls (e.g., call windows/timing) and rate-limiting/throughput knobs specifically, plus independent hands-on verification of batch campaign behavior at scale.
- [claimed-docs] “Batch calls let you initiate high-volume call campaigns by uploading a list of recipients via CSV.”
- [claimed-docs] “Dispatch AI phone calls to call customers, leads, and to streamline operations.”
- [claimed-docs] “Bland supports inbound and outbound SIP. Point calls from your carrier or PBX at Bland to be answered by an agent, or have Bland place calls…”
- [claimed-docs] “Number porting to bring existing numbers to Bland”
Deepgram Voice Agentnone0/10Deepgram's docs confirm outbound telephony connectivity (docs-5, docs-18) and per-call features like barge-in and prompting, but there is no mention of campaign-level batch dialing, call scheduling, or throughput/rate controls for outbound campaigns — this is a real-time conversation API, not a dialer/campaign manager.
- [claimed-docs] “Telephony: connect voice agents to phone networks for inbound and outbound calls.”
- [claimed-docs] “Twilio streams the call audio to your server, and your server bridges that audio to the Deepgram Voice Agent API, a single WebSocket that ru…”
Numbers
developerProvision phone numbers and run both inbound and outbound calls through the platform's API
weight 3 · round to BlandBland's docs explicitly document creating/managing inbound phone numbers, outbound call dispatch via API, bringing your own Twilio numbers, and SIP for both inbound/outbound, all programmatically accessible, plus a CLI/MCP that manage phone numbers and calls end-to-end. Missing for 10: no explicit REST API reference/OpenAPI spec confirmed (probe shows openapi.json 404s) and no independent hands-on developer report of a full provision+call round trip.
- [claimed-docs] “Dispatch AI phone calls to call customers, leads, and to streamline operations.”
- [claimed-docs] “Create inbound phone numbers for customer support, etc.”
- [claimed-docs] “Users can connect their own Twilio account to Bland, easily bring over your existing phone numbers to use within the platform.”
- [claimed-docs] “Number porting to bring existing numbers to Bland”
- [claimed-docs] “Bland supports inbound and outbound SIP. Point calls from your carrier or PBX at Bland to be answered by an agent, or have Bland place calls…”
- [claimed-docs] “Manage your entire Bland account from the terminal: make calls, build and test pathways, configure phone numbers, and more.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.bland.ai/openapi.json, https://docs.bland.ai/swagger.json, https://docs.bland.ai/api/op…”
Docs confirm Deepgram Voice Agent supports inbound/outbound calls and telephony integration (e.g., via Twilio bridging audio to a single WebSocket), but there is no evidence Deepgram itself provisions or manages phone numbers—developers must bring their own Twilio account/number and build a bridging server. Missing for 10: native phone-number provisioning API, first-party telephony number management, and evidence of outbound call initiation directly through Deepgram's API without a third-party carrier.
- [claimed-docs] “Telephony: connect voice agents to phone networks for inbound and outbound calls.”
- [claimed-docs] “Twilio streams the call audio to your server, and your server bridges that audio to the Deepgram Voice Agent API, a single WebSocket that ru…”
- [claimed-docs] “That includes barge-in, the ability to talk over the agent and have it stop instantly.”
Sip
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 BlandBland's docs explicitly document inbound/outbound SIP trunking to connect a customer's own carrier or PBX, plus number porting, and separately support connecting an existing Twilio account/numbers. Missing for 10: no mention of Telnyx import specifically and no independent/hands-on validation of SIP setup success.
- [claimed-docs] “Bland supports inbound and outbound SIP. Point calls from your carrier or PBX at Bland to be answered by an agent, or have Bland place calls…”
- [claimed-docs] “Number porting to bring existing numbers to Bland”
- [claimed-docs] “Users can connect their own Twilio account to Bland, easily bring over your existing phone numbers to use within the platform.”
Deepgram Voice Agentnone0/10Evidence only documents a generic WebSocket bridge pattern for Twilio (docs-18, docs-8) and a general 'Telephony' feature bullet (docs-5), but there is no mention of SIP trunking, PBX connectivity, or Telnyx number import — the specific mechanisms a platform engineer would need to bring their own carrier.
- [claimed-docs] “Telephony: connect voice agents to phone networks for inbound and outbound calls.”
- [claimed-docs] “Twilio streams the call audio to your server, and your server bridges that audio to the Deepgram Voice Agent API, a single WebSocket that ru…”
- [claimed-docs] “That includes barge-in, the ability to talk over the agent and have it stop instantly.”
Testing analytics — stories about testing analytics in this arenaTesting analytics
Stories about testing analytics in this arena
Analytics
ai-native userThe platform's AI reviews my calls for me — scoring quality, flagging failures, and analyzing resolution automatically
weight 2 · round to BlandBland's Evals feature explicitly lets users define LLM-judge agents that grade calls on custom dimensions (quality, resolution, etc.), and the Testbed lets you replay and analyze specific call nodes to spot failures — directly matching automated call review/scoring. However, this requires the user to configure eval criteria rather than being a fully out-of-the-box automatic analysis, and there's no evidence of a pre-built default 'failure flagging' report. Missing for 10: evidence of fully automatic, no-setup call scoring/dashboard, and independent/hands-on validation of eval accuracy.
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges.”
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges. You define eval agents, each of which grades one dimension of a call”
- [claimed-docs] “The testbed lets you take any call ... isolate a specific node interaction, edit the prompt, and run it multiple times to see how the output…”
- [claimed-docs] “The testbed lets you take any call — whether it's a historical call from call logs or a test chat from the pathway editor — isolate a specif…”
Deepgram Voice Agentnone0/10The evidence pack covers Deepgram Voice Agent's real-time conversation infrastructure (STT/TTS, function calling, telephony, prompting, A/B testing of voices/prompts) but contains no mention of post-call AI review, automated quality scoring, failure flagging, or resolution analysis of completed calls.
founderSee call analytics — success rates, durations, outcomes, sentiment — in dashboards without building my own
weight 2 · round to BlandEvidence confirms Bland has an analytics layer (MCP server can 'query analytics') and quality-grading tools like Evals (LLM judges scoring call dimensions) and a testbed for reviewing call interactions, implying some built-in metrics exist. However, there is no direct evidence of an actual dashboard UI showing success rates, call durations, outcomes, or sentiment trends over time — analytics access shown is via MCP/API query rather than a visual dashboard. Missing for 10: screenshots or docs of a native analytics dashboard, explicit mention of success-rate/duration/sentiment metrics, and independent confirmation the dashboard requires no custom building.
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges. You define eval agents, each of which grades one dimension of a call”
- [claimed-docs] “The testbed lets you take any call — whether it's a historical call from call logs or a test chat from the pathway editor — isolate a specif…”
- [probe] “official MCP server documented at https://docs.bland.ai/integrations/mcp/overview”
Deepgram Voice Agentnone0/10Deepgram is a developer API/infrastructure product; evidence shows mentions of A/B testing metrics (conversion, CSAT, containment rate) as data points but no evidence of an actual built-in dashboard for call analytics, success rates, durations, sentiment, or outcomes that founders can view without building their own.
- [claimed-docs] “A/B testing voices or prompts — Run two configurations in parallel and measure conversion, CSAT, or containment rate to pick a winner—no cod…”
Monitoring
platform-engineerMonitor live calls in production and get alerts when agents misbehave or error rates spike
weight 1 · round to BlandBland provides post-call webhooks, evals with LLM judges, and an MCP integration that can 'query analytics' — giving some after-the-fact quality/analytics visibility — but there is no documented live-call monitoring dashboard, real-time alerting, or error-rate-spike notification system in the evidence pack. Missing for 10: live/real-time call monitoring UI, configurable alert thresholds, error-rate spike detection/paging, independent confirmation these exist in production.
- [claimed-docs] “Post-call webhooks are HTTP notifications that Bland AI automatically sends to your server after a phone call completes.”
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges.”
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges. You define eval agents, each of which grades one dimension of a call”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The testbed lets you take any call — whether it's a historical call from call logs or a test chat from the pathway editor — isolate a specif…”
Testing
developerTest agents with simulated conversations or evals before putting them on real phone calls
weight 2 · round to BlandBland provides explicit pre-production testing tools: Evals (LLM-judge grading of call quality), the Testbed (replay/edit/re-run node interactions on historical or test chats), staging promotion and draft-vs-production pathway separation, and canary/A/B rollout testing against real calls before full deployment. Together these let a developer simulate conversations and grade agent behavior before real phone calls go live. missing for 10: no independent/hands-on evidence of eval accuracy or testbed usage from outside vendor docs, and no explicit description of a pure text-based conversation simulator separate from testbed/staging.
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges.”
- [claimed-docs] “The testbed lets you take any call ... isolate a specific node interaction, edit the prompt, and run it multiple times to see how the output…”
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges. You define eval agents, each of which grades one dimension of a call”
- [claimed-docs] “The testbed lets you take any call — whether it's a historical call from call logs or a test chat from the pathway editor — isolate a specif…”
- [claimed-docs] “You can also promote a version to staging to test it before it goes live, or send an individual call against a specific”
- [claimed-docs] “When you edit a pathway, you are working on a draft. Live calls are not affected. They keep using the published production version.”
- [claimed-docs] “This is how you A/B test a new agent release against your live production version, with real calls, before committing to a full rollout.”
- [claimed-docs] “Bland supports canary deployments — a way to run a new release on a separate set of containers alongside your production infrastructure and …”
Deepgram Voice Agentnone0/10The evidence covers live-call features (function calling, prompting, telephony, A/B testing of live configs) but nothing describes a simulated-conversation or eval framework for pre-production testing of agents before real phone calls. Missing for 10: any documentation of a test/sandbox mode, conversation simulation tool, or eval harness for agents.
- [claimed-docs] “A/B testing voices or prompts — Run two configurations in parallel and measure conversion, CSAT, or containment rate to pick a winner—no cod…”
- [claimed-docs] “Reusable Agent Configurations allow you to define and persist the agent block of your Settings message using the Deepgram API. Once created,…”
Tools function calling — stories about tools function calling in this arenaTools function calling
Stories about tools function calling in this arena
Post call
developerExtract structured data from every call — outcomes, entities, dispositions — delivered via API or webhook after the call
weight 2 · round to BlandBland documents post-call webhooks that automatically deliver call data to a developer's server after each call, and evals let you grade/classify calls (dispositions) via LLM judges — both align with the API/webhook delivery and outcome-tagging parts of the story. However, there's no explicit documentation of structured entity extraction (e.g., named fields like names, dates, custom entities) as a distinct capability, nor a described webhook payload schema. Missing for 10: explicit entity-extraction feature docs, sample webhook payload showing structured outcome/entity/disposition fields, and independent confirmation of the data delivered.
- [claimed-docs] “Post-call webhooks are HTTP notifications that Bland AI automatically sends to your server after a phone call completes.”
- [claimed-docs] “Evals let you measure the quality of your calls with LLM judges. You define eval agents, each of which grades one dimension of a call”
- [claimed-docs] “Give your agent instructions on how it should respond at specific points of the conversation. Choose between prompting or fixed sentences. E…”
Deepgram Voice Agentnone0/10The evidence pack covers live function calling during a call and various agent configuration/telephony features, but there is no mention of post-call structured data extraction (summaries, entities, dispositions) or webhook delivery of such analytics after a call ends.
Tools
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 drawnBlandnone0/10Bland ships an MCP *server* so coding agents can control the Bland account (docs-11/20/27, probe-3/probe-rt-2), which is the opposite role from what the story asks — the voice agent itself acting as an MCP *client* that plugs in external MCP servers as tool sources mid-call. Tool/function calling is documented only via custom HTTP API integrations (bland-docs-4, bland-docs-25), with no mention of the agent consuming MCP servers as a toolset source during calls.
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [claimed-docs] “The Bland MCP server lets AI coding agents work with your Bland account through natural language: place and inspect calls, build and validat…”
- [probe] “official MCP server documented at https://docs.bland.ai/integrations/mcp/overview”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the hosted MCP endpoint https://api.bland.ai/v1/mcp returned HTTP 4…”
- [claimed-docs] “The API integration lets you connect your AI agent to any HTTP endpoint.”
- [claimed-docs] “Connect external APIs and take live actions during phone calls.”
Deepgram Voice Agentnone0/10Evidence confirms mid-call function calling exists for the Voice Agent (deepgram-docs-2) but only documents an MCP *server* built into the CLI that lets coding tools access Deepgram APIs (deepgram-docs-13, deepgram-probe-4) — this is the reverse direction, not the Voice Agent acting as an MCP client to pull in external toolsets mid-call. No evidence shows the Voice Agent itself can connect to MCP servers as a tool source.
- [claimed-docs] “In the context of Deepgram Voice Agents, function calling enables your agent to perform tasks during a live conversation.”
- [claimed-docs] “The dg CLI includes a built-in MCP (Model Context Protocol) server that gives AI coding tools direct access to Deepgram APIs.”
- [probe] “official MCP server documented at https://developers.deepgram.com/developer-tools/agentic-tools”
developerMy agent can call external APIs and custom functions mid-conversation and speak the result without awkward dead air
weight 3 · round drawnBland's pathway/tools docs confirm agents can call external APIs and execute webhooks mid-conversation (bland-docs-4, bland-docs-25, bland-docs-30), which supports live function calling during a call. However, no evidence describes mechanisms for avoiding dead air (e.g., filler speech, streaming partial responses) while waiting on API results. missing for 10: explicit documentation of latency-masking/filler-speech behavior during API calls, and independent/hands-on confirmation of smooth conversational flow.
- [claimed-docs] “The API integration lets you connect your AI agent to any HTTP endpoint.”
- [claimed-docs] “Connect external APIs and take live actions during phone calls.”
- [claimed-docs] “Give your agent instructions on how it should respond at specific points of the conversation. Choose between prompting or fixed sentences. E…”
- [claimed-docs] “Conversational pathways are our new way of prompting Bland that has led to major breakthroughs in realism. Give your agent instructions on h…”
Docs confirm function calling is a supported feature for performing tasks mid-conversation (deepgram-docs-2), and the agent architecture is a single low-latency WebSocket for audio in/out (deepgram-docs-1) with barge-in and inject-message features (deepgram-docs-8, deepgram-docs-11) suggesting attention to latency/dead-air. However there's no explicit documentation or example describing how function-call latency is masked (e.g., filler speech, streaming partial results) while awaiting an API response. Missing for 10: concrete guidance/examples on avoiding dead air during function execution, sample code showing async function calls with the agent speaking a holding phrase, and independent/hands-on verification of smooth latency handling.
- [claimed-docs] “In the context of Deepgram Voice Agents, function calling enables your agent to perform tasks during a live conversation.”
- [claimed-docs] “Deepgram's Voice Agent API collapses that stack into a single, unified API. You open one WebSocket connection, send audio in, and receive au…”
- [claimed-docs] “That includes barge-in, the ability to talk over the agent and have it stop instantly.”
- [claimed-docs] “Inject agent message | Mid-call | InjectAgentMessage | Makes the agent speak a specific line”
Transcription recording — stories about transcription recording in this arenaTranscription recording
Stories about transcription recording in this arena
Recording
platform-engineerRetrieve full call recordings and transcripts programmatically for every call
weight 2 · round drawnBlandnone0/10No evidence pack item explicitly documents an API or endpoint for retrieving full call recordings or transcripts programmatically; references to call logs (testbed) and post-call webhooks hint at underlying data but never confirm a recording/transcript retrieval capability.
Deepgram Voice Agentnone0/10The evidence pack covers Voice Agent architecture, function calling, telephony bridging, LLM providers, and data privacy opt-outs, but nowhere describes an API or mechanism to retrieve full call recordings or persisted transcripts after a call ends. No endpoint, storage feature, or retrieval workflow is documented for this specific capability.
Transcription
developerGet accurate real-time transcription with control over the STT provider, language models, or key terms
weight 2 · round to Deepgram Voice AgentBlandnone0/10Bland is a phone-call AI platform where transcription accuracy is clearly relevant, but the evidence pack contains no mention of STT provider selection, language model choice for transcription, or key-term/vocabulary boosting features. missing for 10: STT provider selection, transcription accuracy documentation, custom key terms/vocabulary support, language model configuration for transcription.
Docs confirm real-time transcription via the unified WebSocket API, selectable LLM providers (docs-9), and multilingual STT/TTS model choices (docs-10), giving developers meaningful control over STT and LLM models. However, there is no evidence of 'key terms' or keyword-boosting controls specific to the Voice Agent's transcription pipeline. Missing for 10: explicit key-term/keyword-boost configuration support, independent benchmarking of transcription accuracy.
- [claimed-docs] “Deepgram's Voice Agent API collapses that stack into a single, unified API. You open one WebSocket connection, send audio in, and receive au…”
- [claimed-docs] “Supported LLM providers | Parameter | open_ai | anthropic | aws_bedrock | google | groq | nvidia”
- [claimed-docs] “A multilingual voice agent has two model decisions: which STT model transcribes the user, and which TTS model speaks the agent.”
Voices tts — stories about voices tts in this arenaVoices tts
Stories about voices tts in this arena
Voices
founderClone a custom brand voice and use it for my agents, with a documented consent process
weight 2 · round to BlandBland documents voice cloning itself (a ~10-second clean sample sets the quality ceiling) which supports the 'clone a custom brand voice' half of the story, but no evidence describes a documented consent process, verification, or authorization requirement for cloning someone's voice. missing for 10: documented consent/verification workflow for voice cloning, legal/compliance guidance on brand-voice rights, independent confirmation of the cloning feature's fidelity.
- [claimed-docs] “A clone needs one clean sample of about ten seconds. Quality of the sample sets the ceiling on quality of the voice”
developerChoose from a broad voice library or plug in multiple TTS providers to get the voice I want
weight 2 · round to BlandDocs show voice cloning support (a 10-second sample sets voice quality) but there is no evidence of a broad pre-built voice library to choose from, nor any mention of plugging in multiple third-party TTS providers. Missing for 10: documented voice library/catalog, multi-provider TTS integration, and any comparison of voice options.
- [claimed-docs] “A clone needs one clean sample of about ten seconds. Quality of the sample sets the ceiling on quality of the voice”
Deepgram Voice Agentnone0/10Evidence confirms TTS model selection exists (docs-10 references choosing a TTS model) but there is no documentation of a broad voice library or of plugging in multiple third-party TTS providers analogous to the multi-LLM-provider list (docs-9). Missing for 10: evidence of voice catalog/library breadth, evidence of multiple supported TTS providers/vendors, and any provider-switching mechanism for voice output.
- [claimed-docs] “A multilingual voice agent has two model decisions: which STT model transcribes the user, and which TTS model speaks the agent.”