{ "data": { "a": { "slug": "amazon-nova-sonic", "name": "Amazon Nova 2 Sonic", "vendor": "Amazon Web Services", "vendorUrl": "https://aws.amazon.com/ai/generative-ai/nova/speech/", "kind": "http-api", "category": "voice-agents", "summary": "Amazon Nova 2 Sonic is AWS's speech-to-speech model for voice agents on Amazon Bedrock. Clients stream audio and text events both ways over the `InvokeModelWithBidirectionalStream` API, with turn-taking, interruptions, asynchronous tool calls and multilingual voices.", "url": "https://www.anchorterminal.com/tools/amazon-nova-sonic", "markdownUrl": "https://www.anchorterminal.com/tools/amazon-nova-sonic.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/amazon-nova-sonic.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/amazon-nova-sonic.json", "dns": "amazon-nova-sonic.grade.anchorterminal.com", "repo": "https://github.com/aws-samples/amazon-nova-samples", "transports": [ "http" ], "packages": [ { "registry": "pypi", "name": "aws-sdk-bedrock-runtime" }, { "registry": "npm", "name": "@aws-sdk/client-bedrock-runtime" } ], "auth": "api-key", "authNotes": "AWS Signature Version 4 with IAM credentials or a role, scoped per model ARN by IAM policy. The Sonic quickstart signs with environment credentials. Whether Bedrock API keys work on the bidirectional stream wasn't confirmed. Access is self-serve once a person has an AWS account.", "pricing": "usage", "pricingNotes": "Billed per speech and text token on Bedrock on demand. The Nova and Bedrock pricing pages draw their price tables by script, so the figures weren't read on 6 November 2026. No model-specific free tier; new AWS accounts get up to $200 in Free Tier credits.", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Nova or Bedrock docs (checked 2026-11-06). Billing runs through the AWS account.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.aws.amazon.com/nova/latest/nova2-userguide/using-conversational-speech.html", "llmsTxt": "https://docs.aws.amazon.com/nova/latest/nova2-userguide/llms.txt", "capabilities": [ "voice.agent", "voice.speech-to-speech", "voice.tools", "voice.telephony" ], "tags": [ "official", "hosted", "usage-priced", "closed-source", "python", "typescript", "llms-txt", "streaming", "enterprise" ], "lastRelease": "2026-05-28", "graded": true, "anchor": { "graded": true, "score": 67.6, "grade": "B", "agentReady": false, "rank": 314, "ranked": true, "rankOf": 1486, "categoryRank": 6, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 50, "payments": 10, "reliability": 95, "schema": 75, "security": 77, "transparency": 79 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-06" }, "negative": 0, "verdict": "Nova 2 Sonic runs speech-to-speech conversations with asynchronous tools on Bedrock, with IAM scoping, no default storage of inputs and a 99.9 per cent SLA. Sessions cut off at 8 minutes, the Python SDK is pre-alpha, and the event payloads have no schema file. Prices are in a script-drawn table we couldn't read.", "bestFor": "Voice agents on AWS, call centres on Amazon Connect, teams that want IAM and in-account data handling.", "strengths": [ "No Bedrock event on the AWS Health history in the 90 days from 8 August 2026", "IAM scoping per model ARN with SigV4 and temporary credentials", "Bedrock stores no inputs or outputs by default, and Sonic isn't on the list of models kept for abuse review", "Asynchronous tool calls let the model keep speaking while a tool runs", "Telephony guides for Twilio, Vonage and Amazon Connect" ], "weaknesses": [ "Connections end after 8 minutes, so long calls need the session-continuation pattern", "The Python SDK for bidirectional streaming is pre-alpha and needs Python 3.12", "Sonic's event payloads are documented as examples, with no schema file", "20 concurrent sessions per Region, not adjustable through Service Quotas", "The March and May 2026 refreshes changed the model in place under the same ID" ], "agentNotes": [ "Plan a reconnect before 8 minutes and replay chat history (up to 200 KB) at the start of the new session", "Send session, prompt and content start events in order before any audio", "Make tool calls safe to repeat, since a reconnect can replay them", "Back off on `ThrottlingException` and stay within 20 concurrent sessions per Region", "Use the polyglot voices TIFFANY or MATTHEW when callers may switch language" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.6 } ], "editorialScores": { "ergonomics": 64, "maintenance": 50, "payments": 10, "reliability": 95, "schema": 75, "security": 77, "transparency": 64 }, "provenanceScore": 94, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install aws-sdk-bedrock-runtime" }, "letme": { "capability": "https://letme.dev/voice.agent", "tool": "https://letme.dev/amazon-nova-sonic" }, "sameCompany": [ "amazon-bedrock", "amazon-nova-embeddings", "amazon-bedrock-guardrails", "amazon-transcribe", "amazon-polly", "agentcore-memory", "agentcore-identity", "aws-secrets-manager", "agentcore-web-search", "aws-mcp-servers", "amazon-ses", "amazon-location", "amazon-translate", "amazon-ads-api", "amazon-creators-api" ], "area": "voice", "provenance": { "legalEntity": "Amazon Web Services, Inc.", "domain": "amazon.com", "domainRegistered": "1994-11-01", "domainNote": "The endpoint is on amazonaws.com, an AWS domain registered on 2005-08-18. The security.txt on aws.amazon.com expires on 2027-10-16.", "endpointOnVendorDomain": true, "terms": "https://aws.amazon.com/service-terms/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "https://health.aws.amazon.com/health/status", "changelog": "https://docs.aws.amazon.com/nova/latest/nova2-userguide/release-notes.html", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "The AWS Service Terms were last updated on 30 October 2026. Section 50.12 covers Amazon Bedrock, and Bedrock is not among the services section 50.3 lists for use of content to improve AWS services.", "RDAP gives 1994-11-01 for amazon.com and 2005-08-18 for amazonaws.com.", "aws.amazon.com/.well-known/security.txt has Contact, Policy and Encryption fields. Its Expires value is 2027-10-16T16:25:03Z, re-read on 2026-11-01.", "docs.aws.amazon.com/robots.txt allows the Nova and Bedrock pages read. The Nova and Bedrock pricing pages draw their tables by script, so Nova 2 Sonic's prices weren't read." ], "score": 94 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/amazon-nova-sonic.json", "live": { "slug": "amazon-nova-sonic", "versions": [ { "registry": "npm", "name": "@aws-sdk/client-bedrock-runtime", "version": "3.1164.0", "seenAt": "2026-11-06T23:05:35.366071006Z" }, { "registry": "pypi", "name": "aws-sdk-bedrock-runtime", "version": "0.12.0", "released": "2026-10-08", "seenAt": "2026-11-06T23:05:33.518358123Z" } ], "githubStars": 456, "npmWeekly": 21825916, "pypiWeekly": 112826, "securityTxt": { "url": "https://amazon.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T16:00:18.354437696Z" }, "llmsTxt": { "url": "https://docs.aws.amazon.com/nova/latest/nova2-userguide/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:25.828159373Z" }, "pages": [ { "url": "https://docs.aws.amazon.com/nova/latest/nova2-userguide/release-notes.html", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:05:20.262718007Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "48cb3eb6c070" } ], "updatedAt": "2026-11-07T16:00:18.354437696Z" } }, "answer": "Amazon Nova 2 Sonic scores 67.6 (B) on agent readiness against Vocily AI's 53.9 (D), and leads in 3 of 7 scored categories. Vocily AI leads on schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "vocily", "name": "Vocily AI", "vendor": "Vocily AI Private Limited", "vendorUrl": "https://vocily.ai", "kind": "http-api", "category": "voice-agents", "summary": "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.", "url": "https://www.anchorterminal.com/tools/vocily", "markdownUrl": "https://www.anchorterminal.com/tools/vocily.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/vocily.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/vocily.json", "dns": "vocily.grade.anchorterminal.com", "license": "Proprietary service under Vocily's terms of service. No open-source code or published package was found", "transports": [ "http" ], "remoteUrl": "https://api.vocily.ai", "packages": [], "auth": "api-key", "authNotes": "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": "usage", "pricingNotes": "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).", "priceSummary": "$8 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.vocily.ai", "llmsTxt": "https://docs.vocily.ai/llms.txt", "openapi": "https://docs.vocily.ai/developers/openapi.json", "capabilities": [ "voice.agent", "voice.pipeline", "voice.tools", "voice.telephony" ], "tags": [ "hosted", "india", "openapi", "llms-txt", "webhooks", "pipeline", "telephony", "whatsapp", "prepaid", "new" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 53.9, "grade": "D", "agentReady": false, "rank": 930, "ranked": true, "rankOf": 1486, "categoryRank": 19, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 84, "maintenance": 61, "payments": 40, "reliability": 40, "schema": 90, "security": 46, "transparency": 48 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -5, "negativeNotes": [ "2026-09-23 to 2026-10-30, -3, one same-day term. Releases removed fields and routes under `/v1` on the day they were posted: `tools` on the agent body, `call_type`, `?skip=` and `?offset=` and the `/widgets` collection routes (23 and 25 September), `allowed_templates` and `phone_number_id` (10 October), and `builtin_tools.send_whatsapp_template` with `GET /v1/whatsapp/templates` (30 October). On 27 September amounts for organisations moved to INR began coming back in rupees where they were always dollars, and on 17 October the `voicemail` call status changed meaning for every outbound call. The API reference says fields are never removed or renamed within a version. Each came with same-day migration notes (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. On 4 November the developer page no longer lists the SDKs or the MCP server and says to generate a typed client from the OpenAPI file; a corrected claim keeps its term for twelve months (https://vocily.ai/platform/api-tools and https://docs.vocily.ai/developers/api-reference.md)" ], "verdict": "The REST API is documented in detail, with an OpenAPI 3.1 file of 60 operations, a required idempotency key on calls, Retry-After on 429 and signed webhooks. No status page, SLA, SDK or security programme was found, and releases from September to 30 October 2026 removed fields under `/v1` on the day they were announced.", "bestFor": "Indian-language phone agents where a backend builds agents, places outbound calls and reads results over REST, with prepaid rupee billing.", "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" ], "agentNotes": [ "Send a fresh UUID in `Idempotency-Key` on every `POST /v1/calls`. The API refuses the request without it", "Pass a `from_number` the workspace holds. The shared Test Number returns 403 from the API", "Publish a version and make it live before placing a call, or the call returns 409 `agent_not_published`", "Branch on `detail.code`, falling back to the top-level `code`. A 429 body is flat, so read `Retry-After`", "Read `currency` on every call and chat record. Costs are in rupees or dollars depending on the organisation" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.9 } ], "editorialScores": { "ergonomics": 84, "maintenance": 61, "payments": 40, "reliability": 40, "schema": 90, "security": 46, "transparency": 34 }, "provenanceScore": 61, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-10-27", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.vocily.ai/v1/agents \\\n -H \"Authorization: Bearer vk_your_key_here\"" }, "letme": { "capability": "https://letme.dev/voice.agent", "tool": "https://letme.dev/vocily" }, "area": "voice", "unitPrices": [ { "item": "Voice, lowest-priced configuration", "unit": "call-minute", "usd": 0.041, "note": "Soniox, GPT-5 Nano, Vocily voice and the $0.03 platform fee. ₹3.10 for a rupee organisation. Telephony extra on a rented number" }, { "item": "Telephony on a number rented from Vocily", "unit": "call-minute", "usd": 0.004, "note": "billed in 30-second pulses, doubled while a transfer is connected. Free on your own carrier account" }, { "item": "Web chat or WhatsApp AI reply, GPT-5 Nano", "unit": "message", "usd": 0.001, "note": "per model reply, up to $0.02 on GPT-5.6 Terra" }, { "item": "WhatsApp utility template, platform fee", "unit": "message", "usd": 0.0004, "note": "Meta's own charges are paid to Meta separately" }, { "item": "Capacity pack, two more concurrent calls", "unit": "month", "usd": 8, "note": "ten concurrent calls are included at no monthly fee" }, { "item": "Rented Indian phone number", "unit": "month", "usd": 5, "note": "₹499 for a rupee organisation" } ], "provenance": { "legalEntity": "VOCILY AI PRIVATE LIMITED", "domain": "vocily.ai", "domainRegistered": "2026-07-12", "domainNote": "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.", "endpointOnVendorDomain": true, "terms": "https://vocily.ai/terms", "privacy": "https://vocily.ai/privacy", "statusPage": "", "changelog": "https://docs.vocily.ai/developers/changes", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "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." ], "score": 61 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/vocily.json", "live": { "slug": "vocily", "probe": { "target": "https://api.vocily.ai", "method": "get", "lastAt": "2026-11-07T18:21:04.542739535Z", "lastOk": true, "lastStatus": 200, "lastMs": 613, "authRequired": false, "uptime24h": 100, "uptime30d": 99.92, "p50ms24h": 598, "p95ms24h": 710, "samples24h": 239, "samples30d": 7440, "days": [ { "date": "2026-10-08", "probes": 70, "ok": 70 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 251 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 181 }, { "date": "2026-11-06", "probes": 241, "ok": 240 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ], "outages": [ { "start": "2026-11-05T00:42:49.033570433Z", "end": "2026-11-05T01:05:55.629372483Z", "note": "HTTP 502 server error" } ] }, "securityTxt": { "url": "https://vocily.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:39.942882179Z" }, "llmsTxt": { "url": "https://docs.vocily.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:18.643434349Z" }, "domain": { "domain": "vocily.ai", "registered": "2026-07-12", "source": "https://rdap.identitydigital.services/rdap/domain/vocily.ai", "checkedAt": "2026-11-01T14:08:36.201696684Z" }, "pages": [ { "url": "https://docs.vocily.ai/developers/changes", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:08:37.579491785Z", "changedAt": "2026-11-07T14:08:37.579491785Z", "fingerprint": "7e62b1e00c62" }, { "url": "https://vocily.ai/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:23:29.478888232Z", "changedAt": "2026-11-05T13:07:49.023190626Z", "fingerprint": "37fc5f17f0eb" }, { "url": "https://vocily.ai/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:23:32.128459391Z", "changedAt": "2026-10-29T05:18:32.313255936Z", "fingerprint": "07d8f107761d" }, { "url": "https://vocily.ai/terms", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:23:35.731883386Z", "changedAt": "2026-10-29T05:18:34.594674353Z", "fingerprint": "e9e0fd59d51e" } ], "updatedAt": "2026-11-07T18:21:04.542739535Z" } }, "edges": [ { "by": 55, "category": "reliability", "leads": "amazon-nova-sonic", "name": "Reliability", "reasons": { "a": "Hosted reading. AWS Health Dashboard with per-service, per-Region history (20). The dashboard history file (newest event 30 October 2026) lists no Bedrock event in the 90 days from 8 August, and the 3 September us-west-2 event names STS, Connect and IAM Identity Center, not Bedrock. The public dashboard records broad events only, so 25 of 30, as amazon-nova-embeddings was read. Quotas published, 20 concurrent requests per Region, not adjustable (15). The stream API lists `ThrottlingException` (429), `ServiceUnavailableException` (503), `ModelTimeoutException` (408) and `ModelStreamErrorException` (424), Bedrock's troubleshooting guide advises backoff with jitter, and the 8-minute connection limit comes with a session-continuation sample (15). Bedrock's SLA of 99.9 per cent a month per Region for model APIs, as read for amazon-nova-embeddings on 1 November (10). Generally available since 2 December 2025 (10). 20 + 25 + 15 + 15 + 10 + 10 = 95.", "b": "Graded on the public REST API at api.vocily.ai, read as a hosted service. No status page found: status.vocily.ai gave no answer on 4 November 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 (moving window), with ten concurrent calls per organisation included (15). A 429 carries `Retry-After` and `X-RateLimit` headers, and `POST /v1/calls`, the write that places a billed call, requires an `Idempotency-Key` and returns the original call on a retry (15). No SLA found. The terms say availability isn't guaranteed (0). The docs don't label the API beta, but nine dated changes from 23 September to 30 October 2026 changed the `/v1` contract, seven of them with removals, changed error codes or changed meanings, and the terms still allow for beta and pre-launch service; the 8 October reading of the API root's version is struck (a request to the product's own endpoint), and the partial is carried (5 of 10). 0 + 5 + 15 + 15 + 0 + 5 = 40." }, "scores": { "a": 95, "b": 40 } }, { "by": 31, "category": "security", "leads": "amazon-nova-sonic", "name": "Security \u0026 auth", "reasons": { "a": "SigV4 with IAM roles and temporary credentials scoped per model ARN, as the Sonic quickstart signs (30). Tools run in the client, so side effects are the developer's to approve, and IAM can restrict which models a role invokes, with no approval step in the API (12 of 20). The model listens to callers and acts on tool results, and no prompt-injection guidance was found in the Sonic guide (5 of 15). CloudTrail logs Bedrock API calls, read as amazon-nova-embeddings was (12 of 15). VDP on HackerOne, Bedrock in SOC scope and a valid security.txt on aws.amazon.com, with no paid bounty, as on the other AWS listings (18 of 20). Total 77.", "b": "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 (404 on 4 November), 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). 22 + 10 + 4 + 8 + 2 = 46." }, "scores": { "a": 77, "b": 46 } }, { "by": 31, "category": "transparency", "leads": "amazon-nova-sonic", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed model under the AWS Service Terms, with Apache-2.0 SDKs and samples (15). Bedrock stores no inputs or outputs by default and model providers can't see them, Sonic isn't on the abuse-detection page's list of models whose traffic is stored, and section 50.3 doesn't list Bedrock among services whose content improves AWS services, as read for amazon-nova-embeddings on 1 November (22 of 30). Bedrock's lifecycle policy for models launched before 7 September 2026 promises 12 months and a Legacy period of at least 6 months, but the March and May refreshes changed the model in place under the same ID (15 of 20). Regions are listed, with sub-processors not read (12 of 20). Total 64.", "b": "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 compliance page says 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 and 10 and 30 October 2026 with same-day notes and migration tables and no notice period (6 of 20). The privacy policy mentions vetted providers without naming them. The compliance page now says call records, transcripts and recordings are stored on AWS in Mumbai (ap-south-1), that model providers process in their own regions and that Plivo carries calls; no sub-processor list was found, so the partial is carried (6 of 20). 10 + 12 + 6 + 6 = 34." }, "scores": { "a": 79, "b": 48 } }, { "by": 30, "category": "payments", "leads": "vocily", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). The Nova and Bedrock pricing pages carry a speech-to-speech table drawn by script, so the per-token prices weren't read and this line scores absent, which is our reader's limit and not the vendor's (0). New accounts get up to $200 in Free Tier credits, and the Free Tier FAQ says most new customers need no payment method, read as half on the other AWS listings (10). A person signs up for an AWS account in a browser (0). Total 10.", "b": "No x402, MPP or L402 (0 of 40). Per-minute and per-reply prices are public without a login in rupees and US dollars, voice from 4.10 cents a minute and chat from 0.10 cents a model reply, with a 3.00 cents a minute platform fee and capacity packs at $8 a month (20). A new organisation gets 200 credits (₹200) or 2 credits ($2) once its owner's email is verified, 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). 0 + 20 + 20 + 0 = 40." }, "scores": { "a": 10, "b": 40 } }, { "by": 20, "category": "ergonomics", "leads": "vocily", "name": "Agent ergonomics", "reasons": { "a": "Scored as an API. Responses carry transcripts of both sides and usage events, chat history is capped at 200 KB and can be injected once per session (15 of 25). Output controls are voice, turn-taking sensitivity and text or audio input (12 of 20). Typed exceptions with HTTP codes, while errors inside the event stream are less documented (15 of 20). Asynchronous tool calls let the model keep talking, and AWS samples show how to resume after the 8-minute limit, with nothing on repeating tool side effects after a reconnect (12 of 20). A session needs a sequence of start events before audio. The JavaScript SDK is current, but the Python SDK the quickstart uses is pre-alpha and needs Python 3.12 (10 of 15). Total 64.", "b": "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). 20 + 18 + 20 + 18 + 8 = 84." }, "scores": { "a": 64, "b": 84 } }, { "by": 15, "category": "schema", "leads": "vocily", "name": "Schema \u0026 documentation", "reasons": { "a": "The Bedrock service model types `InvokeModelWithBidirectionalStream`, but the Sonic events inside it (session, prompt, content, tool and usage events) are JSON payloads documented only in the guide, with no schema file (12 of 25). llms.txt and Markdown copies of the Nova 2 guide (10). Guides on the event lifecycle, barge-in, turn-taking, async tools and chat history say when and how to use each (16 of 20). Event fields are documented as JSON examples and tables, not typed schemas (10 of 15). Sample repositories in several languages and the API's exceptions with HTTP codes (12 of 15). Release notes and document history, with in-place model refreshes and a versioned model ID (15). Total 75.", "b": "A public OpenAPI 3.1 file, linked from llms.txt, with 60 operations on 4 November (54 on 8 October) 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). 234 example entries 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 from 23 September 2026, which records removals made under `/v1` (23 and 25 September, 10 and 30 October) against the reference's own rule that fields are never removed within a version (12 of 15). 25 + 10 + 16 + 12 + 15 + 12 = 90." }, "scores": { "a": 75, "b": 90 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "Vocily AI Private Limited", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.vocily.ai", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service under Vocily's terms of service. No open-source code or published package was found", "name": "Licence" }, { "a": "0", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-05-28", "b": "2026-10-30", "name": "Last release" }, { "a": "2026-10-01", "b": "2026-06-10", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "2026-09-03", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Amazon Nova 2 Sonic scores 67.6 (B) on agent readiness against Vocily AI's 53.9 (D), and leads in 3 of 7 scored categories. Vocily AI leads on schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Amazon Nova 2 Sonic or Vocily AI?" }, { "answer": "Both need an API key.", "question": "Do Amazon Nova 2 Sonic and Vocily AI need an API key?" }, { "answer": "No hosted endpoint is listed for Amazon Nova 2 Sonic. Vocily AI has a hosted endpoint at https://api.vocily.ai.", "question": "Can an agent call Amazon Nova 2 Sonic and Vocily AI without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 95 against 40", "Security \u0026 auth, 77 against 46", "Transparency \u0026 trust, 79 against 48" ], "also": [ "No incidents deducted, where Vocily AI loses 5 points for them" ], "goodFor": "Voice agents on AWS, call centres on Amazon Connect, teams that want IAM and in-account data handling.", "slug": "amazon-nova-sonic", "watchFor": "Connections end after 8 minutes, so long calls need the session-continuation pattern" }, { "aheadOn": [ "Schema \u0026 documentation, 90 against 75", "Agent ergonomics, 84 against 64", "Payments \u0026 pricing, 40 against 10", "Maintenance \u0026 community, 61 against 50" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "Indian-language phone agents where a backend builds agents, places outbound calls and reads results over REST, with prepaid rupee billing.", "slug": "vocily", "watchFor": "No status page, incident history or SLA was found" } ], "history": { "amazon-nova-sonic": null, "vocily": [ { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 53.8, "fromGrade": "D", "to": 53.9, "toGrade": "D" } ] }, "job": { "capability": "voice.agent", "name": "Voice agents" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-assemblyai-voice-agent.json", "title": "Amazon Nova 2 Sonic vs AssemblyAI Voice Agent API", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-assemblyai-voice-agent" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-bland-ai.json", "title": "Amazon Nova 2 Sonic vs Bland AI API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-bland-ai" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-bolna.json", "title": "Amazon Nova 2 Sonic vs Bolna API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-bolna" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-deepgram-voice-agent.json", "title": "Amazon Nova 2 Sonic vs Deepgram Voice Agent API", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-deepgram-voice-agent" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-elevenlabs-agents.json", "title": "Amazon Nova 2 Sonic vs ElevenLabs Agents API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-elevenlabs-agents" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-fone-me.json", "title": "Amazon Nova 2 Sonic vs fone.me", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-fone-me" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-gemini-live.json", "title": "Amazon Nova 2 Sonic vs Gemini Live API", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-gemini-live" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-gpt-live.json", "title": "Amazon Nova 2 Sonic vs GPT-Live", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-gpt-live" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-harmony-ai.json", "title": "Amazon Nova 2 Sonic vs Harmony.ai", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-harmony-ai" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-hume-evi.json", "title": "Amazon Nova 2 Sonic vs Hume EVI (Empathic Voice Interface)", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-hume-evi" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-inworld-realtime.json", "title": "Amazon Nova 2 Sonic vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-livekit-agents.json", "title": "Amazon Nova 2 Sonic vs LiveKit Agents", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-livekit-agents" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-openai-realtime.json", "title": "Amazon Nova 2 Sonic vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-pipecat.json", "title": "Amazon Nova 2 Sonic vs Pipecat", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-pipecat" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-placecall.json", "title": "Amazon Nova 2 Sonic vs PlaceCall", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-placecall" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-retell-ai.json", "title": "Amazon Nova 2 Sonic vs Retell AI API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-retell-ai" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-rime-prism.json", "title": "Amazon Nova 2 Sonic vs Rime Prism", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-synthflow.json", "title": "Amazon Nova 2 Sonic vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-ultravox.json", "title": "Amazon Nova 2 Sonic vs Ultravox Realtime API", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-ultravox" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vaani-voice.json", "title": "Amazon Nova 2 Sonic vs Vaani Developer Platform", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vaani-voice" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vapi.json", "title": "Amazon Nova 2 Sonic vs Vapi API + MCP", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vapi" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vogent.json", "title": "Amazon Nova 2 Sonic vs Vogent API", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-vocily.json", "title": "AssemblyAI Voice Agent API vs Vocily AI", "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-vocily.json", "title": "Bland AI API + MCP vs Vocily AI", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/bolna-vs-vocily.json", "title": "Bolna API + MCP vs Vocily AI", "url": "https://www.anchorterminal.com/compare/bolna-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vocily.json", "title": "Deepgram Voice Agent API vs Vocily AI", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vocily.json", "title": "ElevenLabs Agents API + MCP vs Vocily AI", "url": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vocily.json", "title": "fone.me vs Vocily AI", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/gemini-live-vs-vocily.json", "title": "Gemini Live API vs Vocily AI", "url": "https://www.anchorterminal.com/compare/gemini-live-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/gpt-live-vs-vocily.json", "title": "GPT-Live vs Vocily AI", "url": "https://www.anchorterminal.com/compare/gpt-live-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-vocily.json", "title": "Harmony.ai vs Vocily AI", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/hume-evi-vs-vocily.json", "title": "Hume EVI (Empathic Voice Interface) vs Vocily AI", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vocily.json", "title": "Inworld Realtime API vs Vocily AI", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/livekit-agents-vs-vocily.json", "title": "LiveKit Agents vs Vocily AI", "url": "https://www.anchorterminal.com/compare/livekit-agents-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-vocily.json", "title": "OpenAI Realtime API vs Vocily AI", "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/pipecat-vs-vocily.json", "title": "Pipecat vs Vocily AI", "url": "https://www.anchorterminal.com/compare/pipecat-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/placecall-vs-vocily.json", "title": "PlaceCall vs Vocily AI", "url": "https://www.anchorterminal.com/compare/placecall-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/retell-ai-vs-vocily.json", "title": "Retell AI API + MCP vs Vocily AI", "url": "https://www.anchorterminal.com/compare/retell-ai-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/rime-prism-vs-vocily.json", "title": "Rime Prism vs Vocily AI", "url": "https://www.anchorterminal.com/compare/rime-prism-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/synthflow-vs-vocily.json", "title": "Synthflow API + MCP vs Vocily AI", "url": "https://www.anchorterminal.com/compare/synthflow-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/ultravox-vs-vocily.json", "title": "Ultravox Realtime API vs Vocily AI", "url": "https://www.anchorterminal.com/compare/ultravox-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/vaani-voice-vs-vocily.json", "title": "Vaani Developer Platform vs Vocily AI", "url": "https://www.anchorterminal.com/compare/vaani-voice-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/vapi-vs-vocily.json", "title": "Vapi API + MCP vs Vocily AI", "url": "https://www.anchorterminal.com/compare/vapi-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/vocily-vs-vogent.json", "title": "Vocily AI vs Vogent API", "url": "https://www.anchorterminal.com/compare/vocily-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/cuelight-vs-vocily.json", "title": "CueLight vs Vocily AI", "url": "https://www.anchorterminal.com/compare/cuelight-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/pipecat-phonellm-vs-vocily.json", "title": "Pipecat PhoneLLM vs Vocily AI", "url": "https://www.anchorterminal.com/compare/pipecat-phonellm-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-pipecat-phonellm.json", "title": "Amazon Nova 2 Sonic vs Pipecat PhoneLLM", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-pipecat-phonellm" } ], "panel": null, "scores": [ { "amazon-nova-sonic": 95, "by": 55, "edge": "amazon-nova-sonic", "key": "reliability", "name": "Reliability", "vocily": 40, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "amazon-nova-sonic": 75, "by": 15, "edge": "vocily", "key": "schema", "name": "Schema \u0026 documentation", "vocily": 90, "weight": 13 }, { "amazon-nova-sonic": 64, "by": 20, "edge": "vocily", "key": "ergonomics", "name": "Agent ergonomics", "vocily": 84, "weight": 13 }, { "amazon-nova-sonic": 77, "by": 31, "edge": "amazon-nova-sonic", "key": "security", "name": "Security \u0026 auth", "vocily": 46, "weight": 14 }, { "amazon-nova-sonic": 10, "by": 30, "edge": "vocily", "key": "payments", "name": "Payments \u0026 pricing", "vocily": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "amazon-nova-sonic": 50, "by": 11, "edge": "vocily", "key": "maintenance", "name": "Maintenance \u0026 community", "vocily": 61, "weight": 7 }, { "amazon-nova-sonic": 79, "by": 31, "edge": "amazon-nova-sonic", "key": "transparency", "name": "Transparency \u0026 trust", "vocily": 48, "weight": 7 } ], "summary": "Amazon Nova 2 Sonic scores 67.6 (B) on agent readiness against Vocily AI's 53.9 (D), and leads in 3 of 7 scored categories. Vocily AI leads on schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and maintenance \u0026 community. Both do voice agents.", "tasks": null, "tutorials": [], "verdicts": { "amazon-nova-sonic": "Nova 2 Sonic runs speech-to-speech conversations with asynchronous tools on Bedrock, with IAM scoping, no default storage of inputs and a 99.9 per cent SLA. Sessions cut off at 8 minutes, the Python SDK is pre-alpha, and the event payloads have no schema file. Prices are in a script-drawn table we couldn't read.", "vocily": "The REST API is documented in detail, with an OpenAPI 3.1 file of 60 operations, a required idempotency key on calls, Retry-After on 429 and signed webhooks. No status page, SLA, SDK or security programme was found, and releases from September to 30 October 2026 removed fields under `/v1` on the day they were announced." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vocily", "json": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vocily.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vocily.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vocily.min.md" }, "markdown": "Amazon Nova 2 Sonic scores 67.6 (B) on agent readiness against Vocily AI's 53.9 (D), and leads in 3 of 7 scored categories. Vocily AI leads on schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and maintenance \u0026 community. Both do voice agents.\n\n- Amazon Nova 2 Sonic: grade B, 67.6/100, rank #314 of 1486. Markdown https://www.anchorterminal.com/tools/amazon-nova-sonic.md · JSON https://www.anchorterminal.com/api/v1/tools/amazon-nova-sonic.json\n- Vocily AI: grade D, 53.9/100, rank #930 of 1486. Markdown https://www.anchorterminal.com/tools/vocily.md · JSON https://www.anchorterminal.com/api/v1/tools/vocily.json\n- Best conversational voice-agent APIs: https://www.anchorterminal.com/best/voice-agents/index.md\n- All 518 voice agents comparisons: https://www.anchorterminal.com/compare/voice-agents/index.md\n\n## Which one, for what\n\n### Amazon Nova 2 Sonic (B)\n\nGood for: Voice agents on AWS, call centres on Amazon Connect, teams that want IAM and in-account data handling.\n\nAhead on:\n- Reliability, 95 against 40\n- Security \u0026 auth, 77 against 46\n- Transparency \u0026 trust, 79 against 48\n\nAlso in its favour:\n- No incidents deducted, where Vocily AI loses 5 points for them\n\nWatch for: Connections end after 8 minutes, so long calls need the session-continuation pattern\n\n### Vocily AI (D)\n\nGood for: Indian-language phone agents where a backend builds agents, places outbound calls and reads results over REST, with prepaid rupee billing.\n\nAhead on:\n- Schema \u0026 documentation, 90 against 75\n- Agent ergonomics, 84 against 64\n- Payments \u0026 pricing, 40 against 10\n- Maintenance \u0026 community, 61 against 50\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No status page, incident history or SLA was found\n\n\n## Why the edge\n\n### Reliability: Amazon Nova 2 Sonic +55\n\n- Amazon Nova 2 Sonic (95): Hosted reading. AWS Health Dashboard with per-service, per-Region history (20). The dashboard history file (newest event 30 October 2026) lists no Bedrock event in the 90 days from 8 August, and the 3 September us-west-2 event names STS, Connect and IAM Identity Center, not Bedrock. The public dashboard records broad events only, so 25 of 30, as amazon-nova-embeddings was read. Quotas published, 20 concurrent requests per Region, not adjustable (15). The stream API lists `ThrottlingException` (429), `ServiceUnavailableException` (503), `ModelTimeoutException` (408) and `ModelStreamErrorException` (424), Bedrock's troubleshooting guide advises backoff with jitter, and the 8-minute connection limit comes with a session-continuation sample (15). Bedrock's SLA of 99.9 per cent a month per Region for model APIs, as read for amazon-nova-embeddings on 1 November (10). Generally available since 2 December 2025 (10). 20 + 25 + 15 + 15 + 10 + 10 = 95.\n- Vocily AI (40): Graded on the public REST API at api.vocily.ai, read as a hosted service. No status page found: status.vocily.ai gave no answer on 4 November 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 (moving window), with ten concurrent calls per organisation included (15). A 429 carries `Retry-After` and `X-RateLimit` headers, and `POST /v1/calls`, the write that places a billed call, requires an `Idempotency-Key` and returns the original call on a retry (15). No SLA found. The terms say availability isn't guaranteed (0). The docs don't label the API beta, but nine dated changes from 23 September to 30 October 2026 changed the `/v1` contract, seven of them with removals, changed error codes or changed meanings, and the terms still allow for beta and pre-launch service; the 8 October reading of the API root's version is struck (a request to the product's own endpoint), and the partial is carried (5 of 10). 0 + 5 + 15 + 15 + 0 + 5 = 40.\n\n### Security \u0026 auth: Amazon Nova 2 Sonic +31\n\n- Amazon Nova 2 Sonic (77): SigV4 with IAM roles and temporary credentials scoped per model ARN, as the Sonic quickstart signs (30). Tools run in the client, so side effects are the developer's to approve, and IAM can restrict which models a role invokes, with no approval step in the API (12 of 20). The model listens to callers and acts on tool results, and no prompt-injection guidance was found in the Sonic guide (5 of 15). CloudTrail logs Bedrock API calls, read as amazon-nova-embeddings was (12 of 15). VDP on HackerOne, Bedrock in SOC scope and a valid security.txt on aws.amazon.com, with no paid bounty, as on the other AWS listings (18 of 20). Total 77.\n- Vocily AI (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 (404 on 4 November), 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). 22 + 10 + 4 + 8 + 2 = 46.\n\n### Transparency \u0026 trust: Amazon Nova 2 Sonic +31\n\n- Amazon Nova 2 Sonic (79): Closed model under the AWS Service Terms, with Apache-2.0 SDKs and samples (15). Bedrock stores no inputs or outputs by default and model providers can't see them, Sonic isn't on the abuse-detection page's list of models whose traffic is stored, and section 50.3 doesn't list Bedrock among services whose content improves AWS services, as read for amazon-nova-embeddings on 1 November (22 of 30). Bedrock's lifecycle policy for models launched before 7 September 2026 promises 12 months and a Legacy period of at least 6 months, but the March and May refreshes changed the model in place under the same ID (15 of 20). Regions are listed, with sub-processors not read (12 of 20). Total 64.\n- Vocily AI (48): 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 compliance page says 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 and 10 and 30 October 2026 with same-day notes and migration tables and no notice period (6 of 20). The privacy policy mentions vetted providers without naming them. The compliance page now says call records, transcripts and recordings are stored on AWS in Mumbai (ap-south-1), that model providers process in their own regions and that Plivo carries calls; no sub-processor list was found, so the partial is carried (6 of 20). 10 + 12 + 6 + 6 = 34.\n\n### Payments \u0026 pricing: Vocily AI +30\n\n- Amazon Nova 2 Sonic (10): No x402, MPP or L402 (0). The Nova and Bedrock pricing pages carry a speech-to-speech table drawn by script, so the per-token prices weren't read and this line scores absent, which is our reader's limit and not the vendor's (0). New accounts get up to $200 in Free Tier credits, and the Free Tier FAQ says most new customers need no payment method, read as half on the other AWS listings (10). A person signs up for an AWS account in a browser (0). Total 10.\n- Vocily AI (40): No x402, MPP or L402 (0 of 40). Per-minute and per-reply prices are public without a login in rupees and US dollars, voice from 4.10 cents a minute and chat from 0.10 cents a model reply, with a 3.00 cents a minute platform fee and capacity packs at $8 a month (20). A new organisation gets 200 credits (₹200) or 2 credits ($2) once its owner's email is verified, 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). 0 + 20 + 20 + 0 = 40.\n\n### Agent ergonomics: Vocily AI +20\n\n- Amazon Nova 2 Sonic (64): Scored as an API. Responses carry transcripts of both sides and usage events, chat history is capped at 200 KB and can be injected once per session (15 of 25). Output controls are voice, turn-taking sensitivity and text or audio input (12 of 20). Typed exceptions with HTTP codes, while errors inside the event stream are less documented (15 of 20). Asynchronous tool calls let the model keep talking, and AWS samples show how to resume after the 8-minute limit, with nothing on repeating tool side effects after a reconnect (12 of 20). A session needs a sequence of start events before audio. The JavaScript SDK is current, but the Python SDK the quickstart uses is pre-alpha and needs Python 3.12 (10 of 15). Total 64.\n- Vocily AI (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). 20 + 18 + 20 + 18 + 8 = 84.\n\n### Schema \u0026 documentation: Vocily AI +15\n\n- Amazon Nova 2 Sonic (75): The Bedrock service model types `InvokeModelWithBidirectionalStream`, but the Sonic events inside it (session, prompt, content, tool and usage events) are JSON payloads documented only in the guide, with no schema file (12 of 25). llms.txt and Markdown copies of the Nova 2 guide (10). Guides on the event lifecycle, barge-in, turn-taking, async tools and chat history say when and how to use each (16 of 20). Event fields are documented as JSON examples and tables, not typed schemas (10 of 15). Sample repositories in several languages and the API's exceptions with HTTP codes (12 of 15). Release notes and document history, with in-place model refreshes and a versioned model ID (15). Total 75.\n- Vocily AI (90): A public OpenAPI 3.1 file, linked from llms.txt, with 60 operations on 4 November (54 on 8 October) 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). 234 example entries 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 from 23 September 2026, which records removals made under `/v1` (23 and 25 September, 10 and 30 October) against the reference's own rule that fields are never removed within a version (12 of 15). 25 + 10 + 16 + 12 + 15 + 12 = 90.\n\n## Score by category\n\n| Category | Weight | Amazon Nova 2 Sonic | Vocily AI | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 95 | 40 | Amazon Nova 2 Sonic +55 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 75 | 90 | Vocily AI +15 |\n| Agent ergonomics | 13% (16.2 this run) | 64 | 84 | Vocily AI +20 |\n| Security \u0026 auth | 14% (17.5 this run) | 77 | 46 | Amazon Nova 2 Sonic +31 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 40 | Vocily AI +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 50 | 61 | Vocily AI +11 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 79 | 48 | Amazon Nova 2 Sonic +31 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **67.6 · B** | **53.9 · D** | |\n\n## Facts side by side\n\n| Fact | Amazon Nova 2 Sonic | Vocily AI |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Vocily AI Private Limited |\n| Hosted endpoint | no (local only) | `https://api.vocily.ai` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | none | Proprietary service under Vocily's terms of service. No open-source code or published package was found |\n| Tools exposed | 0 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-05-28 | 2026-10-30 |\n| Terms last updated | 2026-10-01 | 2026-06-10 |\n| Privacy policy last updated | 2026-05-18 | 2026-09-03 |\n| Customer content may train models | yes, with an opt-out | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n\n## How the scores have moved\n\n### Amazon Nova 2 Sonic\n\nNo score change since it was listed.\n\n### Vocily AI\n\n- +0.1 on 27 October 2026: checklist\n\n## Verdicts\n\n**Amazon Nova 2 Sonic.** Nova 2 Sonic runs speech-to-speech conversations with asynchronous tools on Bedrock, with IAM scoping, no default storage of inputs and a 99.9 per cent SLA. Sessions cut off at 8 minutes, the Python SDK is pre-alpha, and the event payloads have no schema file. Prices are in a script-drawn table we couldn't read.\n\n**Vocily AI.** The REST API is documented in detail, with an OpenAPI 3.1 file of 60 operations, a required idempotency key on calls, Retry-After on 429 and signed webhooks. No status page, SLA, SDK or security programme was found, and releases from September to 30 October 2026 removed fields under `/v1` on the day they were announced.\n\n## Before you call either\n\n### Amazon Nova 2 Sonic\n\n1. Plan a reconnect before 8 minutes and replay chat history (up to 200 KB) at the start of the new session\n2. Send session, prompt and content start events in order before any audio\n3. Make tool calls safe to repeat, since a reconnect can replay them\n4. Back off on `ThrottlingException` and stay within 20 concurrent sessions per Region\n5. Use the polyglot voices TIFFANY or MATTHEW when callers may switch language\n\n### Vocily AI\n\n1. Send a fresh UUID in `Idempotency-Key` on every `POST /v1/calls`. The API refuses the request without it\n2. Pass a `from_number` the workspace holds. The shared Test Number returns 403 from the API\n3. Publish a version and make it live before placing a call, or the call returns 409 `agent_not_published`\n4. Branch on `detail.code`, falling back to the top-level `code`. A 429 body is flat, so read `Retry-After`\n5. Read `currency` on every call and chat record. Costs are in rupees or dollars depending on the organisation\n\n## Questions\n\n### Which is better for AI agents, Amazon Nova 2 Sonic or Vocily AI?\n\nAmazon Nova 2 Sonic scores 67.6 (B) on agent readiness against Vocily AI's 53.9 (D), and leads in 3 of 7 scored categories. Vocily AI leads on schema \u0026 documentation, agent ergonomics, payments \u0026 pricing and maintenance \u0026 community.\n\n### Do Amazon Nova 2 Sonic and Vocily AI need an API key?\n\nBoth need an API key.\n\n### Can an agent call Amazon Nova 2 Sonic and Vocily AI without installing anything?\n\nNo hosted endpoint is listed for Amazon Nova 2 Sonic. Vocily AI has a hosted endpoint at https://api.vocily.ai.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vocily.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vocily.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"amazon-nova-sonic\", \"b\": \"vocily\"}`. From a terminal: `anchor compare amazon-nova-sonic vocily`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/amazon-nova-sonic.json and https://www.anchorterminal.com/api/v1/tools/vocily.json\n\n## Other comparisons with Amazon Nova 2 Sonic or Vocily AI\n\n- [Amazon Nova 2 Sonic vs AssemblyAI Voice Agent API](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-assemblyai-voice-agent.md)\n- [Amazon Nova 2 Sonic vs Bland AI API + MCP](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-bland-ai.md)\n- [Amazon Nova 2 Sonic vs Bolna API + MCP](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-bolna.md)\n- [Amazon Nova 2 Sonic vs Deepgram Voice Agent API](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-deepgram-voice-agent.md)\n- [Amazon Nova 2 Sonic vs ElevenLabs Agents API + MCP](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-elevenlabs-agents.md)\n- [Amazon Nova 2 Sonic vs fone.me](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-fone-me.md)\n- [Amazon Nova 2 Sonic vs Gemini Live API](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-gemini-live.md)\n- [Amazon Nova 2 Sonic vs GPT-Live](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-gpt-live.md)\n- [Amazon Nova 2 Sonic vs Harmony.ai](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-harmony-ai.md)\n- [Amazon Nova 2 Sonic vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-hume-evi.md)\n- [Amazon Nova 2 Sonic vs Inworld Realtime API](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-inworld-realtime.md)\n- [Amazon Nova 2 Sonic vs LiveKit Agents](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-livekit-agents.md)\n- [Amazon Nova 2 Sonic vs OpenAI Realtime API](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-openai-realtime.md)\n- [Amazon Nova 2 Sonic vs Pipecat](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-pipecat.md)\n- [Amazon Nova 2 Sonic vs PlaceCall](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-placecall.md)\n- [Amazon Nova 2 Sonic vs Retell AI API + MCP](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-retell-ai.md)\n- [Amazon Nova 2 Sonic vs Rime Prism](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-rime-prism.md)\n- [Amazon Nova 2 Sonic vs Synthflow API + MCP](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-synthflow.md)\n- [Amazon Nova 2 Sonic vs Ultravox Realtime API](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-ultravox.md)\n- [Amazon Nova 2 Sonic vs Vaani Developer Platform](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vaani-voice.md)\n- [Amazon Nova 2 Sonic vs Vapi API + MCP](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vapi.md)\n- [Amazon Nova 2 Sonic vs Vogent API](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vogent.md)\n- [AssemblyAI Voice Agent API vs Vocily AI](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-vocily.md)\n- [Bland AI API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/bland-ai-vs-vocily.md)\n- [Bolna API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/bolna-vs-vocily.md)\n- [Deepgram Voice Agent API vs Vocily AI](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vocily.md)\n- [ElevenLabs Agents API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vocily.md)\n- [fone.me vs Vocily AI](https://www.anchorterminal.com/compare/fone-me-vs-vocily.md)\n- [Gemini Live API vs Vocily AI](https://www.anchorterminal.com/compare/gemini-live-vs-vocily.md)\n- [GPT-Live vs Vocily AI](https://www.anchorterminal.com/compare/gpt-live-vs-vocily.md)\n- [Harmony.ai vs Vocily AI](https://www.anchorterminal.com/compare/harmony-ai-vs-vocily.md)\n- [Hume EVI (Empathic Voice Interface) vs Vocily AI](https://www.anchorterminal.com/compare/hume-evi-vs-vocily.md)\n- [Inworld Realtime API vs Vocily AI](https://www.anchorterminal.com/compare/inworld-realtime-vs-vocily.md)\n- [LiveKit Agents vs Vocily AI](https://www.anchorterminal.com/compare/livekit-agents-vs-vocily.md)\n- [OpenAI Realtime API vs Vocily AI](https://www.anchorterminal.com/compare/openai-realtime-vs-vocily.md)\n- [Pipecat vs Vocily AI](https://www.anchorterminal.com/compare/pipecat-vs-vocily.md)\n- [PlaceCall vs Vocily AI](https://www.anchorterminal.com/compare/placecall-vs-vocily.md)\n- [Retell AI API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/retell-ai-vs-vocily.md)\n- [Rime Prism vs Vocily AI](https://www.anchorterminal.com/compare/rime-prism-vs-vocily.md)\n- [Synthflow API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/synthflow-vs-vocily.md)\n- [Ultravox Realtime API vs Vocily AI](https://www.anchorterminal.com/compare/ultravox-vs-vocily.md)\n- [Vaani Developer Platform vs Vocily AI](https://www.anchorterminal.com/compare/vaani-voice-vs-vocily.md)\n- [Vapi API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/vapi-vs-vocily.md)\n- [Vocily AI vs Vogent API](https://www.anchorterminal.com/compare/vocily-vs-vogent.md)\n- [CueLight vs Vocily AI](https://www.anchorterminal.com/compare/cuelight-vs-vocily.md)\n- [Pipecat PhoneLLM vs Vocily AI](https://www.anchorterminal.com/compare/pipecat-phonellm-vs-vocily.md)\n- [Amazon Nova 2 Sonic vs Pipecat PhoneLLM](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-pipecat-phonellm.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Amazon Nova 2 Sonic vs Vocily AI", "url": "" } ], "description": "Amazon Nova 2 Sonic scores 67.6 (B) to Vocily AI's 53.9 (D) for voice agents. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Amazon Nova 2 Sonic B 67.6", "Vocily AI D 53.9", "scores" ], "h1": "Amazon Nova 2 Sonic vs Vocily AI", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/amazon-nova-sonic-vs-vocily", "published": "2026-10-01", "section": "tools", "title": "Amazon Nova 2 Sonic vs Vocily AI for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vocily" }, "tokens": { "markdown": 5700, "slim": 3230 }, "version": 1 }