# Vocily AI > Vocily AI is a hosted voice-agent platform from Bengaluru for phone calls, WhatsApp and website voice and chat, aimed at Indian languages. Its REST API builds and publishes agents, places outbound calls and reads back transcripts, recordings and costs. - Canonical: https://www.anchorterminal.com/tools/vocily - Markdown: https://www.anchorterminal.com/tools/vocily.md (~7,800 tokens) - Slim: https://www.anchorterminal.com/tools/vocily.min.md (~1,880 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/vocily.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade D · 53.8/100 · rank #540 of 722 · #8 in Conversational voice agents · not agent-ready · confidence medium** ## Assessment The REST API is documented in detail for a product a few months old, with an OpenAPI 3.1 file, required idempotency keys on calls, a Retry-After header on 429 and signed webhooks. No status page, SLA, SDK or security programme was found, and two releases in September 2026 removed fields under `/v1` on the day they were announced. ## Facts | Field | Value | | --- | --- | | Vendor | Vocily AI Private Limited (https://vocily.ai) | | Kind | HTTP API | | Category | Conversational voice agents (https://www.anchorterminal.com/categories/voice-agents) | | Transport | HTTP | | Endpoint | `https://api.vocily.ai` | | Auth | API key · A Bearer API key (`vk_...`) created in the dashboard under Developers, API Keys, shown once and revocable there. A key is bound to one workspace and reaches the whole public API for it. Billing, team members, account settings and key management answer 403 to any key. Keys have no scopes to configure, although the error table names an `agents:publish` permission for making a version live. Webhooks are signed with HMAC-SHA256 and a timestamp, with two signatures sent during a secret rotation. Access is self-serve after an email-verified signup. | | Pricing | Pay per use ($8 / mo) · Prepaid wallet with no monthly fee, billed in rupees or US dollars as chosen at signup, each with its own price list. Voice starts at ₹3.10 or $0.041 a connected minute (speech-to-text, model, voice and a $0.03 platform fee), and telephony is free on your own Plivo or VoBiz account or $0.004 a minute in 30-second pulses on a rented number. Chat is charged per model reply from $0.001. A new organisation gets ₹200 or $2 of credit with no card. Ten concurrent calls are included and a pack of two more is $8 a month (https://vocily.ai/pricing). | | x402 | No · No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (checked 2026-10-08). | | Licence | Proprietary service under Vocily's terms of service. No open-source code or published package was found | | Docs | https://docs.vocily.ai | | llms.txt | https://docs.vocily.ai/llms.txt | | Last release | 2026-09-30 | | Surface graded | The public REST API at https://api.vocily.ai/v1 (54 operations) with its webhooks. The dashboard, the WhatsApp tooling and batch campaigns are outside it | | Architecture | Pipeline of a transcriber, a language model and a voice, each chosen per agent, with an optional backup from a different provider for each stage. No speech-to-speech mode was found in the docs | | Models | Speech-to-text from Soniox, Deepgram (Nova 2, Nova 3, Flux) and Sarvam Saaras v4, the default. Nine language models from OpenAI, Google and Sarvam. Voices from Vocily's own engine, Smallest, Sarvam, Cartesia and ElevenLabs (https://vocily.ai/pricing) | | Languages | The docs list 12 Indic languages (Assamese, Bengali, Gujarati, Hindi, Kannada, Malayalam, Marathi, Odia, Punjabi, Tamil, Telugu, Urdu), three English variants and eight others. The site says 17+ Indian languages with code-mixing | | Telephony | Your own Plivo or VoBiz account, or a number rented from Vocily at $5 or ₹499 a month. Indian numbers need a compliance filing. Inbound and outbound, with call transfer | | Tool calling | Built-in hold, end call, transfer and WhatsApp template tools, custom HTTP tools with saved credentials, Cal.com booking and knowledge bases. Custom tools are built in the dashboard, not through the API | | API coverage | Agents with drafts, versions, publish and make-live, calls, recordings, chats, knowledge bases, caller memory, post-call analysis, the website widget, catalogues of models, voices and languages, and text to speech | | Rate limits | 300 requests a minute per key. Ten concurrent calls per organisation, five outbound and five inbound, with usage in `X-Vocily-Concurrency-Limit` and `X-Vocily-Concurrency-Used` on every response | | Errors | JSON with a `detail.code` reason and a message, a published table of reason codes by status, and a 422 that lists every invalid field. Every response has an `X-Request-ID` | | Webhooks | Five `call.*` events per agent, signed with HMAC-SHA256, sent at least once with up to three attempts (0 s, 2 min, 15 min). Endpoints are set in the dashboard | | Free tier | ₹200 or $2 of credit once the owner's email is verified, no card. Top-ups from ₹500 or $5, with 18 per cent GST on rupee purchases | | Data retention | Recordings are kept for the life of the account and deleted on request, per the pricing page. Saving call audio and transcripts is a per-agent setting, on by default. The privacy policy states no period | | SDKs and MCP | None found. The docs give cURL, Python requests and Node fetch examples. The marketing site lists SDKs and an MCP server that the docs don't mention | | Capabilities | voice.agent, voice.pipeline, voice.tools, voice.telephony | | Tags | hosted, india, openapi, llms-txt, webhooks, pipeline, telephony, whatsapp, prepaid, new | | JSON | https://www.anchorterminal.com/api/v1/tools/vocily.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 40 | 8.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 90 | 14.6 | | Agent ergonomics | 13% | 16.2 | 84 | 13.7 | | Security & auth | 14% | 17.5 | 46 | 8.1 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 61 | 5.3 | | Transparency & trust (editorial 34, provenance 59) | 7% | 8.8 | 47 | 4.1 | | Negative events | up to −15 | up to −15 | 2026-09-23 and 2026-09-25, -3. Two releases removed fields and routes under `/v1` with no notice period, including `tools` on the agent body, `call_type`, `?skip=` and `?offset=`, and the `/widgets` collection routes. The 23 September note says there is no window in which both shapes work. The API reference says fields are never removed or renamed within a version. Documented the same day with migration tables, so the deduction is reduced (https://docs.vocily.ai/developers/changes.md) 2026-10-08, -2. The developer page on the marketing site lists Fern-generated Python and TypeScript SDKs, an MCP server, API key routes with rotation, webhook endpoint routes, `POST /v1/agents/{id}/chat` and events such as `transcript.ready`. The docs and the OpenAPI file have none of these, keys and webhook endpoints are dashboard-only, and no package was found on npm or PyPI (https://vocily.ai/platform/api-tools and https://docs.vocily.ai/developers/api-reference.md) | -5 | | **Total** | | | | **53.8 → D** | ### Why each score - Reliability 40: Graded on the public REST API at api.vocily.ai, read as a hosted service. No status page found. status.vocily.ai doesn't resolve and neither the site nor the docs link one (0). No readable incident history (5). The limit is published as 300 requests a minute per key, with ten concurrent calls per organisation reported in response headers (15). A 429 carries `Retry-After` and `X-RateLimit` headers, capacity refusals carry `Retry-After`, and `POST /v1/calls` requires an `Idempotency-Key` and replays the original call on a retry (15). No SLA found. The terms say availability isn't guaranteed, and the Enterprise tier mentions only agreed support response commitments (0). The docs don't label the API beta, but four dated releases between 23 and 30 September 2026 changed the `/v1` contract, three of them with removals or changed codes, the API root reports version 0.1.0, and the terms still allow for beta and pre-launch service (5 of 10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 90: A public OpenAPI 3.1 file with 54 operations at docs.vocily.ai/developers/openapi.json (25). llms.txt, llms-full.txt and a Markdown copy of every page (10). Pages say what each route is for and what to use instead, such as webhooks over polling and dashboard batches over a loop of calls, though some operation titles are generated names such as Create Kb (16 of 20). Bodies refuse unknown fields and carry ranges and enums, but list filters such as `status` are plain strings and `variables` and `metadata` are free-form (12 of 15). 196 examples in the spec, a reason-code table by status and a 422 that lists every invalid field (15). The `/v1` prefix and a dated API changes page, which starts on 23 September 2026 and records removals made under `/v1` against the reference's own rule that fields are never removed within a version (12 of 15). - Agent ergonomics 84: List calls take `limit` from 1 to 100, default 20, and return the transcript only with `include=transcript` (20 of 25). Every growing list uses the same cursor envelope, and calls filter by agent, status, direction, origin and date. The bounded lists return bare arrays (18 of 20). Errors carry a machine-readable `detail.code`, a field path on validation failures and an `X-Request-ID` (20). `Idempotency-Key` is required on call creation, agent edits accept `If-Match` on a document revision, and the bulk memory erase previews unless `dry_run` is false. Other writes have no idempotency key (18 of 20). A call needs only `agent_id` and `to_number` and an agent only `name`. No SDK was found in the docs, on npm or on PyPI (8 of 15). - Security & auth 46: Bearer keys are shown once, revocable in the dashboard and bound to one workspace, and they can't reach billing, members or key management. There are no scopes to set and no rotation route, and webhooks are HMAC-signed with a timestamp and a rotation overlap (22 of 30). No read-only key. Spending and contractual actions stay in the dashboard, a version answers calls only after publish and make-live, and the memory erase previews by default (10 of 20). Transcripts and caller speech are untrusted content, and the API docs have no prompt-injection guidance. The site describes topic fencing and an empty-knowledge-base guard (4 of 15). Each call keeps a record with cost and version, webhooks have a delivery log and every response a request id, but we found no audit log of account or key actions (8 of 15). No security.txt, disclosure policy, bug bounty or certification. The compliance page says Vocily doesn't claim certification, and the privacy policy states encryption in transit and at rest (2 of 20). - Payments & pricing 40: No x402, MPP or L402 (0 of 40). Per-minute prices for each speech-to-text model, language model and voice, the platform fee, telephony, per-reply chat prices and WhatsApp fees are public without a login in rupees and US dollars (20). A new organisation gets ₹200 or $2 of credit, and the pricing page says no card (20). Access starts with a browser signup and email verification, and API keys can only be created in the dashboard (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 61: The latest dated API change is 30 September 2026 (30). Four dated entries, on 23, 25, 27 and 30 September (20). A public change log, a Discord server and a founder email address are the channels found, and we didn't test whether they answer (8 of 15 for a closed service). No official SDK found, although the marketing site lists Python and TypeScript SDKs (0 of 15). There is no package to assess. The OpenAPI file was last modified on 1 October 2026 (3 of 10). - Transparency & trust 47: A closed service. The terms (10 June 2026) name no legal entity or governing law, still describe a possible beta, and say paid plans may come later while prices are live (10 of 30). The privacy policy (3 September 2026) is written mainly around WhatsApp data and gives no retention period. The pricing and compliance pages say recordings are kept for the life of the account and deleted on request, and audio and transcript storage are per-agent settings. No DPA found (12 of 30). The reference promises additive changes within `/v1`, but removals shipped on 23 and 25 September 2026 with same-day notes and migration tables and no notice period (6 of 20). The privacy policy mentions vetted providers without naming them. Model providers and carriers can be read from the pricing page and docs, and no data location is documented (6 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (22 items): https://www.anchorterminal.com/fixes/vocily.md (JSON https://www.anchorterminal.com/fixes/vocily.json) ### What we couldn't check - We made no authenticated call, so rate-limit headers, idempotent replay and error bodies are as documented, not as observed. An unauthenticated request returned 401 with an `x-request-id` header. - Whether the Python and TypeScript SDKs and the MCP server listed on vocily.ai/platform/api-tools exist anywhere. They aren't in the docs, and npm and PyPI have no package named vocily. - What the `agents:publish` permission in the error table refers to, given that the reference says keys have nothing to configure. - Where call recordings and transcripts are stored. The compliance page says the region is chosen by the customer, and the docs and privacy policy name no location. - The sub-processor list and any DPA. Neither was found on the site. - Whether support on Discord or by email answers. We didn't test it. - The legal entity is taken from the registrant field of the vocily.ai domain record. No page on the site names it, and we didn't check a company registry. - The scout's note described a REST API for batches and a realtime API for conversation events. Batch campaigns are dashboard-only per the API reference, and the docs have webhooks, not a realtime API. The app now lives at app.vocily.ai, with app.vocily.com redirecting to it. ### Sources - API reference (auth, pagination, idempotency, rate limits, errors, versioning): (seen 2026-10-08) - OpenAPI 3.1 file: (seen 2026-10-08) - API changes: (seen 2026-10-08) - docs index: (seen 2026-10-08) - webhooks overview: (seen 2026-10-08) - webhook signature verification: (seen 2026-10-08) - Test Number limits: (seen 2026-10-08) - voice call pricing: (seen 2026-10-08) - wallet and welcome credits: (seen 2026-10-08) - call lines and capacity packs: (seen 2026-10-08) - WhatsApp pricing: (seen 2026-10-08) - roles and permissions: (seen 2026-10-08) - pricing page: (seen 2026-10-08) - home page: (seen 2026-10-08) - developer page on the marketing site: (seen 2026-10-08) - compliance page: (seen 2026-10-08) - terms of service: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - API root and unauthenticated response: (seen 2026-10-08) - domain record for vocily.ai: (seen 2026-10-08) - domain record for vocily.com: (seen 2026-10-08) ## Who's behind it (provenance 59/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | VOCILY AI PRIVATE LIMITED | 20/20 | | Domain age | vocily.ai, registered 2026-07-12 (under a year) | 0/15 | | Endpoint on the vendor's domain | api.vocily.ai | 15/15 | | Terms of service | read, states 4 of the 7 things a reader expects | 7.4/10 | | Privacy policy | read, states 4 of the 8 things a reader expects | 7/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | RDAP for vocily.ai gives a registration date of 2026-07-12 and VOCILY AI PRIVATE LIMITED as registrant. vocily.com was registered on 2026-01-27 through Squarespace Domains with no registrant shown, and it redirects to vocily.ai. app.vocily.com, which the site links, redirects to app.vocily.ai. The terms (last updated 10 June 2026) and the privacy policy (last updated 3 September 2026) refer only to Vocily and name no legal entity, address or governing law. The site footer says Vocily AI, Bengaluru, India. The legal name comes from the registrant field of the vocily.ai domain record. The website, the docs (docs.vocily.ai), the API (api.vocily.ai) and the app (app.vocily.ai) are all on vocily.ai. https://vocily.com answers 307 to https://vocily.ai/ and https://app.vocily.com answers 308 to https://app.vocily.ai/. No status page was found. status.vocily.ai doesn't resolve and neither the site nor the docs link one. https://vocily.ai/.well-known/security.txt and https://vocily.ai/security.txt return 404. The only contact given in the terms and privacy policy is founder@vocily.ai. The terms still describe the service as possibly in beta or pre-launch and say paid plans may be introduced later, while the pricing page lists live prices. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://vocily.ai/terms), read 2026-10-08, dated 2026-06-10, states 4 of the 7 things a reader expects. - Gives the date it was last updated. Last updated 2026-06-10. - Not found in the text. Names the governing law or courts. - States a limit on its liability. Capped at the fees paid in the 3 months before the claim. - Not found in the text. Says how changes to the terms are announced. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). Total liability is capped at the amounts paid in the three months before the event, or 10,000 Indian rupees if nothing was paid. "To the fullest extent permitted by law, our total liability for all claims relating to the service will not exceed the amounts you paid to Vocily for the service in the three months before the event giving rise to the claim, or INR 10,000 if you have not paid Vocily during that period." - Also in the text (2026-10-08). The customer is responsible for the instructions, credentials, permissions and effects when its agent acts in another system. "If you configure an agent to call an external API, book appointments, update records, transfer calls, send messages, send webhooks, or otherwise act in another system, you are responsible for the instructions, credentials, permissions, request payloads, and effects of those actions." - Also in the text (2026-10-08). The terms forbid misleading people into believing an AI agent is a human when disclosure is required or appropriate. "Misleading people into believing an AI agent is a human when disclosure is required or appropriate." **Privacy policy** (https://vocily.ai/privacy), read 2026-10-08, dated 2026-09-03, states 4 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2026-09-03. - Not found in the text. Says what personal data is collected. - Says how long data is kept. For as long as needed, with no period named. - Not found in the text. Says whether personal data is sold or shared for advertising. - Not found in the text. Says what rights people have over their data. - Not found in the text. Gives a privacy contact. - Also in the text (2026-10-08). Vocily relies on outside providers to run the service, including AI model providers used to generate replies. "We rely on a small number of vetted providers strictly to run the service — for example, cloud hosting and infrastructure, and AI model providers used to generate replies." ## Live (updated 2026-10-08 19:53 UTC) - Right now: up, HTTP 200, 554 ms, checked 2026-10-08 19:53 UTC (get on `https://api.vocily.ai`) - Uptime 24h 100.0% (27 probes) · 30 days 100.0% (27 probes) · p50 572 ms · p95 651 ms - Watching changelog - Watching pricing - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/vocily.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Voice, lowest-priced configuration | $0.041 | per minute of call | Soniox, GPT-5 Nano, Vocily voice and the $0.03 platform fee. ₹3.10 for a rupee organisation. Telephony extra on a rented number | | Telephony on a number rented from Vocily | $0.004 | per minute of call | billed in 30-second pulses, doubled while a transfer is connected. Free on your own carrier account | | Web chat or WhatsApp AI reply, GPT-5 Nano | $0.001 | per message | per model reply, up to $0.02 on GPT-5.6 Terra | | WhatsApp utility template, platform fee | $0.0004 | per message | Meta's own charges are paid to Meta separately | | Capacity pack, two more concurrent calls | $8 | per month (plan) | ten concurrent calls are included at no monthly fee | | Rented Indian phone number | $5 | per month (plan) | ₹499 for a rupee organisation | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - OpenAPI 3.1 file with 54 operations, plus llms.txt and a Markdown copy of every docs page - `POST /v1/calls` requires an `Idempotency-Key`, and a retry returns the original call - 429 responses carry `Retry-After` and `X-RateLimit` headers, with a published limit of 300 requests a minute per key - Webhooks are signed with HMAC-SHA256 and a timestamp, with a five-minute replay window - Every component price is public in rupees and US dollars, and signup credit needs no card ## Weaknesses - No status page, incident history or SLA was found - Fields and routes were removed under `/v1` on 23 and 25 September 2026 on the day of the announcement - The marketing site lists SDKs, an MCP server and key management endpoints that the docs don't have - No security.txt, disclosure policy, bug bounty or certification was found - The terms and privacy policy name no legal entity, sub-processor or retention period ## Before you call it (notes for agents) 1. Send a fresh UUID in `Idempotency-Key` on every `POST /v1/calls`. The API refuses the request without it 2. Pass a `from_number` the workspace holds. The shared Test Number returns 403 from the API 3. Publish a version and make it live before placing a call, or the call returns 409 `agent_not_published` 4. Branch on `detail.code`, falling back to the top-level `code`. A 429 body is flat, so read `Retry-After` 5. Read `currency` on every call and chat record. Costs are in rupees or dollars depending on the organisation ## Connect First request: ```bash curl https://api.vocily.ai/v1/agents \ -H "Authorization: Bearer vk_your_key_here" ``` Through letme (picks today, calling later): https://letme.dev/vocily. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | ElevenLabs Agents API + MCP | BB | 71.3 | 113 | voice.agent, voice.pipeline, voice.tools, voice.telephony | no | https://www.anchorterminal.com/tools/elevenlabs-agents.md | | Retell AI API + MCP | B | 69.1 | 167 | voice.agent, voice.pipeline, voice.tools, voice.telephony | no | https://www.anchorterminal.com/tools/retell-ai.md | | Bland AI API + MCP | B | 63.8 | 291 | voice.agent, voice.pipeline, voice.tools, voice.telephony | no | https://www.anchorterminal.com/tools/bland-ai.md | | Vapi API + MCP | B | 63.5 | 308 | voice.agent, voice.pipeline, voice.tools, voice.telephony | no | https://www.anchorterminal.com/tools/vapi.md | | Hume EVI (Empathic Voice Interface) | C | 56.7 | 486 | voice.agent, voice.pipeline, voice.tools, voice.telephony | no | https://www.anchorterminal.com/tools/hume-evi.md | | Bolna API + MCP | D | 52.6 | 561 | voice.agent, voice.pipeline, voice.tools, voice.telephony | no | https://www.anchorterminal.com/tools/bolna.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The product is new. vocily.ai was registered on 12 July 2026, the terms are dated 10 June 2026, and the API change log starts on 23 September 2026 (source: ) - The public API has 54 operations in an OpenAPI 3.1 file. Creating an API key, buying or connecting a number, setting a webhook URL, WhatsApp setup, HTTP tools and batch campaigns stay in the dashboard (source: ) - `POST /v1/calls` refuses a request without an `Idempotency-Key` header, and a retry with the same key returns the original call with `Idempotent-Replay: true` (source: ) - The releases of 23 and 25 September 2026 removed fields and renamed routes under `/v1` on the day they were announced, although the reference says fields are never removed or renamed within a version (source: ) - The shared Test Number can't be used from the API (403 `test_number_not_allowed`), so an API call needs a number from your own Plivo or VoBiz account or one rented from Vocily, and a rented Indian number needs an accepted compliance filing (source: ) - The marketing site lists Python and TypeScript SDKs and an MCP server. Neither appears in the docs, and no package was found on npm or PyPI under the name vocily (source: ) ## Compare - [Bland AI API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/bland-ai-vs-vocily.md): B 63.8 vs D 53.8 - [Bolna API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/bolna-vs-vocily.md): D 52.6 vs D 53.8 - [Deepgram Voice Agent API vs Vocily AI](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vocily.md): B 68.1 vs D 53.8 - [ElevenLabs Agents API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vocily.md): BB 71.3 vs D 53.8 - [Hume EVI (Empathic Voice Interface) vs Vocily AI](https://www.anchorterminal.com/compare/hume-evi-vs-vocily.md): C 56.7 vs D 53.8 - [Retell AI API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/retell-ai-vs-vocily.md): B 69.1 vs D 53.8 - [Synthflow API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/synthflow-vs-vocily.md): D 51.1 vs D 53.8 - [Ultravox Realtime API vs Vocily AI](https://www.anchorterminal.com/compare/ultravox-vs-vocily.md): C 58.5 vs D 53.8 - [Vapi API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/vapi-vs-vocily.md): B 63.5 vs D 53.8 - [Vocily AI vs Vogent API](https://www.anchorterminal.com/compare/vocily-vs-vogent.md): D 53.8 vs D 47.1 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on vocily.ai or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "vocily", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Vocily AI on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Vocily AI on Anchor Terminal](https://www.anchorterminal.com/badges/vocily.svg)](https://www.anchorterminal.com/tools/vocily) ``` Plain link: ```html Vocily AI on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Vocily AI is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/vocily-dark.png - Light: https://www.anchorterminal.com/assets/share/vocily-light.png