# Synthflow API + MCP vs Vaani Developer Platform (slim)

> Synthflow scores 51.3 (D) to Vaani Developer Platform's 44.6 (E) for voice agents. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/synthflow-vs-vaani-voice.md (~5,500 tokens) · this version ~3,030 tokens · JSON https://www.anchorterminal.com/compare/synthflow-vs-vaani-voice.json · canonical https://www.anchorterminal.com/compare/synthflow-vs-vaani-voice
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-02
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Synthflow API + MCP scores 51.3 (D) on agent readiness against Vaani Developer Platform's 44.6 (E), and leads in 5 of 7 scored categories. Vaani Developer Platform leads on agent ergonomics and payments & pricing. Both do voice agents.

- Synthflow API + MCP: D 51.3, rank #932 of 1266 · https://www.anchorterminal.com/tools/synthflow.min.md
- Vaani Developer Platform: E 44.6, rank #1084 of 1266 · https://www.anchorterminal.com/tools/vaani-voice.min.md
- Synthflow API + MCP, good for Contact centres buying a managed voice-agent platform with SIP connectors to their existing PBX and EU data residency. Ahead on Reliability, 45 against 28; Schema & documentation, 87 against 57; Security & auth, 51 against 44; Maintenance & community, 68 against 59; Transparency & trust, 68 against 42.
- Vaani Developer Platform, good for Outbound and inbound phone agents and campaigns for Indian businesses, with Hindi, Hinglish and Indian carriers, India DND checks and TRAI calling windows built in, plus WebRTC sessions for apps. Ahead on Agent ergonomics, 64 against 45; Payments & pricing, 22 against 0. Also Runs on your own machine.

| Category | Synthflow API + MCP | Vaani Developer Platform |
| --- | --- | --- |
| Reliability (16%) | 45 | 28 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 57 |
| Agent ergonomics (13%) | 45 | 64 |
| Security & auth (14%) | 51 | 44 |
| Payments & pricing (10%) | 0 | 22 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 68 | 59 |
| Transparency & trust (7%) | 68 | 42 |

| Fact (where they differ) | Synthflow API + MCP | Vaani Developer Platform |
| --- | --- | --- |
| Vendor | Synthflow | Vaani AI Research Private Limited |
| Hosted endpoint | `https://api.synthflow.ai/v2` | `https://api.vaanivoice.ai` |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Paid | Pay per use |
| Licence | none | Proprietary hosted service under Vaani AI Research's terms of service. The Python SDK (vaani-sdk) and the local MCP server (vaani-research-mcp) are MIT. The SDK's full source ships in its PyPI sdist, and the MCP server's npm package holds only the bundled JavaScript |
| Tools exposed | 60 | 9 |
| Read-only variant documented | no | yes |
| Last release | 2026-10-01 | 2026-10-14 |
| Terms last updated | 2026-05-13 | no date given |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | none | 14 npm/wk, 19 PyPI/wk |
| Agent reviews | 2/5 (2) | none |

Why the edge:
- Schema & documentation, Synthflow API + MCP +30: Synthflow API + MCP 87 (OpenAPI at docs.synthflow.ai/openapi.json (25). llms.txt with Markdown pages (10). Guides cover agents, actions and SIP connectors with when-to-use advice (14 of 20). Typed request bodies, with agent configuration as large nested objects (12 of 15). Examples throughout, and transfer failures gained nine specific reasons on 29 September 2026 (11 of 15). A dated changelog with entries most weekdays and a v2 API (15).); Vaani Developer Platform 57 (A public OpenAPI 3.1 file at docs.vaani.dev/api-reference/openapi.json, version 2.0.0, but it holds 5 of the 24 operations in the API reference (trigger-call, call history, transcript, stream, call details). It declares the key only as a header parameter with no security scheme, its trigger-call schema leaves out `medium` and `modify_agent`, and four response schemas are empty. The MCP tools have typed zod inputs (8 of 25). llms.txt, llms-full.txt and a Markdown copy of each page on Mintlify (10). Pages explain what each route is for and warn where it matters, such as dispatch acceptance not meaning a completed call, transcripts returning 404 while processing, and real paid calls from trigger_call (14 of 20). Ranges and enums are documented (`medium`, `voice_speed` 0.6 to 1.4, `page_size` up to 200, campaign retries 1 to 10, campaign status), but `metadata`, `modify_agent` and three MCP tool payloads are free-form objects (9 of 15). Request examples in cURL, Python and JavaScript on every endpoint, a campaign error-code table, 422 and 404 bodies and an SDK exception table by status. No single error reference for the whole API (12 of 15). The docs state API version 2.0.0, but no changelog or release notes page was found (4 of 15). 8+10+14+9+12+4 = 57.)
- Transparency & trust, Synthflow API + MCP +26: Synthflow API + MCP 68 (Closed platform with clear terms (15). Recordings and transcripts can be switched off or deleted after 30 days, PII redaction is available, and a BAA template is public. Default retention looks indefinite (18 of 30). Old self-serve plans are closed to new subscriptions and the changelog is dated, but we found no deprecation policy (8 of 20). Separate Global, US and EU regions are documented, and we didn't find a subprocessor list on the pages we read (12 of 20).); Vaani Developer Platform 42 (A closed service. The terms name Vaani AI Research Private Limited, its Bengaluru address, CIN, Indian law and Bengaluru courts, but they're undated, written for the website www.vaaniresearch.com, and say nothing on billing, refunds, API use or customer data. The SDK and MCP server are MIT, with the SDK's full source in its PyPI sdist (14 of 30). The privacy policy (undated) keeps data, including voice recordings, for up to 24 months, while the pricing table gives 30 days' retention on pay as you go and zero retention on Enterprise. Voice data trains models only with explicit consent. No DPA found (8 of 30). No deprecation policy. The privacy policy promises 15 days' notice of significant changes, and the terms allow changes and termination without notice (2 of 20). The privacy policy names vendor categories (cloud hosting, analytics, voice transcription) and says data may be stored outside India. Model and telephony providers can be read from the calculator, and India data residency is offered on demand. No subprocessor list or data location for the hosted service (5 of 20). 14+8+2+5 = 29.)
- Payments & pricing, Vaani Developer Platform +22: Synthflow API + MCP 0 (No x402, MPP or L402 (0 of 40). Sales-led only, with contracts from $30,000 a year and no published per-minute price (0). No free tier or trial for new customers (0). An agent can't get access without a sales process (0).); Vaani Developer Platform 22 (No x402, MPP or L402 (0 of 40). The ₹1 ($0.02) a minute platform fee, number rental, concurrency lines and add-ons are public, and the calculator shows each provider's unit rate without a login. Registry checks, extraction and evaluations "can add separate charges" that aren't priced, and the billing pulse depends on the account, so 3 off (17 of 20). The home page says "Start free on Vaani's Platform", but the pricing page states a prepaid wallet with no free credit, trial minutes or card rule, and we didn't sign up to check, so 5 of 20. A person signs up with email verification at platform.vaani.dev and creates keys in the dashboard (0). 0+17+5+0 = 22.)
- Agent ergonomics, Vaani Developer Platform +19: Synthflow API + MCP 45 (The hosted MCP server lists 60 tools in seven groups, with no toolsets or read-only subset (5 of 25). Call and log lists filter and page (14 of 20). Errors carry codes and the new transfer failure reasons (13 of 20). Deletes need a second call with `confirmed=true`, but publish and rollback run at once and there are no annotations or idempotency keys documented (8 of 20). No official SDK packages, so agents work from raw HTTP or the MCP server (5 of 15).); Vaani Developer Platform 64 (The local MCP server loads 9 compact tools, and `VAANI_READ_ONLY=true` leaves 3. Transcripts are cut at 20,000 characters by default with a note. The REST API has no field selection or summaries, so 3 off (22 of 25). Call history pages by `page` and `page_size` up to 200 with no filters. The MCP agent filter runs client-side on one page. Agents filter by `search` and `published_only` and campaigns by `status` (12 of 20). Campaign errors carry a machine-readable `code`, a message, the path and a `request_id` (shown as "unknown" in the example). Validation errors list the field location, the SDK maps each status to a typed exception including 402 for a low wallet, and the MCP server adds a hint per status (15 of 20). All 9 MCP tools carry readOnlyHint, destructiveHint and idempotentHint, with `trigger_call` and `campaign_action` marked destructive. No idempotency key on trigger-call, and the MCP client retries a POST once after a timeout or 5xx, so a call can be placed twice. The webhook docs say to deduplicate by event id (8 of 20). A call needs `agent_id`, `contact_number` and `name`, with `medium` defaulting to telephony. One official SDK, Python, sync and async. The npm package is an MCP server, not an SDK (7 of 15). 22+12+15+8+7 = 64.)
- Reliability, Synthflow API + MCP +17: Synthflow API + MCP 45 (Statuspage at status.synthflow.ai with incidents and maintenance back to May 2025 (20). Four incidents since 3 July 2026, 18 minutes of degraded US calling on 6 July, post-call webhook failures from 08:20 to 11:10 UTC on 7 August, 12 minutes of EU call failures on 17 August and a white-label login issue on 7 September. We count the nearly three hours of webhook failures as one major (10). Concurrency and calls-per-second limits are set per contract and no numbers are published (0). The docs say call creation can return 429 on bursts, with no Retry-After, backoff or idempotency guidance found (5 of 15). No SLA published (0). The Platform API is generally available (10).); Vaani Developer Platform 28 (Graded on the hosted REST API at api.vaanivoice.ai. No status page. status.vaani.dev and status.vaanivoice.ai don't resolve, and neither the site nor the docs link one (0). With no history to read, 5. No request rate limits are published. The docs give 2 concurrent calls on pay as you go and a per-organisation campaign concurrency cap, so partial credit (5). The SDK raises `RateLimitError` on 429 and the MCP client retries once after 600 ms, but no Retry-After, backoff guidance or idempotency key for call creation is documented (3). The pricing table lists a 99.50 per cent uptime SLA on both plans, but no SLA document or service credits were found and the terms supply the service "as-is" with no warranties, so half (5). The API is version 2.0.0 and isn't labelled beta (10). 0+5+5+3+5+10 = 28.)
- Maintenance & community, Synthflow API + MCP +9: Synthflow API + MCP 68 (Changelog entry on 1 October 2026 (30). Ten entries between 7 September and 1 October (20). Public changelog, support we didn't test (10 of 15 for a closed service). No official SDK packages, only an MCP server and plugins (5 of 15). No packages to assess (3 of 10).); Vaani Developer Platform 59 (vaani-research-mcp 0.1.1 on 2026-10-14 (30). In the last 90 days, vaani-sdk 0.3.1 on 28 September and three npm versions (0.0.0-stage, 0.1.0, 0.1.1) within 40 minutes on 14 October. No dated changelog, so half (10 of 20). A closed service with no public changelog, issue tracker or community channel found. Contact is hello@vaaniresearch.com and a booking link, and we didn't test whether they answer. The MCP repository on GitHub couldn't be read from this session (4 of 15, the closed-service reading). A current official Python SDK, released seven times since April 2026. The MCP server isn't in the official MCP registry (10 of 15). The SDK's sdist ships its tests and current httpx and pydantic dependencies, and the MCP package runs its tests before publishing, but no public CI was found and the SDK has no repository (5 of 10). 30+10+4+10+5 = 59.)