Head to head · Voice agents · October 2026 research run

Bland AI API + MCP vs Deepgram Voice Agent API

Deepgram Voice Agent API scores 74.7 (BB) on agent readiness against Bland AI API + MCP's 69.5 (B), and leads in 5 of 7 scored categories. Bland AI API + MCP leads on security & auth and payments & pricing. Both do voice agents.

Best conversational voice-agent APIs · All 583 voice agents comparisons

Which one, for what

Bland AI API + MCP B

Best for Teams that want one predictable per-minute bill for outbound and inbound phone agents, and personal agents that need their own US number.

Ahead on

  • Security & auth, 79 against 71
  • Payments & pricing, 85 against 60

Watch for

No OpenAPI document

Deepgram Voice Agent API BB

Best for Developers who already run telephony (Twilio, Amazon Connect, Genesys, AudioCodes) and want a cheap managed pipeline with their choice of LLM.

Ahead on

  • Reliability, 75 against 65
  • Schema & documentation, 90 against 68
  • Agent ergonomics, 67 against 53
  • Maintenance & community, 85 against 70
  • Transparency & trust, 78 against 72

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

No phone numbers or SIP, so you bridge Twilio or another carrier yourself

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Bland AI API + MCP +25

Bland AI API + MCP 85

No x402 or L402. The headless signup endpoint answers 402 with a Machine Payments Protocol challenge settled through Stripe, but only to buy the $29.99 Agent Phone Plan, not to pay for calls (10 of 40). Per-minute rates for every self-serve plan are public, re-read on 2 November (20). The Start plan needs no card and comes with 2 credits and an inbound number (20). An agent can open an account through the headless flow, with the owner's only step being to relay a 6-digit texted code, or through a device-code flow that sends the owner to a browser (15 of 20). 10 + 20 + 20 + 15 = 65. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 10 of 40 is 2.5 of 10, and the other lines' 55 is 82.5 at 30 each, so 65 is 85.

Deepgram Voice Agent API 60

No x402, MPP or L402 (0 of 40). Per-minute prices for every tier on the public pricing page (20). $200 of credit with no card (20). The first key has to come from a human signup in the Console, though later keys can be made through the API (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Schema & documentation Deepgram Voice Agent API +22

Bland AI API + MCP 68

No OpenAPI document found. The MCP server's dedicated tools take typed inputs and its API Reference tools take each reference page's parameters, but no machine-readable contract is published (5 of 25). llms.txt with 551 entries, each page served as Markdown (10). MCP tool descriptions say when to use a tool, for example the reference tells agents to use send_call and to choose one of agent_id, persona_id, pathway_id or task (14 of 20). The REST reference types every parameter with enums and defaults, though pathways travel as a raw graph and call_bland_api is a free-form passthrough (11 of 15). Errors for 400, 401, 402, 403, 404, 429 and 500 are documented with example messages (13 of 15). Versioned v1 and v2 APIs, agent versions and environments, and a dated changelog (15). 5 + 10 + 14 + 11 + 13 + 15 = 68.

Deepgram Voice Agent API 90

Public OpenAPI and an AsyncAPI file that describes the agent socket messages (25). llms.txt with a Markdown copy of each page, and a keyless docs MCP server (10). Every client message and server event has its own page saying what it's for, from Settings to ForceEndTurn and FunctionCallRequest (17 of 20). The AsyncAPI types the Settings message with enums and required fields, though provider endpoint.headers are free-form (13 of 15). Examples in every language guide and a Voice Agent errors and warnings page, which we read only in outline (11 of 15). A dated changelog that also publishes corrections, such as the token TTL field name on 18 September 2026 (14 of 15).

Maintenance & community Deepgram Voice Agent API +15

Bland AI API + MCP 70

The newest entry in the product changelog is still 3 August 2026, 91 days before 2 November. Bland's official plugin for its hosted MCP server and Norm agent builder (CINTELLILABS/bland-plugins, MIT, linked from the docs) keeps a dated changelog, with bland 2.2.1 and norm 1.11.1 on 20 October 2026 (30). In the 90 days from 4 August, that changelog has 30 dated releases on 13 days from 8 September to 20 October, and the migration guide dates the agent architecture change to September 2026, while the product changelog's 6 July, 21 July and 3 August entries have left the window; the CLI's npm dates couldn't be read (20). Public changelog, no public issue tracker, and we didn't test support (8 of 15 for a closed service). Official tooling is the bland-cli npm package (Node 18 or later), a web SDK and a TTS Node library, with no server SDK in a second language (8 of 15). No public repository or CI for the CLI (4 of 10). 30 + 20 + 8 + 8 + 4 = 70.

Deepgram Voice Agent API 85

Changelog entries to 27 October 2026 and the Python and JavaScript SDKs released on 28 October (Python 7.16.0, JavaScript 5.17.0), both adding Voice Agent Think Live messages (30). 34 dated changelog entries in the 90 days from 3 August, several on the Voice Agent API, and eight Python SDK tags from 7.9.0 on 14 September to 7.16.0 on 28 October (20). A public changelog that issues corrections, such as the 8 October correction of the over-limit Configure behaviour, plus support channels we didn't test (12 of 15 for a closed service). Official SDKs current in Python, JavaScript, Java, Go, .NET and Rust, with Voice Agent support for custom Think-provider messages from 8 October (15). MIT SDKs with current releases (8 of 10). 30 + 20 + 12 + 15 + 8 = 85.

Agent ergonomics Deepgram Voice Agent API +14

Bland AI API + MCP 53

The hosted MCP server lists 62 dedicated tools and 282 API Reference tools, one per reference page, plus 3 prompts on key connections. Sign-in connections see a smaller allowlist, but there are no toolsets or dynamic loading (5 of 25). List endpoints such as audit logs and knowledge bases page and filter, but we found no field selection on call logs (14 of 20). Errors carry codes and readable messages, and a restricted key's 403 names the permission it lacks (16 of 20). Every MCP tool carries a read, write or destructive annotation, but there are no idempotency keys on call creation (10 of 20). A call needs only phone_number and a task, agent_id, persona_id or pathway_id, with defaults for voice and temperature. Official tooling is the Node CLI, a web SDK and a TTS Node library, and we found no Python SDK (8 of 15). 5 + 14 + 16 + 10 + 8 = 53.

Deepgram Voice Agent API 67

Scored as an API. Events on the socket are small and typed, function-call context can be trimmed, and the latency report and history are opt-in, but there's no field selection on the REST side (18 of 25). Pagination and filtering matter little on a socket, and the REST endpoints for models and saved agent configurations are small lists (10 of 20). Errors and warnings are documented as typed events (14 of 20). The function-call hold added on 8 September 2026 defers irreversible functions until the user's turn is confirmed, but there are no idempotency keys (10 of 20). Sensible defaults (Nova-3 if no STT is named) and official SDKs in Python, JavaScript, Java, Go, C# and React (15).

Reliability Deepgram Voice Agent API +10

Bland AI API + MCP 65

Atlassian Statuspage at status.bland.ai with US, Asia Pacific and Canada components and an incident history back to 20 October 2025, read on 2 November through its history feed (20). Six incidents in the 90 days from 4 August. Five were partial and read as minor, latency of 30 minutes on 27 August and 35 minutes on 14 September, delayed or missing audio on BTTS V3 voices for about two hours on 25 September (some calls, one voice family), variable extraction failing for some customers for about an hour on 5 October, and inbound calls in the US region failing for 8 minutes on 19 October with outbound unaffected. On 14 October, from about 3:00 to 4:10 PM PT, an upstream outage took down the language model every agent uses in conversation, live calls went silent or slow and outbound dispatch was paused, which we count as one major (10). Numeric limits are published, 10 concurrent, 100 an hour and 100 a day on Start, 50, 1,000 and 2,000 on Build, 120 MCP requests a minute and one call per number every 10 seconds (15). The call API documents 429 responses with messages, but we found no Retry-After, backoff or idempotency guidance (5 of 15). The pricing page claims a 99.9 per cent uptime SLA on every plan, while the terms of 28 August 2026 give no uptime commitment and no credits, so we give half (5). The API is generally available (10). 20 + 10 + 15 + 5 + 5 + 10 = 65.

Deepgram Voice Agent API 75

Statuspage at status.deepgram.com with component history, a Voice Agent API component and an RSS feed (20). Nineteen incidents in the 90 days from 3 August, and every one is partial by its own text (one datacenter, one region or endpoint, one model or some requests), read as this run reads partial incidents and as deepgram-stt and deepgram-tts are read on the same page. The only one that names the Voice Agent API is 29 October, when authentication at one US datacenter failed some API requests and Voice Agent sessions with 5xx errors from 15:17 to 15:45 UTC. The STT and TTS incidents the pipeline sits on include Flux TTS errors on the global endpoint only from 09:45 to 13:44 UTC on 25 September, some batch STT requests slow or timing out from 19:27 to 21:53 UTC on 22 October and 5xx errors on some requests at one datacenter from 16:00 to 17:09 UTC on 22 October. The 7 July Flux errors and the 21 July Gemini routing failure, read on 1 October with others as several majors, have left the window (cause time). Minor only (20). Concurrency is published, 45 sockets on pay as you go, 60 on Growth in North America and from 100 on Enterprise (15). Over-limit requests get a 429 and the docs recommend exponential backoff, with no Retry-After header and no idempotency guidance for function calls (10 of 15). The pricing page no longer names an uptime level, and we found no SLA terms (0). The Voice Agent API is generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

Security & auth Bland AI API + MCP +8

Bland AI API + MCP 79

Organisation API keys, several per organisation and each revocable on its own, and since the 1 October check restricted keys with per-resource scopes (calls:read, calls:create, agents:write and others) and OAuth client credentials with the same permissions for short-lived tokens (an organisation that doesn't see OAuth clients in its dashboard is told to contact support). Restricted keys are rolling out by organisation and aren't available on pinned deployments, credited as conditional availability elsewhere in this run (30). A key can now be limited to read scopes, sign-in connections to the MCP server take mcp:read or mcp:write scopes, and destructive tools carry an annotation for the client's approval prompt. The server no longer asks for confirmation itself, and personas, numbers and tools stay full-access only (15 of 20). Agents read caller speech and transcripts, which are untrusted, and we found guard rails mentioned in the CLI but no prompt-injection guidance (5 of 15). Audit logs exist but are an enterprise function and don't record API key use, and every call has a log; the key list shows who created each key (12 of 15). security.txt valid until 2027-04-05 (re-read on 2 November), a trust portal, SOC 2 Type II and a PCI DSS assessment by a QSA per the vendor, and a disclosure address. No bug bounty found (17 of 20). 30 + 15 + 5 + 12 + 17 = 79.

Deepgram Voice Agent API 71

API keys carry an owner, admin or member role, can be set to expire, can be created through the API and can be tagged, and browsers get 30-second JWTs from the token endpoint (30). Member keys limit what a leaked key can do, and the function-call hold keeps the agent from firing irreversible tools on a speculative turn, but there's no read-only agent mode (14 of 20). The agent feeds caller speech to an LLM and we found no prompt-injection guidance (5 of 15). Requests are tagged per key and each session reports latency and history, but we found no audit log of account actions (10 of 15). The compliance page states SOC 2 Type 1 and Type 2, HIPAA and PCI. deepgram.com now serves a valid security.txt (Contact security@deepgram.com, Expires 30 September 2027), not found on 30 September. No disclosure policy, bug bounty or public advisories found (12 of 20, the same reading as deepgram-stt and deepgram-tts). 30 + 14 + 5 + 10 + 12 = 71.

Score by category

CategoryWeightBland AI API + MCPDeepgram Voice Agent APIEdge
Reliability16%6575Deepgram Voice Agent API +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6890Deepgram Voice Agent API +22
Agent ergonomics13%5367Deepgram Voice Agent API +14
Security & auth14%7971Bland AI API + MCP +8
Payments & pricing10%8560Bland AI API + MCP +25
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7085Deepgram Voice Agent API +15
Transparency & trust7%7278Deepgram Voice Agent API +6
Negative events≤1500
TotalB 69.5/100BB 74.7/100

Facts side by side

FactBland AI API + MCPDeepgram Voice Agent API
KindHTTP APIHTTP API
VendorBland AIDeepgram
Hosted endpointhttps://api.bland.ai/v1https://agent.deepgram.com/v1/agent
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP, stdio, SSE (legacy)
AuthAPI keyAPI key
PricingFreemiumPay per use
Price for voice agents$29.99 per month (plan)not published
x402nono
LicencenoneMIT (SDKs)
Tools exposed42none
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-132026-10-28
Terms last updated2026-08-282026-08-06
Privacy policy last updated2026-06-232021-10-26
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textyes
Popularity1.2k npm/wk468 stars, 1.1M npm/wk, 805k PyPI/wk
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Bland AI API + MCP

One per-minute rate covering STT, LLM, TTS and telephony, $0.14 on Start and $0.12 on Build, and restricted keys with per-resource scopes rolling out. No OpenAPI document, the MCP server lists over 340 tools without toolsets, and the product changelog's newest entry is from 3 August 2026.

Deepgram Voice Agent API

$0.075 a minute all in on Standard, $0.050 with your own LLM and TTS, and $200 of credit with no card. Every status incident since August was partial. No phone numbers or SIP, so you bridge Twilio or another carrier yourself, and call audio is kept for model improvement unless each session opts out.

Before you call either

Bland AI API + MCP

  1. Call wait_for_call (it waits up to 45 seconds) instead of polling get_call_log
  2. Keep client tool-approval prompts on for destructive MCP tools; the server no longer asks for confirmation
  3. Space calls to the same number at least 10 seconds apart or expect a 429
  4. Budget $0.015 for every outbound attempt, including ones that never connect
  5. Use a restricted key with only the scopes you need for REST calls; the MCP server needs a full-access key or sign-in

Deepgram Voice Agent API

  1. Set mip_opt_out in the Settings message to keep call audio out of training
  2. Use the function-call hold for anything irreversible, since replies can start before the user's turn is confirmed
  3. Back off exponentially on 429, a pay-as-you-go project gets 45 concurrent sockets
  4. Pin the LLM version, an unpinned Gemini route failed for 1.5 hours on 21 July 2026
  5. Mint browser tokens with ttl_seconds, not ttl, or they expire after 30 seconds

Questions

Which is better for AI agents, Bland AI API + MCP or Deepgram Voice Agent API?

Deepgram Voice Agent API scores 74.7 (BB) on agent readiness against Bland AI API + MCP's 69.5 (B), and leads in 5 of 7 scored categories. Bland AI API + MCP leads on security & auth and payments & pricing.

Do Bland AI API + MCP and Deepgram Voice Agent API need an API key?

Both need an API key.

Can an agent call Bland AI API + MCP and Deepgram Voice Agent API without installing anything?

Yes. Bland AI API + MCP has a hosted endpoint at https://api.bland.ai/v1 and Deepgram Voice Agent API at https://agent.deepgram.com/v1/agent.

Other comparisons with Bland AI API + MCP or Deepgram Voice Agent API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.