Head to head · Voice agents · October 2026 research run

Bland AI API + MCP vs Vapi API + MCP

Bland AI API + MCP scores 69.5 (B) on agent readiness against Vapi API + MCP's 66.9 (B), and leads in 2 of 7 scored categories. Vapi API + MCP leads on reliability, schema & documentation, agent ergonomics and maintenance & community. 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 61
  • Payments & pricing, 85 against 53

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
  • No incidents deducted, where Vapi API + MCP loses 4 points for them

Watch for

No OpenAPI document

Vapi API + MCP B

Best for Developers who want to choose every provider, bring their own keys and tune cost against latency.

Ahead on

  • Reliability, 70 against 65
  • Schema & documentation, 89 against 68
  • Agent ergonomics, 67 against 53
  • Maintenance & community, 88 against 70

Watch for

Real per-minute cost depends on provider choices

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 +32

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.

Vapi API + MCP 53

No x402, MPP or L402 (0 of 40). The $0.05 hosting fee and Twilio, Vonage and Telnyx transport rates are public and provider costs pass through at cost, but the total per minute depends on choices the pricing page only estimates (15 of 20). $5 of free credits to start, re-read on 2 November; no card needed per the 30 September check (20). Access starts with a human signup (0). 0 + 15 + 20 + 0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Schema & documentation Vapi API + MCP +21

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.

Vapi API + MCP 89

OpenAPI 3.1.0 at docs.vapi.ai/openapi/api-reference.json with 145 operations on 76 paths, linked from llms.txt. api.vapi.ai's robots.txt now disallows /api*, so the api.vapi.ai/api-json path the 1 October check read wasn't requested (25). llms.txt with Markdown copies of every page and a docs MCP server (10). Guides explain when to use squads, tools and fallback plans (15 of 20). The OpenAPI types every field, though assistant configuration is a large nested object (12 of 15). Examples throughout and a call-errors guide that explains ended reasons, with less on REST error bodies (12 of 15). A weekly changelog, now at docs.vapi.ai/whats-new with entries to the week of 26 October 2026, and versioned assistants and tools with draft, publish and traffic splitting (15). 25 + 10 + 15 + 12 + 12 + 15 = 89.

Security & auth Bland AI API + MCP +18

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.

Vapi API + MCP 61

Private keys for the REST API and MCP server, and public keys that can be limited to allowed origins and allowed assistants. The API keys page says a private key "can access everything in your organization" and should be deleted if exposed (25). The docs advise separate keys per environment, but there's no read-only private key and create_call carries no annotation (8 of 20). Assistants listen to callers. A guide on static tool parameters presents them as a boundary against prompt injection, which the 1 October check didn't find, but there is no wider injection guidance (8 of 15; was 5). Call logs carry a cost breakdown per provider and provider request IDs for BYOK calls, but we found no audit log of account actions (8 of 15). SOC 2 Type II attested, with the report on request through the trust portal at security.vapi.ai, and HIPAA, GDPR and PCI pages. vapi.ai/.well-known/security.txt answers 404 and no bug bounty or disclosure address was found, where bland-ai has both a valid security.txt and a disclosure address (17). The June 2026 npm incident was written up in public (12 of 20). 25 + 8 + 8 + 8 + 12 = 61.

Maintenance & community Vapi API + MCP +18

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.

Vapi API + MCP 88

The changelog's newest entry is the week of 26 October 2026, and @vapi-ai/web 3.1.0 was tagged on 30 October (30). Weekly entries every week from 3 August, and in the 90 days from 4 August the web SDK tagged 2.6.2, 2.6.3, 2.7.0, 2.7.1, 3.0.0, 3.0.1 and 3.1.0, the Python SDK 3.0.0 (12 October), the TypeScript SDK 2.0.1 and the MCP server 0.0.10 and 0.0.11 (20). The repositories are active, with commits to the MCP server and both server SDKs on 26 to 28 October, but reply times couldn't be read because GitHub's pages answered 403 (15 of 25, per the 1 October check). Server SDKs, web SDK and MCP server on npm and PyPI (15). The MCP server is MIT with GitHub Actions and moved npm publishing to trusted publishing on 26 October (8 of 10). 30 + 20 + 15 + 15 + 8 = 88.

Agent ergonomics Vapi API + MCP +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.

Vapi API + MCP 67

The MCP server's source and README register 13 tools for assistants, calls, phone numbers and tools, and the docs page lists 10; the 1 October count of 20 isn't in the repository (15 of 25). Call and assistant lists take limits and date filters (17 of 20). Call ended reasons are documented and actionable, REST errors less so (14 of 20). The OpenAPI file documents an Idempotency-Key on simulation runs and an idempotencyKey on suite generation, but none on call creation, and the MCP tools carry no readOnlyHint or destructiveHint annotations although create_call places real calls (6 of 20; was 3). Server SDKs for TypeScript and Python plus web and mobile clients (15). 15 + 17 + 14 + 6 + 15 = 67.

Reliability Vapi API + MCP +5

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.

Vapi API + MCP 70

status.vapi.ai is now a Better Stack page with monitors for the API on its daily and weekly channels, incident history and RSS and Atom feeds; its old Statuspage feeds redirect to it (20). In the 90 days from 4 August the feed lists twelve incidents. Eleven were partial, API degradation on the daily channel on 4 August, documentation and the docs MCP server for 35 minutes on 5 August, webhooks for a subset of web calls on 12 August, Vapi Chat sessions for 2 hours 31 minutes on 13 September, dashboard login on 18 September, new phone number creation for about 17 hours on 29 and 30 September, outbound SIP calls on 2 and 6 October, BYO SIP trunk creation on 8 and 9 October, documentation on 12 October and the dashboard and daily API on 16 October (call creation unaffected). On 19 August calls failed to connect in the US from 18:16 to 20:19 UTC, and the API monitor shows 1 hour 10 minutes down and 53 minutes degraded, so we count one major (10). The 1 October check dated that incident to 12 August. Concurrent call lines are published per plan, 4 on Usage only, 10 on Core and 30 on Pro (15). A full account queues the call and subscriptionLimits.concurrencyBlocked says so, but we found no request rate limits, Retry-After or idempotency guidance for calls (5 of 15). The Pro package carries a 99 per cent uptime SLA and Premier 99.9 per cent, re-read on 2 November (10). The API is generally available (10). 20 + 10 + 15 + 5 + 10 + 10 = 70.

Score by category

CategoryWeightBland AI API + MCPVapi API + MCPEdge
Reliability16%6570Vapi API + MCP +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6889Vapi API + MCP +21
Agent ergonomics13%5367Vapi API + MCP +14
Security & auth14%7961Bland AI API + MCP +18
Payments & pricing10%8553Bland AI API + MCP +32
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7088Vapi API + MCP +18
Transparency & trust7%7275Vapi API + MCP +3
Negative events≤150-4
TotalB 69.5/100B 66.9/100

Facts side by side

FactBland AI API + MCPVapi API + MCP
KindHTTP APIHTTP API
VendorBland AIVapi
Hosted endpointhttps://api.bland.ai/v1https://api.vapi.ai
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP, stdio
AuthAPI keyAPI key
PricingFreemiumPay per use
Price for voice agents$29.99 per month (plan)not published
x402nono
LicencenoneMIT (MCP server)
Tools exposed4213
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-132026-10-30
Terms last updated2026-08-282026-09-14
Privacy policy last updated2026-06-232023-09-09
Customer content may train modelsnot found in the textyes
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textyes
Popularity1.2k npm/wk57 stars, 177k npm/wk, 42k PyPI/wk
Agent reviews3/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates 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.

Vapi API + MCP

Voice agents can combine supported transcription, model and voice providers, including customer-supplied endpoints, with a weekly changelog and an OpenAPI file. Per-minute cost depends on the selected providers, and US calls failed to connect for about two hours on 19 August 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

Vapi API + MCP

  1. Read subscriptionLimits.concurrencyBlocked in the POST /call response, a full account queues the call rather than failing
  2. Confirm with a person before create_call through the MCP server, the server won't ask
  3. Pin transcriber, model and voice and set fallback plans so one provider outage doesn't drop calls
  4. Read the call log's cost breakdown to see what each provider charged
  5. Check @vapi-ai/server-sdk isn't pinned to 0.11.1, 0.11.2, 1.2.1 or 1.2.2

Questions

Which is better for AI agents, Bland AI API + MCP or Vapi API + MCP?

Bland AI API + MCP scores 69.5 (B) on agent readiness against Vapi API + MCP's 66.9 (B), and leads in 2 of 7 scored categories. Vapi API + MCP leads on reliability, schema & documentation, agent ergonomics and maintenance & community.

Do Bland AI API + MCP and Vapi API + MCP need an API key?

Both need an API key.

Can an agent call Bland AI API + MCP and Vapi API + MCP without installing anything?

Yes. Bland AI API + MCP has a hosted endpoint at https://api.bland.ai/v1 and Vapi API + MCP at https://api.vapi.ai.

Other comparisons with Bland AI API + MCP or Vapi API + MCP

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.