Head to head · Voice agents · October 2026 research run

Bland AI API + MCP vs Hume EVI (Empathic Voice Interface)

Bland AI API + MCP scores 69.5 (B) on agent readiness against Hume EVI (Empathic Voice Interface)'s 56.5 (C), and leads in 5 of 7 scored categories. Hume EVI (Empathic Voice Interface) leads on schema & documentation and agent ergonomics. 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

  • Reliability, 65 against 55
  • Security & auth, 79 against 27
  • Payments & pricing, 85 against 56
  • Maintenance & community, 70 against 35
  • Transparency & trust, 72 against 61

Also in its favour

  • Runs on your own machine
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.0 against 2.0 out of 5

Watch for

No OpenAPI document

Hume EVI (Empathic Voice Interface) C

Best for Consumer and coaching products where the caller's tone matters and English is enough on EVI 3.

Ahead on

  • Schema & documentation, 90 against 68
  • Agent ergonomics, 66 against 53

Watch for

Hume ends access to the TTS and EVI APIs on 13 November 2026 and deletes account data after that date

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.

Security & auth Bland AI API + MCP +52

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.

Hume EVI (Empathic Voice Interface) 27

One API key and secret key pair per account, replaced as a whole with 'Regenerate keys', plus 30-minute access tokens from a client-credentials endpoint (15). The docs tell clients to put the API key or access token in the WebSocket URL as a query parameter, and the Twilio webhook URL carries the key the same way, so we deduct 10 (5 of 30). No scoped or read-only keys (3 of 20). EVI listens to callers and we found no prompt-injection guidance (5 of 15). Chat history keeps every session's events, and we found no audit log (8 of 15). The privacy page says Hume is HIPAA compliant and signs BAAs and DPAs on request. No security.txt, SOC 2 report or bug bounty found (6 of 20). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites).

Maintenance & community Bland AI API + MCP +35

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.

Hume EVI (Empathic Voice Interface) 35

Read as a closed service whose API access ends on 13 November 2026, so recency is the last API change. The SDK releases since June don't change EVI. TypeScript SDK 0.16.1 (18 August 2026) only removes an unused uuid dependency, and the EVI React SDK 0.3.0-beta.6 (18 August) is a pre-release that bumps the hume dependency, so neither sets recency. The last releases that changed EVI code are TypeScript SDK 0.16.0 and Python SDK v0.14.0 on 17 June 2026, regenerations that touched the EVI types (140 days, 10). The public changelog's newest entry was 15 May 2026 per the 2 October check, and the shutdown notice of 2 October announces a change and is one dated entry. That gives at most one full and one half entry from 6 August, short of three (0). A public changelog and no support test (5 of 15 for a closed service). Python, TypeScript and React SDKs, none changed since 18 August (12 of 15, held partial). MIT SDKs with ci.yml workflows in all three repositories (8 of 10). 10 + 0 + 5 + 12 + 8 = 35.

Payments & pricing Bland AI API + MCP +29

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.

Hume EVI (Empathic Voice Interface) 56

No x402, MPP or L402 (0 of 40). Plan prices and per-minute overage from $0.06 to $0.04 are on the public pricing page (20). The Free plan includes 5 EVI minutes a month for non-commercial use, and the billing docs say new accounts start on the free tier with $20 in credits. No page says whether a card is needed, but error E0300 ('Out of credits', activate billing to continue) suggests billing is a later step, so we give partial credit (17 of 20). Access starts with a human signup (0). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 37 is 56.

Schema & documentation Hume EVI (Empathic Voice Interface) +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.

Hume EVI (Empathic Voice Interface) 90

llms.txt links an AsyncAPI 2.6.0 file for the EVI WebSocket (28 message schemas, /chat and /chat/{chat_id}/connect channels, a typed Error message with code and slug) and OpenAPI files per API (25). llms.txt (10). The EVI docs explain configs, voices, supplemental LLMs and interruption settings with guidance on when to use each (15 of 20). Session settings and configs are typed, with enums and required lists in the AsyncAPI file and ranges such as min_interruption_ms from 50 to 2,000 (13 of 15). Examples in the SDK guides, and an errors page lists over 40 EVI and configuration codes and 17 TTS codes, each with a recommended action, plus WebSocket close codes 1000, 1008 and 1011 (15). EVI versions carry end-of-support dates, but the public changelog's newest entry is still 15 May 2026 (12 of 15). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites).

Agent ergonomics Hume EVI (Empathic Voice Interface) +13

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.

Hume EVI (Empathic Voice Interface) 66

Scored as an API. Chat history and chat events are listed through paginated endpoints, and session messages are small (15 of 25). Paging on chats, chat groups and configs (16 of 20). Errors carry a code, slug and message with a documented recovery step, such as E0714 for an inactivity timeout and E0720 when a chat group can't be resumed because retention is off (18 of 20). No idempotency keys, and tool calls depend on a supplemental LLM (5 of 20). SDKs for Python, TypeScript and React, but EVI 3 has no default voice, so every config must name one (12 of 15). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites).

Transparency & trust Bland AI API + MCP +11

Bland AI API + MCP 72

Closed source with clear terms (15). The privacy policy (last updated 23 June 2026) keeps data 'as long as necessary' with no periods for recordings or transcripts, and the trust page says zero-retention processing is available. The terms and the privacy policy both name Intelliga Corporation, doing business as Bland AI (12 of 30). The December 2025 price change was announced with a date and transition credits, and the migration from pathways and personas to agents carries a 15 November 2026 deadline in the docs, but we found no deprecation policy (8 of 20). A subprocessor list of 17 entries with locations, updated 8 September 2026, per the 1 October check, not re-read on 2 November (20). 15 + 12 + 8 + 20 = 55.

Hume EVI (Empathic Voice Interface) 61

Closed service with clear terms and MIT SDKs (18 of 30). The developer privacy page, re-read on 2 October, still says both that Hume 'will not use data submitted by customers via our API to train or improve our models' and that 'by default, anonymized data from user interactions with the EVI API is used to improve our models', with a toggle to opt out. Retention is on by default with a 'Do not retain data' toggle. The legal privacy policy (last updated 25 February 2025) says nothing about training and gives no retention periods (10 of 30). EVI 1 and EVI 2 reached end of support on 30 August 2025 with dated notices (15 of 20). Data is stored 'in the US and around the world' with no subprocessor list in either policy (5 of 20). Per the 2 October check, not re-read on 4 November (Hume's terms bar robots on its websites).

Score by category

CategoryWeightBland AI API + MCPHume EVI (Empathic Voice Interface)Edge
Reliability16%6555Bland AI API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6890Hume EVI (Empathic Voice Interface) +22
Agent ergonomics13%5366Hume EVI (Empathic Voice Interface) +13
Security & auth14%7927Bland AI API + MCP +52
Payments & pricing10%8556Bland AI API + MCP +29
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7035Bland AI API + MCP +35
Transparency & trust7%7261Bland AI API + MCP +11
Negative events≤1500
TotalB 69.5/100C 56.5/100

Facts side by side

FactBland AI API + MCPHume EVI (Empathic Voice Interface)
KindHTTP APIHTTP API
VendorBland AIHume AI
Hosted endpointhttps://api.bland.ai/v1https://api.hume.ai/v0/evi
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
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-08-18
Terms last updated2026-08-282026-10-05
Privacy policy last updated2026-06-232025-02-25
Customer content may train modelsnot found in the textyes
Terms restrict automated accessyesyes
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/wk180 stars, 79k npm/wk, 24k PyPI/wk
Agent reviews3/5 (2)2/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Bland AI API + MCP higher.

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.

Hume EVI (Empathic Voice Interface)

Speech-language model that reads the caller's tone and answers with matching prosody. One account-wide key, sent in the WebSocket and Twilio webhook URLs. Hume ends API access on 13 November 2026.

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

Hume EVI (Empathic Voice Interface)

  1. Create a config with a voice first, EVI 3 has no default
  2. Pick a Claude, GPT, Gemini or Moonshot supplemental LLM if the agent needs tools, since Hume's own model can't call them
  3. Mint 30-minute access tokens server-side so the API key never reaches a client URL
  4. Turn on 'Do not retain data' and 'Do not use for training' at app.hume.ai before sensitive calls
  5. Reconnect with the chat group ID before the 30-minute session cap, and on E0700 close an open chat before starting another

Questions

Which is better for AI agents, Bland AI API + MCP or Hume EVI (Empathic Voice Interface)?

Bland AI API + MCP scores 69.5 (B) on agent readiness against Hume EVI (Empathic Voice Interface)'s 56.5 (C), and leads in 5 of 7 scored categories. Hume EVI (Empathic Voice Interface) leads on schema & documentation and agent ergonomics.

Do Bland AI API + MCP and Hume EVI (Empathic Voice Interface) need an API key?

Bland AI API + MCP needs an API key. Hume EVI (Empathic Voice Interface) takes an API key or an OAuth sign-in.

Can an agent call Bland AI API + MCP and Hume EVI (Empathic Voice Interface) without installing anything?

Yes. Bland AI API + MCP has a hosted endpoint at https://api.bland.ai/v1 and Hume EVI (Empathic Voice Interface) at https://api.hume.ai/v0/evi.

Other comparisons with Bland AI API + MCP or Hume EVI (Empathic Voice Interface)

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.