# Gemini Live API vs Vaani Developer Platform (slim)

> Gemini Live scores 57.1 (C) 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/gemini-live-vs-vaani-voice.md (~6,100 tokens) · this version ~3,630 tokens · JSON https://www.anchorterminal.com/compare/gemini-live-vs-vaani-voice.json · canonical https://www.anchorterminal.com/compare/gemini-live-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)

Gemini Live API scores 57.1 (C) on agent readiness against Vaani Developer Platform's 44.6 (E), and leads in every scored category. Both do voice agents.

- Gemini Live API: C 57.1, rank #720 of 1266 · https://www.anchorterminal.com/tools/gemini-live.min.md
- Vaani Developer Platform: E 44.6, rank #1084 of 1266 · https://www.anchorterminal.com/tools/vaani-voice.min.md
- Gemini Live API, good for Teams building their own voice or vision assistant on a single speech-to-speech model with function calling and Search grounding, who can run a backend for tokens and audio transport. Ahead on Reliability, 41 against 28; Schema & documentation, 66 against 57; Agent ergonomics, 69 against 64; Payments & pricing, 40 against 22; Maintenance & community, 83 against 59; Transparency & trust, 72 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. Also Runs on your own machine.

| Category | Gemini Live API | Vaani Developer Platform |
| --- | --- | --- |
| Reliability (16%) | 41 | 28 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 66 | 57 |
| Agent ergonomics (13%) | 69 | 64 |
| Security & auth (14%) | 48 | 44 |
| Payments & pricing (10%) | 40 | 22 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 59 |
| Transparency & trust (7%) | 72 | 42 |

| Fact (where they differ) | Gemini Live API | Vaani Developer Platform |
| --- | --- | --- |
| Vendor | Google | Vaani AI Research Private Limited |
| Hosted endpoint | `https://generativelanguage.googleapis.com/v1beta` | `https://api.vaanivoice.ai` |
| Transports | HTTP | HTTP, stdio |
| Pricing | Freemium | Pay per use |
| Licence | Proprietary service under the Gemini API Additional Terms of Service. The Python and JavaScript SDKs are Apache-2.0 | 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 | none | 9 |
| Read-only variant documented | no | yes |
| Last release | 2026-09-15 | 2026-10-14 |
| Terms last updated | 2026-04-28 | no date given |
| Privacy policy last updated | 2026-10-01 | no date given |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | 29.5M npm/wk, 34.1M PyPI/wk | 14 npm/wk, 19 PyPI/wk |

Why the edge:
- Transparency & trust, Gemini Live API +30: Gemini Live API 72 (Closed service with clear terms, SDKs under Apache-2.0 (15 of 30). The terms, pricing page and zero data retention page agree that free-tier content improves Google products and paid content does not. The terms say abuse logs are kept for a limited period and the abuse monitoring page gives 55 days. Session state is kept up to 24 hours when resumption is on, and Search grounding data 30 days (20 of 30). A deprecations table gives earliest shutdown dates and replacements, with 17 November 2026 for the two older Live previews, about nine weeks after the replacement shipped, and no stated minimum notice (15 of 20). The terms say data may be stored transiently or cached in any country where Google has facilities. The Data Processing Addendum applies to paid services, and no sub-processor list was read (5 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.)
- Maintenance & community, Gemini Live API +24: Gemini Live API 83 (`gemini-3.8-live` went generally available on 15 September 2026, 23 days before the check (30). Three dated Live entries in the last 90 days, the robotics streaming model on 30 July, `gemini-3.5-transcribe-live` on 26 August and the 3.8 Live models on 15 September (20). Closed service with a changelog updated several times a month. Support channels were not tested (10 of 15). Current official SDKs, `google-genai` v2.29.0 and `@google/genai` v2.28.0, both tagged 7 October with about weekly tags since August (15). Apache-2.0 SDKs with type-check workflows in the Python repository and Node 20 or later stated. CI results were not read (8 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.)
- Payments & pricing, Gemini Live API +18: Gemini Live API 40 (No x402, MPP or L402 (0 of 40). Per-token prices with per-minute equivalents are published without a login (20). The Live models are free of charge on the free tier, and the billing guide says new accounts start there with billing linked only to move to the paid tier (20). A key needs a Google account and AI Studio, so a person signs up in a browser (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.)
- Reliability, Gemini Live API +13: Gemini Live API 41 (Graded as a hosted API on the Gemini Developer API. A status page exists at aistudio.google.com/status, but it is drawn by script and we could read no components or history on 8 October (10 of 20, and 5 of 30 for the incident line with no readable record). Session limits are published, 15 minutes for audio and 2 for audio with video without compression, connections of about 10 minutes, and spend limits of $10, $50 and $200 per 10 minutes on Tiers 1 to 3. Per-model request limits and concurrent sessions are shown only in AI Studio (8 of 15). The server sends a GoAway message with `timeLeft` before closing, session resumption handles last 2 hours, and the troubleshooting guide gives exponential backoff with jitter for 429 and 503 (12 of 15). No SLA found for the Developer API (0). `gemini-3.8-live` is stable and generally available since 15 September, but the endpoint is `v1beta`, ephemeral tokens are in preview and three docs pages still label the Live API a preview (6 of 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.)
- Schema & documentation, Gemini Live API +9: Gemini Live API 66 (No AsyncAPI or similar file for the WebSocket messages was found. The keyless Discovery document (revision 20261006) types `auth_tokens.create` and five related schemas, `BidiGenerateContentSetup` among them, but not the client and server messages (8 of 25). llms.txt with a Markdown twin of every page (10). The capabilities guide, model comparison table and best practices page say when to use each model, voice activity mode and tool behaviour (16 of 20). The reference at ai.google.dev/api/live lists every message with field types, enums such as `ActivityHandling`, `TurnCoverage` and the sensitivity levels, and required marks, as tables and not as a schema (12 of 15). Python and JavaScript examples on every guide, but no list of WebSocket close codes or Live error responses was found (8 of 15). Dated changelog and versioned model names, less 3 because the tools page omits the 3.8 models, the overview says 70 languages where the capabilities guide lists 99, and preview banners remain after general availability (12 of 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.)
- Agent ergonomics, Gemini Live API +5: Gemini Live API 69 (Scored as an API. Context can be sized with sliding-window compression and a trigger token count, media resolution is configurable and `UsageMetadata` reports token counts (18 of 25). No lists to page. Output controls are turn coverage, optional transcription of either side and the compression window (12 of 20). Server signals an agent can act on are `interrupted`, `generationComplete`, GoAway and tool call cancellation, but there is no documented error catalogue for the socket (10 of 20). Session resumption makes reconnects safe, resuming does not spend a token use, and non-blocking function calls take `SILENT`, `WHEN_IDLE` or `INTERRUPT` scheduling. No idempotency guidance for tool side effects after an interruption (14 of 20). A session needs only a model and a response modality, voice activity detection is automatic, and there are official Python and JavaScript SDKs (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.)