{ "data": { "a": { "slug": "inworld-realtime", "name": "Inworld Realtime API", "vendor": "Inworld AI", "vendorUrl": "https://inworld.ai", "kind": "http-api", "category": "voice-agents", "summary": "Inworld's Realtime API runs spoken conversations over WebSocket or WebRTC, chaining Inworld STT, an LLM chosen by the developer and Inworld TTS, with turn detection, interruptions and tool calling. It follows OpenAI's Realtime protocol.", "url": "https://www.anchorterminal.com/tools/inworld-realtime", "markdownUrl": "https://www.anchorterminal.com/tools/inworld-realtime.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/inworld-realtime.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/inworld-realtime.json", "dns": "inworld-realtime.grade.anchorterminal.com", "transports": [ "websocket", "http" ], "packages": [ { "registry": "npm", "name": "@inworld/cli" } ], "auth": "api-key", "authNotes": "Servers send `Authorization: Basic` with the Base64 `key_id:secret` credential. Browsers send `Authorization: Bearer` with a session token minted server side. The `key` query parameter in the WebSocket URL is a session ID, not a secret.", "pricing": "usage", "pricingNotes": "No per-minute or per-session price. A session is billed as its STT ($0.10 to $0.15 an hour), its LLM tokens at the model's rate and its TTS characters (TTS-2 from $25 per million on the free plan). Segments already sent to TTS are billed after an interruption.", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, llms.txt or pricing page (checked 2026-11-06). Plans and credits are bought in the Portal.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.inworld.ai/realtime/overview", "llmsTxt": "https://docs.inworld.ai/llms.txt", "capabilities": [ "voice.agent", "voice.pipeline", "voice.tools", "voice.telephony" ], "tags": [ "hosted", "usage", "free-tier", "closed-source", "llms-txt", "streaming", "websocket", "webrtc", "openai-compatible", "enterprise" ], "lastRelease": "2026-10-16", "graded": true, "anchor": { "graded": true, "score": 60.1, "grade": "C", "agentReady": false, "rank": 671, "ranked": true, "rankOf": 1510, "categoryRank": 12, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 71, "payments": 40, "reliability": 62, "schema": 60, "security": 58, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Inworld's Realtime API speaks OpenAI's Realtime protocol over WebSocket or WebRTC, with a choice of LLM, client-side tools and dated release notes. Cost is the sum of STT, LLM and TTS usage with no per-minute price, there is no machine-readable event schema, and status history couldn't be read.", "bestFor": "Teams moving off OpenAI's Realtime API who want a choice of LLM and Inworld voices.", "strengths": [ "Follows OpenAI's Realtime events, with a migration guide that changes only the URL, key and a few defaults", "Dated release notes name affected clients and required actions for each compatibility change", "A choice of LLM through Inworld's router, with prompt caching on Anthropic models", "Concurrent sessions from 10 on the free plan to 1,000 on Growth", "Zero data retention covers session content from the Developer plan up" ], "weaknesses": [ "No per-minute price. A session's cost depends on STT, LLM tokens and TTS characters, and interrupted segments are still billed", "No AsyncAPI or other machine-readable schema for the socket events", "Status history couldn't be read, and an SLA exists only for Enterprise", "The 21 July 2026 release changed response and item shapes for existing clients", "Zero data retention doesn't cover requests routed to third-party LLM providers" ], "agentNotes": [ "Set the auto follow-up off if your client sends its own `response.create` after a tool result, or replies double", "Read `response.done` usage as an estimate and mute input audio when nobody speaks, since STT bills every second sent", "Use `response.speak` for fixed greetings, which skips the LLM", "Treat `unsupported_field` errors as warnings and keep the session open", "Mint browser session tokens on your server and never ship the Basic credential to a client" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.1 } ], "editorialScores": { "ergonomics": 68, "maintenance": 71, "payments": 40, "reliability": 62, "schema": 60, "security": 58, "transparency": 51 }, "provenanceScore": 75, "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": "npm install -g @inworld/cli" }, "letme": { "capability": "https://letme.dev/voice.agent", "tool": "https://letme.dev/inworld-realtime" }, "sameCompany": [ "inworld-stt", "inworld-tts", "inworld-voice-cloning" ], "area": "voice", "unitPrices": [ { "item": "Speech recognition in a session", "unit": "audio-minute", "usd": 0.0025, "note": "STT-1 at $0.15 an hour On-Demand, $0.10 on paid plans" }, { "item": "Agent speech, TTS-2", "unit": "1m-chars", "usd": 25, "note": "free On-Demand plan; lower on paid plans" } ], "provenance": { "legalEntity": "Theai, Inc. dba Inworld AI", "domain": "inworld.ai", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://inworld.ai/terms", "privacy": "https://inworld.ai/privacy", "statusPage": "https://status.inworld.ai", "changelog": "https://docs.inworld.ai/release-notes/realtime", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The Terms of Service (effective 11 June 2025) are an agreement with Theai, Inc. dba Inworld AI under California law, with courts in Santa Clara. The Privacy Notice (last updated 18 January 2026) names Theai, Inc.", "inworld.ai/.well-known/security.txt returns 404. The security page links a vulnerability report form.", "status.inworld.ai runs the open-source issue-status app, which draws incidents from GitHub issues in inworld-ai/inworld-issue-status. Its history wasn't read, because GitHub's robots.txt couldn't be read from our environment.", "inworld.ai's robots.txt allows Claude agents on the paths read and sets `Content-Signal: ai-train=no, search=yes, ai-input=no`. docs.inworld.ai has no such signal.", "The domain's registration date wasn't established, because the RDAP lookup failed.", "firstReleased is left empty. The public Realtime release notes start on 21 July 2026 and no launch date was found." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/inworld-realtime.json", "live": { "slug": "inworld-realtime", "vendorStatus": { "page": "https://status.inworld.ai", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:57.03709454Z" }, "versions": [ { "registry": "npm", "name": "@inworld/cli", "version": "1.5.0", "seenAt": "2026-11-06T23:35:04.551623033Z" } ], "npmWeekly": 290, "securityTxt": { "url": "https://inworld.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:11.794771951Z" }, "llmsTxt": { "url": "https://docs.inworld.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:46.028273902Z" }, "pages": [ { "url": "https://docs.inworld.ai/release-notes/realtime", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:06:42.218731652Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9ae0f1f05b69" }, { "url": "https://inworld.ai/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:11:39.031139211Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "99dc39a9de92" }, { "url": "https://inworld.ai/terms", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:11:41.181276356Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "777d881cbf9b" } ], "updatedAt": "2026-11-07T16:01:11.794771951Z" } }, "answer": "Inworld Realtime API scores 60.1 (C) on agent readiness against Vogent API's 44.9 (E), and leads in 6 of 7 scored categories. Vogent API leads on schema \u0026 documentation.", "b": { "slug": "vogent", "name": "Vogent API", "vendor": "Vogent", "vendorUrl": "https://www.vogent.ai", "kind": "http-api", "category": "voice-agents", "summary": "Phone voice-agent platform with its own conversational LLM, voices and IVR-navigation models alongside GPT.", "url": "https://www.anchorterminal.com/tools/vogent", "markdownUrl": "https://www.anchorterminal.com/tools/vogent.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/vogent.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/vogent.json", "dns": "vogent.grade.anchorterminal.com", "transports": [ "http" ], "remoteUrl": "https://api.vogent.ai/api", "packages": [ { "registry": "npm", "name": "@vogent/vogent-web-client" } ], "auth": "api-key", "authNotes": "Bearer API key created per user in the dashboard. Keys stop working when that user leaves the workspace. The Websocket TTS reference also accepts the key as an `apiKey` query parameter. Webhooks are signed with HMAC-SHA256 in the `X-Elto-Signature` header.", "pricing": "usage", "pricingNotes": "Pay as you go, metered by the second. $0.09 a minute ($0.0015 a second) with standard voices and $0.14 a minute ($0.0023 a second) with premium voices. The docs don't say whether telephony is included or whether there's free credit. Enterprise plans add volume discounts from about 5,000 to 10,000 calls a month (https://docs.vogent.ai/platform-overview/billing).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 support in the docs or OpenAPI spec (checked 2026-09-30).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://docs.vogent.ai", "llmsTxt": "https://docs.vogent.ai/llms.txt", "openapi": "https://docs.vogent.ai/api-reference/openapi.yaml", "capabilities": [ "voice.agent", "voice.pipeline", "voice.tools", "voice.telephony" ], "tags": [ "hosted", "closed-source", "openapi", "llms-txt", "typescript", "webhooks", "pipeline", "enterprise" ], "lastRelease": "2026-01-23", "graded": true, "anchor": { "graded": true, "score": 44.9, "grade": "E", "agentReady": false, "rank": 1209, "ranked": true, "rankOf": 1510, "categoryRank": 22, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 57, "maintenance": 11, "payments": 15, "reliability": 57, "schema": 73, "security": 26, "transparency": 57 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-05" }, "negative": 0, "verdict": "Outbound calling with IVR detection and navigation, an OpenAPI file and idempotent dial creation. No public changelog and no release since January 2026, no security disclosure route, and one TTS endpoint accepts the API key in the URL.", "bestFor": "Outbound calling that has to navigate IVRs in English or Spanish, in the US, Canada and the UK.", "strengths": [ "IVR detection and navigation models for outbound calls", "Idempotent dial creation with `idempotencyKey` and a 409 on reuse", "OpenAPI 3.0.3 and AsyncAPI files linked from llms.txt", "HMAC-SHA256 signed webhooks", "A subprocessors page names 12 providers with purpose and location" ], "weaknesses": [ "No public changelog and no release found since January 2026", "No published rate limits or 429 handling", "No free tier or trial stated", "The Websocket TTS endpoint accepts the API key as an `apiKey` query parameter", "No security.txt, disclosure policy or certification found" ], "agentNotes": [ "Send an `idempotencyKey` on `POST /dials`, a reused key returns 409", "Create a call with `callAgentId`, plus `toNumber` and `fromNumberId` for phone calls", "Send the key in the `Authorization` header on the TTS websocket, not the `apiKey` query parameter", "Verify webhooks with the HMAC in `X-Elto-Signature`", "Expect new dials to fail at the workspace's concurrent dial limit until calls end" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 44.9 } ], "editorialScores": { "ergonomics": 57, "maintenance": 11, "payments": 15, "reliability": 57, "schema": 73, "security": 26, "transparency": 43 }, "provenanceScore": 70, "checked": { "categories": { "ergonomics": "2026-11-05", "maintenance": "2026-11-05", "payments": "2026-11-05", "reliability": "2026-11-05", "schema": "2026-11-05", "security": "2026-11-05", "transparency": "2026-11-05" }, "last": "2026-11-05", "lastMoved": "2026-11-05", "oldest": "2026-11-05", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -X POST https://api.vogent.ai/api/dials -H \"Authorization: Bearer $VOGENT_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"callAgentId\":\"\u003cagent-id\u003e\",\"toNumber\":\"+11234567890\",\"fromNumberId\":\"\u003cnumber-id\u003e\"}'" }, "letme": { "capability": "https://letme.dev/voice.agent", "tool": "https://letme.dev/vogent" }, "area": "voice", "unitPrices": [ { "item": "Standard voices", "unit": "call-minute", "usd": 0.09, "note": "billed per second, docs don't say if telephony is included" }, { "item": "Premium voices", "unit": "call-minute", "usd": 0.14, "note": "billed per second" } ], "provenance": { "legalEntity": "Monoid, Inc.", "domain": "vogent.ai", "domainRegistered": "2024-08-28", "domainNote": "Vogent traded as Elto before, and recording URLs still sit on api.getelto.com.", "endpointOnVendorDomain": true, "terms": "https://www.vogent.ai/terms", "privacy": "https://www.vogent.ai/privacy", "statusPage": "https://status.vogent.ai", "changelog": "", "securityTxt": "none", "checked": "2026-11-05", "notes": [ "Per the 30 September check, the terms and privacy notice name Monoid, Inc., doing business as Vogent, and were last updated 2024-03-03. Both pages render only with JavaScript and weren't re-read on 5 November 2026.", "status.vogent.ai is a Better Stack page with one Vogent API component.", "www.vogent.ai/.well-known/security.txt answered 404 on 5 November 2026." ], "score": 70 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/vogent.json", "live": { "slug": "vogent", "probe": { "target": "https://api.vogent.ai/api", "method": "get", "lastAt": "2026-11-07T19:22:43.70435972Z", "lastOk": true, "lastStatus": 404, "lastMs": 413, "authRequired": false, "uptime24h": 100, "uptime30d": 99.99, "p50ms24h": 371, "p95ms24h": 494, "samples24h": 238, "samples30d": 7920, "days": [ { "date": "2026-10-07", "probes": 272, "ok": 271 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "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": 252 }, { "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": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.vogent.ai", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:57.709070684Z" }, "versions": [ { "registry": "npm", "name": "@vogent/vogent-web-client", "version": "0.1.7", "seenAt": "2026-11-07T00:16:11.315963039Z" } ], "npmWeekly": 430, "securityTxt": { "url": "https://vogent.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:07.146057968Z" }, "llmsTxt": { "url": "https://docs.vogent.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:18.662928959Z" }, "domain": { "domain": "vogent.ai", "registered": "2024-08-28", "source": "https://rdap.identitydigital.services/rdap/domain/vogent.ai", "checkedAt": "2026-11-01T14:23:49.547624699Z" }, "pages": [ { "url": "https://www.vogent.ai/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:36:35.489520335Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "5257817e1996" }, { "url": "https://www.vogent.ai/terms", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:36:37.657544754Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "5257817e1996" } ], "updatedAt": "2026-11-07T19:22:43.70435972Z" } }, "edges": [ { "by": 60, "category": "maintenance", "leads": "inworld-realtime", "name": "Maintenance \u0026 community", "reasons": { "a": "Release note of 16 October 2026 (`cache_transcript`), 21 days ago (30). Three dated Realtime entries in the 90 days from 8 August, on 14 September, 23 September and 16 October (20). Discord and support@inworld.ai, with no evidence of answers read (8 of 15). Works with OpenAI's Realtime clients and the CLI is current at 1.5.0, but there is no Inworld Realtime SDK (8 of 15). CLI on npm under MIT, CI not read (5 of 10). Total 71.", "b": "The newest release found is web client v0.1.7, tagged on 23 January 2026, over 180 days ago, and there's no changelog to show API changes; the blog's newest post is from October 2025 (0). No releases found in the last 90 days (0). No public changelog or issue tracker, and we didn't test support (3 of 15). One official SDK, the web client (5 of 15). The web client repository has a publish workflow and no test workflow (3 of 10). 0+0+3+5+3 = 11." }, "scores": { "a": 71, "b": 11 } }, { "by": 32, "category": "security", "leads": "inworld-realtime", "name": "Security \u0026 auth", "reasons": { "a": "Workspace API keys sent as Basic credentials, deleted to revoke, with separate keys per environment advised. The CLI mints read-only keys unless `--write` is given, but write toggles cover only the Voice and Router APIs, so no key is limited to one product. Browsers use short-lived tokens minted server side. Session IDs, not secrets, go in the URL (25 of 30). Tools run in the client, so the developer approves side effects, with no approval step in the API (10 of 20). The agent listens to callers and passes their speech to an LLM, and no prompt-injection guidance was found (5 of 15). Usage per key and a Performance page with errors and throttling (8 of 15). SOC 2 Type II and HIPAA claimed and a vulnerability report form, with no security.txt or bug bounty, per the 4 November reading (10 of 20). Total 58. Zero data retention covers session content from the Developer plan up, but not requests routed to third-party LLM providers.", "b": "Bearer keys created per user, which stop working when that user leaves the workspace, with no scopes (20). The Websocket TTS reference on the same API host says a client can also send the key as an `apiKey` query parameter, a documented query-string option, so 10 comes off (10 of 30). No read-only keys or approval step (3 of 20). Agents hear callers and we found no prompt-injection guidance (5 of 15). Dial history per call, no audit log found (8 of 15). Webhooks are signed with HMAC-SHA256 in `X-Elto-Signature`, but security.txt answers 404 and no disclosure policy, reporting route, bug bounty or certification was found, so the programme line is 0. 10+3+5+8+0 = 26." }, "scores": { "a": 58, "b": 26 } }, { "by": 25, "category": "payments", "leads": "inworld-realtime", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). No per-session price, but each billed part (STT per hour, TTS per character, LLM per token) is priced publicly (20). On-Demand includes free STT and TTS allowances and lists no payment method, though some premium LLMs need a card on file (20). A person signs up in a browser before a key exists (0). Total 40.", "b": "No x402, MPP or L402 (0 of 40). Per-second rates are public, $0.09 a minute on standard voices and $0.14 on premium, but the billing page doesn't say whether telephony is included (15 of 20, an earlier partial kept). No free tier or trial stated (0). Access starts with a human signup (0). 0+15+0+0 = 15." }, "scores": { "a": 40, "b": 15 } }, { "by": 13, "category": "schema", "leads": "vogent", "name": "Schema \u0026 documentation", "reasons": { "a": "No AsyncAPI or other machine-readable file for the socket, and the spec paths redirect (0). llms.txt, Markdown twins and a docs MCP server (10). The overview, OpenAI migration guide, `providerData` reference and the billing page's account of how a session is counted say what to use when (16 of 20). The reference lists every client and server event with field types and required marks, as text rather than a schema (12 of 15). JavaScript and Python example projects and an error event with `type`, `code` and `param`, without a list of codes (9 of 15). Dated release notes with affected clients and required actions, but no API version beyond `/v1` (13 of 15). Total 60.", "b": "OpenAPI 3.0.3 file (version 1.0.11, 42 paths, 65 operations) and an AsyncAPI file, both linked from llms.txt (25). llms.txt with 117 page links and Markdown pages (10). Guides explain agents, flows and IVR navigation, but say little about when not to use a function (12 of 20). Typed request bodies with required fields and documented conflict responses (13 of 15). Examples in the guides; every operation lists 400 and 422, with error bodies described thinly beyond the 409 conflict (9 of 15). The spec carries a version number, but there's no public changelog (4 of 15). 25+10+12+13+9+4 = 73." }, "scores": { "a": 60, "b": 73 } }, { "by": 11, "category": "ergonomics", "leads": "inworld-realtime", "name": "Agent ergonomics", "reasons": { "a": "Scored as an API. Conversation history defaults to the last 100 items, can be trimmed, and can be cached on Anthropic models, and every `response.done` carries a `usage` block (18 of 25). No lists to page. Output controls are modalities, turn detection settings, optional transcription and `response.speak` (12 of 20). Error events follow OpenAI's `type` and `code` shape, unsupported fields come back as non-fatal `unsupported_field` warnings, and `item_not_found` names the bad parameter (14 of 20). Tools run on the client and a follow-up response starts automatically after a tool result. Nothing covers side effects of a tool call cut off by an interruption (12 of 20). Works with OpenAI Realtime clients after changing the URL and key, with no Inworld Realtime SDK (12 of 15). Total 68.", "b": "Scored as an API, since there's no MCP server. Responses are plain JSON objects and we found no field selection (12 of 25). Some list endpoints page by cursor, and filters are limited (12 of 20). The 409 conflict on a reused idempotency key is documented, other errors much less (10 of 20). Dial creation is idempotent with `idempotencyKey` (15 of 20). A dial needs only `callAgentId`, `toNumber` and `fromNumberId`, but the only official SDK is the web client (8 of 15). 12+12+10+15+8 = 57." }, "scores": { "a": 68, "b": 57 } }, { "by": 6, "category": "transparency", "leads": "inworld-realtime", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service with clear terms naming Theai, Inc. dba Inworld AI (15). The ZDR page says what a session keeps and that third-party LLM requests aren't covered, but the terms and privacy notice disagree on training (12 of 30). Release notes flag potentially breaking changes with the clients affected and what to do, without stating a notice period (14 of 20). US headquarters with EU and India residency on Enterprise, and no sub-processor list in the docs, while sessions may route to third-party LLM providers (10 of 20). Total 51.", "b": "Closed platform. Per the 30 September check, the terms and privacy notice name Monoid, Inc. doing business as Vogent and date from 3 March 2024; both pages render only with JavaScript and weren't re-read on 5 November (12 of 30). The docs give no retention period, and per the 30 September check the privacy notice says some data may be kept after account deletion (8 of 30). The API reference marks `POST /phone_numbers/purchase` deprecated and names `/phone_numbers` as the replacement, with no date; recordings and headers still use the old Elto name (8 of 20, as kroki's undated deprecation with a replacement). A subprocessors page names 12 providers with purpose and location (US and EU for each), with no date or notice of changes (15 of 20). 12+8+8+15 = 43." }, "scores": { "a": 63, "b": 57 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Inworld AI", "b": "Vogent", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.vogent.ai/api", "name": "Hosted endpoint" }, { "a": "websocket, HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$25 per 1M characters", "b": "not published", "name": "Price for voice agents" }, { "a": "no", "b": "no", "name": "x402" }, { "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-10-16", "b": "2026-01-23", "name": "Last release" }, { "a": "2025-06-11", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-01-18", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "2/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Inworld Realtime API scores 60.1 (C) on agent readiness against Vogent API's 44.9 (E), and leads in 6 of 7 scored categories. Vogent API leads on schema \u0026 documentation.", "question": "Which is better for AI agents, Inworld Realtime API or Vogent API?" }, { "answer": "Both need an API key.", "question": "Do Inworld Realtime API and Vogent API need an API key?" }, { "answer": "No hosted endpoint is listed for Inworld Realtime API. Vogent API has a hosted endpoint at https://api.vogent.ai/api.", "question": "Can an agent call Inworld Realtime API and Vogent API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 62 against 57", "Agent ergonomics, 68 against 57", "Security \u0026 auth, 58 against 26", "Payments \u0026 pricing, 40 against 15", "Maintenance \u0026 community, 71 against 11", "Transparency \u0026 trust, 63 against 57" ], "also": null, "goodFor": "Teams moving off OpenAI's Realtime API who want a choice of LLM and Inworld voices.", "slug": "inworld-realtime", "watchFor": "No per-minute price. A session's cost depends on STT, LLM tokens and TTS characters, and interrupted segments are still billed" }, { "aheadOn": [ "Schema \u0026 documentation, 73 against 60" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "Outbound calling that has to navigate IVRs in English or Spanish, in the US, Canada and the UK.", "slug": "vogent", "watchFor": "No public changelog and no release found since January 2026" } ], "history": { "inworld-realtime": null, "vogent": [ { "causes": [ "evidence", "correction" ], "date": "2026-11-05", "delta": -2.4, "from": 47.3, "fromGrade": "D", "to": 44.9, "toGrade": "E" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 47.1, "fromGrade": "D", "to": 47.3, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.3, "from": 47.4, "fromGrade": "D", "to": 47.1, "toGrade": "D" } ] }, "job": { "capability": "voice.agent", "name": "Voice agents" }, "others": [ { "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-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-inworld-realtime.json", "title": "AssemblyAI Voice Agent API vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-vogent.json", "title": "AssemblyAI Voice Agent API vs Vogent API", "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-inworld-realtime.json", "title": "Bland AI API + MCP vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/bland-ai-vs-vogent.json", "title": "Bland AI API + MCP vs Vogent API", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/bolna-vs-inworld-realtime.json", "title": "Bolna API + MCP vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/bolna-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/bolna-vs-vogent.json", "title": "Bolna API + MCP vs Vogent API", "url": "https://www.anchorterminal.com/compare/bolna-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-inworld-realtime.json", "title": "Deepgram Voice Agent API vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vogent.json", "title": "Deepgram Voice Agent API vs Vogent API", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-inworld-realtime.json", "title": "ElevenLabs Agents API + MCP vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vogent.json", "title": "ElevenLabs Agents API + MCP vs Vogent API", "url": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-inworld-realtime.json", "title": "fone.me vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/fone-me-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/fone-me-vs-vogent.json", "title": "fone.me vs Vogent API", "url": "https://www.anchorterminal.com/compare/fone-me-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/gemini-live-vs-inworld-realtime.json", "title": "Gemini Live API vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/gemini-live-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/gemini-live-vs-vogent.json", "title": "Gemini Live API vs Vogent API", "url": "https://www.anchorterminal.com/compare/gemini-live-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/gpt-live-vs-inworld-realtime.json", "title": "GPT-Live vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/gpt-live-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/gpt-live-vs-vogent.json", "title": "GPT-Live vs Vogent API", "url": "https://www.anchorterminal.com/compare/gpt-live-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-inworld-realtime.json", "title": "Harmony.ai vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/harmony-ai-vs-vogent.json", "title": "Harmony.ai vs Vogent API", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/hume-evi-vs-inworld-realtime.json", "title": "Hume EVI (Empathic Voice Interface) vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/hume-evi-vs-vogent.json", "title": "Hume EVI (Empathic Voice Interface) vs Vogent API", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-livekit-agents.json", "title": "Inworld Realtime API vs LiveKit Agents", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-livekit-agents" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-openai-realtime.json", "title": "Inworld Realtime API vs OpenAI Realtime API", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-openai-realtime" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat.json", "title": "Inworld Realtime API vs Pipecat", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-placecall.json", "title": "Inworld Realtime API vs PlaceCall", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-placecall" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-retell-ai.json", "title": "Inworld Realtime API vs Retell AI API + MCP", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-retell-ai" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-rime-prism.json", "title": "Inworld Realtime API vs Rime Prism", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-synthflow.json", "title": "Inworld Realtime API vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-ultravox.json", "title": "Inworld Realtime API vs Ultravox Realtime API", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-ultravox" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vaani-voice.json", "title": "Inworld Realtime API vs Vaani Developer Platform", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vaani-voice" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vapi.json", "title": "Inworld Realtime API vs Vapi API + MCP", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vapi" }, { "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-vogent.json", "title": "LiveKit Agents vs Vogent API", "url": "https://www.anchorterminal.com/compare/livekit-agents-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-vogent.json", "title": "OpenAI Realtime API vs Vogent API", "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/pipecat-vs-vogent.json", "title": "Pipecat vs Vogent API", "url": "https://www.anchorterminal.com/compare/pipecat-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/placecall-vs-vogent.json", "title": "PlaceCall vs Vogent API", "url": "https://www.anchorterminal.com/compare/placecall-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/retell-ai-vs-vogent.json", "title": "Retell AI API + MCP vs Vogent API", "url": "https://www.anchorterminal.com/compare/retell-ai-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/rime-prism-vs-vogent.json", "title": "Rime Prism vs Vogent API", "url": "https://www.anchorterminal.com/compare/rime-prism-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/synthflow-vs-vogent.json", "title": "Synthflow API + MCP vs Vogent API", "url": "https://www.anchorterminal.com/compare/synthflow-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/ultravox-vs-vogent.json", "title": "Ultravox Realtime API vs Vogent API", "url": "https://www.anchorterminal.com/compare/ultravox-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/vaani-voice-vs-vogent.json", "title": "Vaani Developer Platform vs Vogent API", "url": "https://www.anchorterminal.com/compare/vaani-voice-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/vapi-vs-vogent.json", "title": "Vapi API + MCP vs Vogent API", "url": "https://www.anchorterminal.com/compare/vapi-vs-vogent" }, { "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-inworld-realtime.json", "title": "CueLight vs Inworld Realtime API", "url": "https://www.anchorterminal.com/compare/cuelight-vs-inworld-realtime" }, { "json": "https://www.anchorterminal.com/compare/cuelight-vs-vogent.json", "title": "CueLight vs Vogent API", "url": "https://www.anchorterminal.com/compare/cuelight-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat-phonellm.json", "title": "Inworld Realtime API vs Pipecat PhoneLLM", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat-phonellm" }, { "json": "https://www.anchorterminal.com/compare/pipecat-phonellm-vs-vogent.json", "title": "Pipecat PhoneLLM vs Vogent API", "url": "https://www.anchorterminal.com/compare/pipecat-phonellm-vs-vogent" } ], "panel": null, "scores": [ { "by": 5, "edge": "inworld-realtime", "inworld-realtime": 62, "key": "reliability", "name": "Reliability", "vogent": 57, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 13, "edge": "vogent", "inworld-realtime": 60, "key": "schema", "name": "Schema \u0026 documentation", "vogent": 73, "weight": 13 }, { "by": 11, "edge": "inworld-realtime", "inworld-realtime": 68, "key": "ergonomics", "name": "Agent ergonomics", "vogent": 57, "weight": 13 }, { "by": 32, "edge": "inworld-realtime", "inworld-realtime": 58, "key": "security", "name": "Security \u0026 auth", "vogent": 26, "weight": 14 }, { "by": 25, "edge": "inworld-realtime", "inworld-realtime": 40, "key": "payments", "name": "Payments \u0026 pricing", "vogent": 15, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 60, "edge": "inworld-realtime", "inworld-realtime": 71, "key": "maintenance", "name": "Maintenance \u0026 community", "vogent": 11, "weight": 7 }, { "by": 6, "edge": "inworld-realtime", "inworld-realtime": 63, "key": "transparency", "name": "Transparency \u0026 trust", "vogent": 57, "weight": 7 } ], "summary": "Inworld Realtime API scores 60.1 (C) on agent readiness against Vogent API's 44.9 (E), and leads in 6 of 7 scored categories. Vogent API leads on schema \u0026 documentation. Both do voice agents.", "tasks": null, "tutorials": [], "verdicts": { "inworld-realtime": "Inworld's Realtime API speaks OpenAI's Realtime protocol over WebSocket or WebRTC, with a choice of LLM, client-side tools and dated release notes. Cost is the sum of STT, LLM and TTS usage with no per-minute price, there is no machine-readable event schema, and status history couldn't be read.", "vogent": "Outbound calling with IVR detection and navigation, an OpenAPI file and idempotent dial creation. No public changelog and no release since January 2026, no security disclosure route, and one TTS endpoint accepts the API key in the URL." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent", "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent.min.md" }, "markdown": "Inworld Realtime API scores 60.1 (C) on agent readiness against Vogent API's 44.9 (E), and leads in 6 of 7 scored categories. Vogent API leads on schema \u0026 documentation. Both do voice agents.\n\n- Inworld Realtime API: grade C, 60.1/100, rank #671 of 1510. Markdown https://www.anchorterminal.com/tools/inworld-realtime.md · JSON https://www.anchorterminal.com/api/v1/tools/inworld-realtime.json\n- Vogent API: grade E, 44.9/100, rank #1209 of 1510. Markdown https://www.anchorterminal.com/tools/vogent.md · JSON https://www.anchorterminal.com/api/v1/tools/vogent.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### Inworld Realtime API (C)\n\nGood for: Teams moving off OpenAI's Realtime API who want a choice of LLM and Inworld voices.\n\nAhead on:\n- Reliability, 62 against 57\n- Agent ergonomics, 68 against 57\n- Security \u0026 auth, 58 against 26\n- Payments \u0026 pricing, 40 against 15\n- Maintenance \u0026 community, 71 against 11\n- Transparency \u0026 trust, 63 against 57\n\nWatch for: No per-minute price. A session's cost depends on STT, LLM tokens and TTS characters, and interrupted segments are still billed\n\n### Vogent API (E)\n\nGood for: Outbound calling that has to navigate IVRs in English or Spanish, in the US, Canada and the UK.\n\nAhead on:\n- Schema \u0026 documentation, 73 against 60\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No public changelog and no release found since January 2026\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Inworld Realtime API +60\n\n- Inworld Realtime API (71): Release note of 16 October 2026 (`cache_transcript`), 21 days ago (30). Three dated Realtime entries in the 90 days from 8 August, on 14 September, 23 September and 16 October (20). Discord and support@inworld.ai, with no evidence of answers read (8 of 15). Works with OpenAI's Realtime clients and the CLI is current at 1.5.0, but there is no Inworld Realtime SDK (8 of 15). CLI on npm under MIT, CI not read (5 of 10). Total 71.\n- Vogent API (11): The newest release found is web client v0.1.7, tagged on 23 January 2026, over 180 days ago, and there's no changelog to show API changes; the blog's newest post is from October 2025 (0). No releases found in the last 90 days (0). No public changelog or issue tracker, and we didn't test support (3 of 15). One official SDK, the web client (5 of 15). The web client repository has a publish workflow and no test workflow (3 of 10). 0+0+3+5+3 = 11.\n\n### Security \u0026 auth: Inworld Realtime API +32\n\n- Inworld Realtime API (58): Workspace API keys sent as Basic credentials, deleted to revoke, with separate keys per environment advised. The CLI mints read-only keys unless `--write` is given, but write toggles cover only the Voice and Router APIs, so no key is limited to one product. Browsers use short-lived tokens minted server side. Session IDs, not secrets, go in the URL (25 of 30). Tools run in the client, so the developer approves side effects, with no approval step in the API (10 of 20). The agent listens to callers and passes their speech to an LLM, and no prompt-injection guidance was found (5 of 15). Usage per key and a Performance page with errors and throttling (8 of 15). SOC 2 Type II and HIPAA claimed and a vulnerability report form, with no security.txt or bug bounty, per the 4 November reading (10 of 20). Total 58. Zero data retention covers session content from the Developer plan up, but not requests routed to third-party LLM providers.\n- Vogent API (26): Bearer keys created per user, which stop working when that user leaves the workspace, with no scopes (20). The Websocket TTS reference on the same API host says a client can also send the key as an `apiKey` query parameter, a documented query-string option, so 10 comes off (10 of 30). No read-only keys or approval step (3 of 20). Agents hear callers and we found no prompt-injection guidance (5 of 15). Dial history per call, no audit log found (8 of 15). Webhooks are signed with HMAC-SHA256 in `X-Elto-Signature`, but security.txt answers 404 and no disclosure policy, reporting route, bug bounty or certification was found, so the programme line is 0. 10+3+5+8+0 = 26.\n\n### Payments \u0026 pricing: Inworld Realtime API +25\n\n- Inworld Realtime API (40): No x402, MPP or L402 (0). No per-session price, but each billed part (STT per hour, TTS per character, LLM per token) is priced publicly (20). On-Demand includes free STT and TTS allowances and lists no payment method, though some premium LLMs need a card on file (20). A person signs up in a browser before a key exists (0). Total 40.\n- Vogent API (15): No x402, MPP or L402 (0 of 40). Per-second rates are public, $0.09 a minute on standard voices and $0.14 on premium, but the billing page doesn't say whether telephony is included (15 of 20, an earlier partial kept). No free tier or trial stated (0). Access starts with a human signup (0). 0+15+0+0 = 15.\n\n### Schema \u0026 documentation: Vogent API +13\n\n- Inworld Realtime API (60): No AsyncAPI or other machine-readable file for the socket, and the spec paths redirect (0). llms.txt, Markdown twins and a docs MCP server (10). The overview, OpenAI migration guide, `providerData` reference and the billing page's account of how a session is counted say what to use when (16 of 20). The reference lists every client and server event with field types and required marks, as text rather than a schema (12 of 15). JavaScript and Python example projects and an error event with `type`, `code` and `param`, without a list of codes (9 of 15). Dated release notes with affected clients and required actions, but no API version beyond `/v1` (13 of 15). Total 60.\n- Vogent API (73): OpenAPI 3.0.3 file (version 1.0.11, 42 paths, 65 operations) and an AsyncAPI file, both linked from llms.txt (25). llms.txt with 117 page links and Markdown pages (10). Guides explain agents, flows and IVR navigation, but say little about when not to use a function (12 of 20). Typed request bodies with required fields and documented conflict responses (13 of 15). Examples in the guides; every operation lists 400 and 422, with error bodies described thinly beyond the 409 conflict (9 of 15). The spec carries a version number, but there's no public changelog (4 of 15). 25+10+12+13+9+4 = 73.\n\n### Agent ergonomics: Inworld Realtime API +11\n\n- Inworld Realtime API (68): Scored as an API. Conversation history defaults to the last 100 items, can be trimmed, and can be cached on Anthropic models, and every `response.done` carries a `usage` block (18 of 25). No lists to page. Output controls are modalities, turn detection settings, optional transcription and `response.speak` (12 of 20). Error events follow OpenAI's `type` and `code` shape, unsupported fields come back as non-fatal `unsupported_field` warnings, and `item_not_found` names the bad parameter (14 of 20). Tools run on the client and a follow-up response starts automatically after a tool result. Nothing covers side effects of a tool call cut off by an interruption (12 of 20). Works with OpenAI Realtime clients after changing the URL and key, with no Inworld Realtime SDK (12 of 15). Total 68.\n- Vogent API (57): Scored as an API, since there's no MCP server. Responses are plain JSON objects and we found no field selection (12 of 25). Some list endpoints page by cursor, and filters are limited (12 of 20). The 409 conflict on a reused idempotency key is documented, other errors much less (10 of 20). Dial creation is idempotent with `idempotencyKey` (15 of 20). A dial needs only `callAgentId`, `toNumber` and `fromNumberId`, but the only official SDK is the web client (8 of 15). 12+12+10+15+8 = 57.\n\n### Transparency \u0026 trust: Inworld Realtime API +6\n\n- Inworld Realtime API (63): Closed service with clear terms naming Theai, Inc. dba Inworld AI (15). The ZDR page says what a session keeps and that third-party LLM requests aren't covered, but the terms and privacy notice disagree on training (12 of 30). Release notes flag potentially breaking changes with the clients affected and what to do, without stating a notice period (14 of 20). US headquarters with EU and India residency on Enterprise, and no sub-processor list in the docs, while sessions may route to third-party LLM providers (10 of 20). Total 51.\n- Vogent API (57): Closed platform. Per the 30 September check, the terms and privacy notice name Monoid, Inc. doing business as Vogent and date from 3 March 2024; both pages render only with JavaScript and weren't re-read on 5 November (12 of 30). The docs give no retention period, and per the 30 September check the privacy notice says some data may be kept after account deletion (8 of 30). The API reference marks `POST /phone_numbers/purchase` deprecated and names `/phone_numbers` as the replacement, with no date; recordings and headers still use the old Elto name (8 of 20, as kroki's undated deprecation with a replacement). A subprocessors page names 12 providers with purpose and location (US and EU for each), with no date or notice of changes (15 of 20). 12+8+8+15 = 43.\n\n## Score by category\n\n| Category | Weight | Inworld Realtime API | Vogent API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 62 | 57 | Inworld Realtime API +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 60 | 73 | Vogent API +13 |\n| Agent ergonomics | 13% (16.2 this run) | 68 | 57 | Inworld Realtime API +11 |\n| Security \u0026 auth | 14% (17.5 this run) | 58 | 26 | Inworld Realtime API +32 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 15 | Inworld Realtime API +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 71 | 11 | Inworld Realtime API +60 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 57 | Inworld Realtime API +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **60.1 · C** | **44.9 · E** | |\n\n## Facts side by side\n\n| Fact | Inworld Realtime API | Vogent API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Inworld AI | Vogent |\n| Hosted endpoint | no (local only) | `https://api.vogent.ai/api` |\n| Transports | websocket, HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Pay per use |\n| Price for voice agents | $25 per 1M characters | not published |\n| x402 | no | no |\n| Tools exposed | 0 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-16 | 2026-01-23 |\n| Terms last updated | 2025-06-11 | couldn't be read |\n| Privacy policy last updated | 2026-01-18 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Agent reviews | none | 2/5 (2) |\n\n## How the scores have moved\n\n### Inworld Realtime API\n\nNo score change since it was listed.\n\n### Vogent API\n\n- -2.4 on 5 November 2026 (D to E): new evidence, correction\n- +0.2 on 27 October 2026: checklist\n- -0.3 on 8 October 2026: checklist\n\n## Verdicts\n\n**Inworld Realtime API.** Inworld's Realtime API speaks OpenAI's Realtime protocol over WebSocket or WebRTC, with a choice of LLM, client-side tools and dated release notes. Cost is the sum of STT, LLM and TTS usage with no per-minute price, there is no machine-readable event schema, and status history couldn't be read.\n\n**Vogent API.** Outbound calling with IVR detection and navigation, an OpenAPI file and idempotent dial creation. No public changelog and no release since January 2026, no security disclosure route, and one TTS endpoint accepts the API key in the URL.\n\n## Before you call either\n\n### Inworld Realtime API\n\n1. Set the auto follow-up off if your client sends its own `response.create` after a tool result, or replies double\n2. Read `response.done` usage as an estimate and mute input audio when nobody speaks, since STT bills every second sent\n3. Use `response.speak` for fixed greetings, which skips the LLM\n4. Treat `unsupported_field` errors as warnings and keep the session open\n5. Mint browser session tokens on your server and never ship the Basic credential to a client\n\n### Vogent API\n\n1. Send an `idempotencyKey` on `POST /dials`, a reused key returns 409\n2. Create a call with `callAgentId`, plus `toNumber` and `fromNumberId` for phone calls\n3. Send the key in the `Authorization` header on the TTS websocket, not the `apiKey` query parameter\n4. Verify webhooks with the HMAC in `X-Elto-Signature`\n5. Expect new dials to fail at the workspace's concurrent dial limit until calls end\n\n## Questions\n\n### Which is better for AI agents, Inworld Realtime API or Vogent API?\n\nInworld Realtime API scores 60.1 (C) on agent readiness against Vogent API's 44.9 (E), and leads in 6 of 7 scored categories. Vogent API leads on schema \u0026 documentation.\n\n### Do Inworld Realtime API and Vogent API need an API key?\n\nBoth need an API key.\n\n### Can an agent call Inworld Realtime API and Vogent API without installing anything?\n\nNo hosted endpoint is listed for Inworld Realtime API. Vogent API has a hosted endpoint at https://api.vogent.ai/api.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent.json, and with the fewest tokens: https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"inworld-realtime\", \"b\": \"vogent\"}`. From a terminal: `anchor compare inworld-realtime vogent`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/inworld-realtime.json and https://www.anchorterminal.com/api/v1/tools/vogent.json\n\n## Other comparisons with Inworld Realtime API or Vogent API\n\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 Vogent API](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vogent.md)\n- [AssemblyAI Voice Agent API vs Inworld Realtime API](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-inworld-realtime.md)\n- [AssemblyAI Voice Agent API vs Vogent API](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-vogent.md)\n- [Bland AI API + MCP vs Inworld Realtime API](https://www.anchorterminal.com/compare/bland-ai-vs-inworld-realtime.md)\n- [Bland AI API + MCP vs Vogent API](https://www.anchorterminal.com/compare/bland-ai-vs-vogent.md)\n- [Bolna API + MCP vs Inworld Realtime API](https://www.anchorterminal.com/compare/bolna-vs-inworld-realtime.md)\n- [Bolna API + MCP vs Vogent API](https://www.anchorterminal.com/compare/bolna-vs-vogent.md)\n- [Deepgram Voice Agent API vs Inworld Realtime API](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-inworld-realtime.md)\n- [Deepgram Voice Agent API vs Vogent API](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vogent.md)\n- [ElevenLabs Agents API + MCP vs Inworld Realtime API](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-inworld-realtime.md)\n- [ElevenLabs Agents API + MCP vs Vogent API](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vogent.md)\n- [fone.me vs Inworld Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-inworld-realtime.md)\n- [fone.me vs Vogent API](https://www.anchorterminal.com/compare/fone-me-vs-vogent.md)\n- [Gemini Live API vs Inworld Realtime API](https://www.anchorterminal.com/compare/gemini-live-vs-inworld-realtime.md)\n- [Gemini Live API vs Vogent API](https://www.anchorterminal.com/compare/gemini-live-vs-vogent.md)\n- [GPT-Live vs Inworld Realtime API](https://www.anchorterminal.com/compare/gpt-live-vs-inworld-realtime.md)\n- [GPT-Live vs Vogent API](https://www.anchorterminal.com/compare/gpt-live-vs-vogent.md)\n- [Harmony.ai vs Inworld Realtime API](https://www.anchorterminal.com/compare/harmony-ai-vs-inworld-realtime.md)\n- [Harmony.ai vs Vogent API](https://www.anchorterminal.com/compare/harmony-ai-vs-vogent.md)\n- [Hume EVI (Empathic Voice Interface) vs Inworld Realtime API](https://www.anchorterminal.com/compare/hume-evi-vs-inworld-realtime.md)\n- [Hume EVI (Empathic Voice Interface) vs Vogent API](https://www.anchorterminal.com/compare/hume-evi-vs-vogent.md)\n- [Inworld Realtime API vs LiveKit Agents](https://www.anchorterminal.com/compare/inworld-realtime-vs-livekit-agents.md)\n- [Inworld Realtime API vs OpenAI Realtime API](https://www.anchorterminal.com/compare/inworld-realtime-vs-openai-realtime.md)\n- [Inworld Realtime API vs Pipecat](https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat.md)\n- [Inworld Realtime API vs PlaceCall](https://www.anchorterminal.com/compare/inworld-realtime-vs-placecall.md)\n- [Inworld Realtime API vs Retell AI API + MCP](https://www.anchorterminal.com/compare/inworld-realtime-vs-retell-ai.md)\n- [Inworld Realtime API vs Rime Prism](https://www.anchorterminal.com/compare/inworld-realtime-vs-rime-prism.md)\n- [Inworld Realtime API vs Synthflow API + MCP](https://www.anchorterminal.com/compare/inworld-realtime-vs-synthflow.md)\n- [Inworld Realtime API vs Ultravox Realtime API](https://www.anchorterminal.com/compare/inworld-realtime-vs-ultravox.md)\n- [Inworld Realtime API vs Vaani Developer Platform](https://www.anchorterminal.com/compare/inworld-realtime-vs-vaani-voice.md)\n- [Inworld Realtime API vs Vapi API + MCP](https://www.anchorterminal.com/compare/inworld-realtime-vs-vapi.md)\n- [Inworld Realtime API vs Vocily AI](https://www.anchorterminal.com/compare/inworld-realtime-vs-vocily.md)\n- [LiveKit Agents vs Vogent API](https://www.anchorterminal.com/compare/livekit-agents-vs-vogent.md)\n- [OpenAI Realtime API vs Vogent API](https://www.anchorterminal.com/compare/openai-realtime-vs-vogent.md)\n- [Pipecat vs Vogent API](https://www.anchorterminal.com/compare/pipecat-vs-vogent.md)\n- [PlaceCall vs Vogent API](https://www.anchorterminal.com/compare/placecall-vs-vogent.md)\n- [Retell AI API + MCP vs Vogent API](https://www.anchorterminal.com/compare/retell-ai-vs-vogent.md)\n- [Rime Prism vs Vogent API](https://www.anchorterminal.com/compare/rime-prism-vs-vogent.md)\n- [Synthflow API + MCP vs Vogent API](https://www.anchorterminal.com/compare/synthflow-vs-vogent.md)\n- [Ultravox Realtime API vs Vogent API](https://www.anchorterminal.com/compare/ultravox-vs-vogent.md)\n- [Vaani Developer Platform vs Vogent API](https://www.anchorterminal.com/compare/vaani-voice-vs-vogent.md)\n- [Vapi API + MCP vs Vogent API](https://www.anchorterminal.com/compare/vapi-vs-vogent.md)\n- [Vocily AI vs Vogent API](https://www.anchorterminal.com/compare/vocily-vs-vogent.md)\n- [CueLight vs Inworld Realtime API](https://www.anchorterminal.com/compare/cuelight-vs-inworld-realtime.md)\n- [CueLight vs Vogent API](https://www.anchorterminal.com/compare/cuelight-vs-vogent.md)\n- [Inworld Realtime API vs Pipecat PhoneLLM](https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat-phonellm.md)\n- [Pipecat PhoneLLM vs Vogent API](https://www.anchorterminal.com/compare/pipecat-phonellm-vs-vogent.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": "Inworld Realtime API vs Vogent API", "url": "" } ], "description": "Inworld Realtime scores 60.1 (C) to Vogent's 44.9 (E) for voice agents. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Inworld Realtime API C 60.1", "Vogent API E 44.9", "scores" ], "h1": "Inworld Realtime API vs Vogent API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/inworld-realtime-vs-vogent", "published": "2026-10-01", "section": "tools", "title": "Inworld Realtime vs Vogent for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent" }, "tokens": { "markdown": 5050, "slim": 2580 }, "version": 1 }