# PlaceCall vs Vaani Developer Platform (slim)

> PlaceCall scores 60.2 (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/placecall-vs-vaani-voice.md (~6,200 tokens) · this version ~3,830 tokens · JSON https://www.anchorterminal.com/compare/placecall-vs-vaani-voice.json · canonical https://www.anchorterminal.com/compare/placecall-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)

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

- PlaceCall: C 60.2, rank #556 of 1266 · https://www.anchorterminal.com/tools/placecall.min.md
- Vaani Developer Platform: E 44.6, rank #1084 of 1266 · https://www.anchorterminal.com/tools/vaani-voice.min.md
- PlaceCall, good for An agent that needs a phone call to a US business done for it, such as checking stock, hours or a quote, or booking and cancelling, with an outcome and transcript at the end. Ahead on Reliability, 45 against 28; Schema & documentation, 82 against 57; Agent ergonomics, 81 against 64; Security & auth, 60 against 44; Payments & pricing, 50 against 22; Maintenance & community, 64 against 59; Transparency & trust, 50 against 42. Also Free to start without a card.
- 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 | PlaceCall | Vaani Developer Platform |
| --- | --- | --- |
| Reliability (16%) | 45 | 28 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 82 | 57 |
| Agent ergonomics (13%) | 81 | 64 |
| Security & auth (14%) | 60 | 44 |
| Payments & pricing (10%) | 50 | 22 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 64 | 59 |
| Transparency & trust (7%) | 50 | 42 |

| Fact (where they differ) | PlaceCall | Vaani Developer Platform |
| --- | --- | --- |
| Vendor | VOYGR Tech, Inc. | Vaani AI Research Private Limited |
| Hosted endpoint | `https://api.voygr.tech/mcp` | `https://api.vaanivoice.ai` |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Licence | Proprietary service under VOYGR's API Terms of Service. The skill, plugin manifests and AGENTS.md in voygr-tech/placecall are MIT | 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 | 4 | 9 |
| Read-only variant documented | no | yes |
| MCP registry | `io.github.voygr-tech/placecall` | not listed |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | couldn't be read | no date given |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | none | 14 npm/wk, 19 PyPI/wk |
| Agent reviews | 3.5/5 (4) | none |

Why the edge:
- Payments & pricing, PlaceCall +28: PlaceCall 50 (No x402, MPP or L402. A 402 from POST /calls is an insufficient-credit error with a checkout link (0). Per-call prices are public, $0.10 for a call that reaches a person and $0.05 for a place suggestion, with credit packs and a public /v1/pricing endpoint (20). A new key includes 2,500 credits, 250 calls, with no card (20). A key is requested with a plain POST of a name and email and arrives by email, with no browser step we could find, so an agent with its own inbox can get one. The MCP route needs a person to sign in, and buying credits goes through Stripe checkout (10 of 20). 0 + 20 + 20 + 10 = 50.); 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.)
- Schema & documentation, PlaceCall +25: PlaceCall 82 (A public OpenAPI 3.1 document at api.voygr.tech/openapi.json with servers and the API-key scheme declared, 22 operations and 49 schemas (25). llms.txt and llms-full.txt, a Markdown rendering of the whole spec (10). Operation descriptions say when to use each route and what not to do, such as not waiting for a transcript after `recording_declined` and not polling the rebuild endpoint. POST /v1/places/suggest and the recording download are in the README but not in the spec (16 of 20). Enums on language, intent, kind and ask_user_mode and length limits on the notice fields, but `slots` is a free-form object whose required keys are listed only in prose (11 of 15). Request examples for both call shapes and example bodies for every documented error (15). The spec is versioned 1.0.0 and the terms carry a date, but we found no API changelog (5 of 15). 25 + 10 + 16 + 11 + 15 + 5 = 82. The MCP tool definitions sit behind sign-in and were not read.); 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.)
- Reliability, PlaceCall +17: PlaceCall 45 (Read with the hosted lines. No status page was found, and status.voygr.tech does not resolve (0). With no published history the incident line takes 5. Rate limits are published with numbers, 10 requests a second and 120 a minute for every self-serve key, plus one concurrent call and 25 calls a day on a free key (15). A 429 carries Retry-After when returned, a 503 for maintenance carries `resume_at`, and POST /calls takes an Idempotency-Key whose replay returns the stored response with `Idempotent-Replayed: true` (15). No SLA for any tier (0). Nothing on the docs, spec or product page calls the API beta or preview (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.); 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.)
- Agent ergonomics, PlaceCall +17: PlaceCall 81 (Four MCP tools per the README, so context cost is small (25). GET /calls takes `limit` up to 1,000 and leaves out transcripts, and the event stream resumes from an `after_event_id` cursor, but we found no cursor or filters on the call list (12 of 20). Errors carry an `error_code` and a `hint`, a 422 for missing slots lists each one with a `suggested_question`, and a 402 names the credits needed (20). Idempotency keys on POST /calls with a 409 on a changed body, a cancel documented as safe to retry, and webhook retries deduplicated on `Webhook-Id`. MCP tool annotations were not readable (16 of 20). A call needs only `target_phone` and `brief`, with `language` defaulting to `auto`. No SDK packages in any language, only plugins, a skill and the spec (8 of 15). 25 + 12 + 20 + 16 + 8 = 81.); 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.)
- Security & auth, PlaceCall +16: PlaceCall 60 (Two credential models. The REST API uses one emailed key per account with no scopes and no self-serve rotation, while the MCP server uses OAuth with dynamic client registration, PKCE and two scopes (calls:place, places:read). We read the mix as plain revocable keys (20 of 30). No read-only key. The skill tells the agent to confirm the number and the brief with the user before dialling, and an owner can set a concurrent-call limit (10 of 20). The tool returns what people say on calls. llms.txt and the skill both say to treat transcripts, summaries and mid-call questions as data, never as instructions (14 of 15). Each call can be listed and read back with its transcript, the notice it spoke and its charge, and /v1/usage shows the balance. We found no account audit log (11 of 15). SECURITY.md in the repository asks for reports by email. No security.txt, bug bounty or certification was found (5 of 20). 20 + 10 + 14 + 11 + 5 = 60.); Vaani Developer Platform 44 (Plain revocable API keys, shown once, several active at a time and rotated by creating a new key and deleting the old one. Every key reaches the whole workspace, with no scoped, read-only or per-agent keys (20). Campaign webhooks are signed with HMAC-SHA256 over a timestamp and the body, with a five-minute replay window in the example (+2). The live-captions URL carries a call-bound token in the query string for 24 hours by default, the documented way for browsers to connect, so 3 off as a judgement call, less than the full 10 because it isn't the account key (19 of 30). The MCP server has a read-only mode and destructive annotations, and its docs, tool descriptions and bundled prompt say to confirm the number and agent with the user before a call. The API itself has no read-only key and nothing stops a call without confirmation (12 of 20). The tool returns transcripts, summaries and entities drawn from callers' speech. No guidance on treating them as untrusted data was found. Agent guardrails exist for the voice agent's own replies (3 of 15). Each call keeps a record in call history and call details, and keys are labelled so calls can be traced to a key, but no account or key audit log is documented (7 of 15). No security.txt (404 on both domains), disclosure policy, bug bounty or certification. vaaniresearch.com marks its security standards "In Progress", the pricing page lists HIPAA compliance on Enterprise with no report or BAA found, and the privacy policy promises breach notice in line with applicable law (3 of 20). 19+12+3+7+3 = 44.)
- Transparency & trust, PlaceCall +8: PlaceCall 50 (Closed service with dated API terms, and the skill and manifests are MIT (15). The API terms and the privacy policy agree on 90 days' retention for recordings and transcripts. A DPA is available only by negotiation, the privacy policy names VOYGR an independent controller of call recipients' data for its own purposes, and it allows de-identified data to be used and shared (20 of 30). The terms reserve the right to change or remove endpoints with or without notice and promise no backward compatibility. One spec field is marked deprecated with no date (3 of 20). No subprocessor list or data locations. The privacy policy names only categories of vendors (5 of 20). 15 + 20 + 3 + 5 = 43.); 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.)