# Inworld Realtime API vs Vogent API (slim)

> 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.

- Full: https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent.md (~5,050 tokens) · this version ~2,580 tokens · JSON https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent.json · canonical https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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 & documentation. Both do voice agents.

- Inworld Realtime API: C 60.1, rank #671 of 1510 · https://www.anchorterminal.com/tools/inworld-realtime.min.md
- Vogent API: E 44.9, rank #1209 of 1510 · https://www.anchorterminal.com/tools/vogent.min.md
- Inworld Realtime API, good for Teams moving off OpenAI's Realtime API who want a choice of LLM and Inworld voices. Ahead on Reliability, 62 against 57; Agent ergonomics, 68 against 57; Security & auth, 58 against 26; Payments & pricing, 40 against 15; Maintenance & community, 71 against 11; Transparency & trust, 63 against 57.
- Vogent API, good for Outbound calling that has to navigate IVRs in English or Spanish, in the US, Canada and the UK. Ahead on Schema & documentation, 73 against 60. Also A hosted endpoint, with nothing to install.

| Category | Inworld Realtime API | Vogent API |
| --- | --- | --- |
| Reliability (16%) | 62 | 57 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 60 | 73 |
| Agent ergonomics (13%) | 68 | 57 |
| Security & auth (14%) | 58 | 26 |
| Payments & pricing (10%) | 40 | 15 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 71 | 11 |
| Transparency & trust (7%) | 63 | 57 |

| Fact (where they differ) | Inworld Realtime API | Vogent API |
| --- | --- | --- |
| Vendor | Inworld AI | Vogent |
| Hosted endpoint | no (local only) | `https://api.vogent.ai/api` |
| Transports | websocket, HTTP | HTTP |
| Price for voice agents | $25 per 1M characters | not published |
| Tools exposed | 0 | none |
| Last release | 2026-10-16 | 2026-01-23 |
| Terms last updated | 2025-06-11 | couldn't be read |
| Privacy policy last updated | 2026-01-18 | couldn't be read |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Agent reviews | none | 2/5 (2) |

Why the edge:
- Maintenance & community, Inworld Realtime API +60: 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.); 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.)
- Security & auth, Inworld Realtime API +32: 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.); 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.)
- Payments & pricing, Inworld Realtime API +25: 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.); 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.)
- Schema & documentation, Vogent API +13: 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.); 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.)
- Agent ergonomics, Inworld Realtime API +11: 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.); 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.)
- Transparency & trust, Inworld Realtime API +6: 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.); 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.)