# Inworld Realtime API > 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. - Canonical: https://www.anchorterminal.com/tools/inworld-realtime - Pricing: https://www.anchorterminal.com/tools/inworld-realtime#pricing - Reviews: https://www.anchorterminal.com/tools/inworld-realtime#reviews - Markdown: https://www.anchorterminal.com/tools/inworld-realtime.md (~7,400 tokens) - Slim: https://www.anchorterminal.com/tools/inworld-realtime.min.md (~1,430 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/inworld-realtime.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT inworld-realtime.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-07 ## Overview **Grade C · 60.1/100 · rank #671 of 1510 · #12 in Conversational voice agents · not agent-ready · confidence medium** More from Inworld AI, listed separately because each is its own product: [Inworld STT](https://www.anchorterminal.com/tools/inworld-stt.md) (Speech-to-text), [Inworld Realtime TTS-2](https://www.anchorterminal.com/tools/inworld-tts.md) (Text-to-speech), [Inworld Instant Voice Cloning](https://www.anchorterminal.com/tools/inworld-voice-cloning.md) (Voice cloning & custom voices). ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Inworld AI (https://inworld.ai) | | Kind | HTTP API | | Category | Conversational voice agents (https://www.anchorterminal.com/categories/voice-agents) | | Transport | websocket, HTTP | | Auth | API key · 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 | Pay per use (Pay per use) · 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. | | x402 | No · 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. | | Licence | unknown | | Tools exposed | 0 | | Packages | npm: `@inworld/cli` | | Docs | https://docs.inworld.ai/realtime/overview | | llms.txt | https://docs.inworld.ai/llms.txt | | Last release | 2026-10-16 | | Surface listed | The Realtime API at api.inworld.ai, read from docs.inworld.ai (llms.txt, Markdown guides, the WebSocket and WebRTC reference, Realtime release notes) and inworld.ai/pricing on 6 November 2026, with terms, privacy, security and status as read for inworld-tts on 4 November. No account was made and no session was opened | | Architecture | A pipeline, not a single speech-to-speech model. STT (`inworld/inworld-stt-1` by default), an LLM the developer picks through Inworld's router, and Inworld TTS, each billed as its own line | | Session controls | Semantic and server VAD, interruptions, client-side tool calling with automatic follow-up responses, `response.speak` for scripted text without the LLM, back-channel interjections, filler responses and prompt caching on Anthropic models | | Same company | Inworld TTS is listed as inworld-tts and Inworld STT as inworld-stt. Ultravox, which Inworld acquired, is listed separately as ultravox and runs its own speech model | | Releases | Dated Realtime release notes on 21 July, 14 September, 23 September and 16 October 2026 | | Capabilities | voice.agent, voice.pipeline, voice.tools, voice.telephony | | Tags | hosted, usage, free-tier, closed-source, llms-txt, streaming, websocket, webrtc, openai-compatible, enterprise | | JSON | https://www.anchorterminal.com/api/v1/tools/inworld-realtime.json | ## Score breakdown (methodology v0.7, October 2026 research run) Assessed 2026-11-06 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 62 | 12.4 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 60 | 9.8 | | Agent ergonomics | 13% | 16.2 | 68 | 11.1 | | Security & auth | 14% | 17.5 | 58 | 10.2 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 71 | 6.2 | | Transparency & trust (editorial 51, provenance 75) | 7% | 8.8 | 63 | 5.5 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **60.1 → C** | ### Why each score - Reliability 62 (checked 2026-11-06): Hosted reading of the checklist. status.inworld.ai is a public status page (20), with history we couldn't read, as on inworld-tts (5). Concurrent sessions are published per plan, 10 on On-Demand up to 1,000 on Growth (15). The rate limits page gives exponential backoff with jitter and Retry-After on longer windows, and sessions emit `rate_limits.updated`, with nothing on reconnecting a dropped session (12 of 15). An SLA appears only in the Enterprise column, with no terms (0). No preview or beta label on the Realtime API (10). 20 + 5 + 15 + 12 + 0 + 10 = 62. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 60 (checked 2026-11-06): 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. - Agent ergonomics 68 (checked 2026-11-06): 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. - Security & auth 58 (checked 2026-11-06): 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. - Payments & pricing 40 (checked 2026-11-06): 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. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 71 (checked 2026-11-06): 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. - Transparency & trust 63 (checked 2026-11-06): 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. Fix list, everything this grade says the listing lacks, the biggest gain first (15 items). What it covers is at https://www.anchorterminal.com/fixes/inworld-realtime.md (JSON https://www.anchorterminal.com/fixes/inworld-realtime.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "inworld-realtime", "plan": "read"}`, free while the beta runs ### What we couldn't check - unchecked: status history, because status.inworld.ai draws on GitHub issues our reader can't open - Whether the 21 July 2026 compatibility changes were announced before they shipped; the release note is dated the same day and no earlier notice was found - unchecked: maximum session length and reconnect behaviour, which weren't found in the reference ### Sources - llms.txt docs index: (seen 2026-11-06) - billing, plan limits and free usage: (seen 2026-11-06) - pricing page: (seen 2026-11-06) - rate limits and 429 handling: (seen 2026-11-06) - zero data retention: (seen 2026-11-06) - Inworld CLI and MCP server: (seen 2026-11-06) - CLI on npm: (seen 2026-11-06) - terms, privacy, security and status, per the inworld-tts check: (seen 2026-11-04) - Realtime overview: (seen 2026-11-06) - WebSocket connection: (seen 2026-11-06) - Realtime WebSocket reference: (seen 2026-11-06) - Realtime release notes: (seen 2026-11-06) - OpenAI migration: (seen 2026-11-06) - tool calling: (seen 2026-11-06) ## Score history Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/inworld-realtime/history.json - 2026-11-06: graded 60.1 C (methodology 0.7) ## Who's behind it (provenance 75/100, checked 2026-11-06) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Theai, Inc. dba Inworld AI | 20/20 | | Domain age | inworld.ai, no registry record we could read | 0/15 | | Endpoint on the vendor's domain | inworld.ai | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects | 9.1/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.inworld.ai | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | | People named | 3 named with their role, none with a public profile | 7/10 | | Support route | a support address, help pages, a community | 5/5 | 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. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://inworld.ai/terms), read 2026-10-30, dated 2025-06-11, states 6 of the 7 things a reader expects. - Gives the date it was last updated. Last updated 2025-06-11. - Names the governing law or courts. Disputes go to the courts of Santa Clara, California. - States a limit on its liability. Capped at the greater of $100 and the fees paid in the 12 months before the claim. - Says how changes to the terms are announced. Gives 30 days of notice before a change. - Not found in the text. Refers to a service level or uptime commitment. **Privacy policy** (https://inworld.ai/privacy), read 2026-10-30, dated 2026-01-18, states 7 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "Some of the activities described in this section may constitute “targeted advertising,” “sharing,” or “selling” under certain laws." - Gives the date it was last updated. Last updated 2026-01-18. - Says how long data is kept. For as long as needed, with no period named. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. privacy@inworld.ai. - Not found in the text. Says where data is transferred or stored. ## Humans behind the project (researched 2026-11-06 from public pages, not part of the grade) ### Key people - Kylan Gibbs, Co-founder and CEO - Ilya Gelfenbeyn, Co-founder - Michael Ermolenko, Co-founder - Note: Copied on 6 November 2026 from the inworld-tts listing's humans file (checked 30 October 2026), since the company is the same. Inworld's Realtime TTS-2 page, read 30 October 2026, quotes Kylan Gibbs as CEO of Inworld AI. Inworld's Series A release of 23 August 2022, as published by Intel Capital, names Ilya Gelfenbeyn, Michael Ermolenko and Kylan Gibbs as founders and Ilya Gelfenbeyn as CEO at the time. No about or team page was found in the inworld.ai sitemap, so the present roles of the other two founders aren't established and the roster may be incomplete. No personal accounts are linked from Inworld's pages, so none are listed. The 28 October 2026 Reasoning post is signed by the Inworld TTS team. The ultravox listing's humans file records Inworld's announcement of 30 September 2026 that it acquired Ultravox. Investors come from the Series A release as published by Intel Capital and from The SaaS News report of the August 2023 round led by Lightspeed. Business Wire and GlobeNewswire, which carry Inworld's own releases, answered robots.txt with 403 and weren't read, so the pre-seed and seed rounds aren't itemised, and Meta is listed without a round. GamesBeat's report of 2 August 2023, read on 6 November 2026, says the Lightspeed round brought the valuation to over $500 million and quotes Kylan Gibbs on over $100 million in total funding, so both are recorded as stated for that round; it also names the Disney Accelerator and NTT Docomo Ventures among investors to date. No later round was found on inworld.ai's sitemap or in a web search on 6 November 2026. - Inworld AI (Theai, Inc.): LinkedIn https://www.linkedin.com/company/inworld-ai X https://x.com/inworld GitHub https://github.com/inworld-ai ### Ownership and investors - Raised: over $100M in total, as of August 2023 (source https://gamesbeat.com/inworld-ai-raises-new-round-at-500m-valuation-for-ai-game-characters/) - Valuation: over $500M as announced (the source doesn't say pre- or post-money), August 2023 round led by Lightspeed, August 2023 (source https://gamesbeat.com/inworld-ai-raises-new-round-at-500m-valuation-for-ai-game-characters/) - Backed by: Section 32, Intel, Lightspeed Venture Partners, Founders Fund, Accelerator Investments LLC, First Spark Ventures, Kleiner Perkins, BITKRAFT Ventures, CRV, Microsoft, Micron, LG, SK Telecom, The Venture Reality Fund, HTC, Meta, Stanford University, Samsung, The Walt Disney Company, NTT DOCOMO ### Getting support - Discord: https://discord.gg/inworld - Support email: support@inworld.ai - Help: https://docs.inworld.ai/portal/support - Help: https://docs.inworld.ai/ - Sources: https://inworld.ai/blog/realtime-tts-2, https://inworld.ai/blog/realtime-tts-2-reasoning-speed-consistency, https://inworld.ai/pricing, https://inworld.ai/terms, https://inworld.ai/security, https://inworld.ai/sitemap.xml, https://docs.inworld.ai/portal/support.md, https://www.intelcapital.com/inworld-ai-closes-50m-series-a-to-populate-video-games-and-the-metaverse-with-interactive-ai-driven-characters/, https://gamesbeat.com/inworld-ai-raises-new-round-at-500m-valuation-for-ai-game-characters/ ## Live (updated 2026-11-07 16:01 UTC) - Vendor status page: not read, no machine-readable status found - npm `@inworld/cli` 1.5.0 - security.txt: none - Watching changelog - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/inworld-realtime.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Speech recognition in a session | $0.0025 | per minute of audio | STT-1 at $0.15 an hour On-Demand, $0.10 on paid plans | | Agent speech, TTS-2 | $25 | per 1M characters | free On-Demand plan; lower on paid plans | Across all listings: https://www.anchorterminal.com/prices/index.md ## 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 ## Before you call it (notes for agents) 1. Set the auto follow-up off if your client sends its own `response.create` after a tool result, or replies double 2. Read `response.done` usage as an estimate and mute input audio when nobody speaks, since STT bills every second sent 3. Use `response.speak` for fixed greetings, which skips the LLM 4. Treat `unsupported_field` errors as warnings and keep the session open 5. Mint browser session tokens on your server and never ship the Basic credential to a client ## Connect Install: ```bash npm install -g @inworld/cli ``` Through letme: https://letme.dev/inworld-realtime. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | LiveKit Agents | BB | 72.7 | 120 | voice.agent, voice.pipeline, voice.tools, voice.telephony | no | https://www.anchorterminal.com/tools/livekit-agents.md | | ElevenLabs Agents API + MCP | BB | 72.6 | 122 | voice.agent, voice.pipeline, voice.tools, voice.telephony | no | https://www.anchorterminal.com/tools/elevenlabs-agents.md | | Bland AI API + MCP | B | 67 | 343 | voice.agent, voice.pipeline, voice.tools, voice.telephony | no | https://www.anchorterminal.com/tools/bland-ai.md | | Retell AI API + MCP | B | 66.2 | 379 | voice.agent, voice.pipeline, voice.tools, voice.telephony | no | https://www.anchorterminal.com/tools/retell-ai.md | | Pipecat | B | 65.2 | 428 | voice.agent, voice.pipeline, voice.tools, voice.telephony | no | https://www.anchorterminal.com/tools/pipecat.md | | Vapi API + MCP | B | 64.7 | 459 | voice.agent, voice.pipeline, voice.tools, voice.telephony | no | https://www.anchorterminal.com/tools/vapi.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - WebSocket at `wss://api.inworld.ai/api/v1/realtime/session?key=&protocol=realtime` and WebRTC through `POST /v1/realtime/calls` (source: ) - Follows OpenAI's Realtime event shapes, with a migration guide and Inworld extensions under `providerData` (source: ) - Concurrent sessions of 10 on On-Demand up to 1,000 on Growth (source: ) - Release notes of 21 July 2026 list potentially breaking changes to align with OpenAI's protocol, each with affected clients and required action (source: ) - Zero data retention covers Realtime sessions, but not requests routed to third-party LLM providers (source: ) - A Twilio Media Streams guide connects phone calls (source: ) - #12 of 27 in Best conversational voice-agent APIs: https://www.anchorterminal.com/best/voice-agents/index.md - All 518 voice agents comparisons: https://www.anchorterminal.com/compare/voice-agents/index.md ## Compare - [Amazon Nova 2 Sonic vs Inworld Realtime API](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-inworld-realtime.md): B 67.6 vs C 60.1 - [AssemblyAI Voice Agent API vs Inworld Realtime API](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-inworld-realtime.md): C 56.4 vs C 60.1 - [Bland AI API + MCP vs Inworld Realtime API](https://www.anchorterminal.com/compare/bland-ai-vs-inworld-realtime.md): B 67 vs C 60.1 - [Bolna API + MCP vs Inworld Realtime API](https://www.anchorterminal.com/compare/bolna-vs-inworld-realtime.md): E 44.7 vs C 60.1 - [Deepgram Voice Agent API vs Inworld Realtime API](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-inworld-realtime.md): BB 72.2 vs C 60.1 - [ElevenLabs Agents API + MCP vs Inworld Realtime API](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-inworld-realtime.md): BB 72.6 vs C 60.1 - [fone.me vs Inworld Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-inworld-realtime.md): F 28.3 vs C 60.1 - [Gemini Live API vs Inworld Realtime API](https://www.anchorterminal.com/compare/gemini-live-vs-inworld-realtime.md): C 54.1 vs C 60.1 - [GPT-Live vs Inworld Realtime API](https://www.anchorterminal.com/compare/gpt-live-vs-inworld-realtime.md): BB 70.6 vs C 60.1 - [Harmony.ai vs Inworld Realtime API](https://www.anchorterminal.com/compare/harmony-ai-vs-inworld-realtime.md): E 43.4 vs C 60.1 - [Hume EVI (Empathic Voice Interface) vs Inworld Realtime API](https://www.anchorterminal.com/compare/hume-evi-vs-inworld-realtime.md): C 54.1 vs C 60.1 - [Inworld Realtime API vs LiveKit Agents](https://www.anchorterminal.com/compare/inworld-realtime-vs-livekit-agents.md): C 60.1 vs BB 72.7 - [Inworld Realtime API vs OpenAI Realtime API](https://www.anchorterminal.com/compare/inworld-realtime-vs-openai-realtime.md): C 60.1 vs BB 71.7 - [Inworld Realtime API vs Pipecat](https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat.md): C 60.1 vs B 65.2 - [Inworld Realtime API vs PlaceCall](https://www.anchorterminal.com/compare/inworld-realtime-vs-placecall.md): C 60.1 vs C 54 - [Inworld Realtime API vs Retell AI API + MCP](https://www.anchorterminal.com/compare/inworld-realtime-vs-retell-ai.md): C 60.1 vs B 66.2 - [Inworld Realtime API vs Rime Prism](https://www.anchorterminal.com/compare/inworld-realtime-vs-rime-prism.md): C 60.1 vs C 59.7 - [Inworld Realtime API vs Synthflow API + MCP](https://www.anchorterminal.com/compare/inworld-realtime-vs-synthflow.md): C 60.1 vs D 47.3 - [Inworld Realtime API vs Ultravox Realtime API](https://www.anchorterminal.com/compare/inworld-realtime-vs-ultravox.md): C 60.1 vs C 59.2 - [Inworld Realtime API vs Vaani Developer Platform](https://www.anchorterminal.com/compare/inworld-realtime-vs-vaani-voice.md): C 60.1 vs E 44.6 - [Inworld Realtime API vs Vapi API + MCP](https://www.anchorterminal.com/compare/inworld-realtime-vs-vapi.md): C 60.1 vs B 64.7 - [Inworld Realtime API vs Vocily AI](https://www.anchorterminal.com/compare/inworld-realtime-vs-vocily.md): C 60.1 vs D 53.9 - [Inworld Realtime API vs Vogent API](https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent.md): C 60.1 vs E 44.9 - [CueLight vs Inworld Realtime API](https://www.anchorterminal.com/compare/cuelight-vs-inworld-realtime.md): D 47.8 vs C 60.1 - [Inworld Realtime API vs Pipecat PhoneLLM](https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat-phonellm.md): C 60.1 vs C 60.4 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on inworld.ai or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "inworld-realtime", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Inworld Realtime API on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Inworld Realtime API on Anchor Terminal](https://www.anchorterminal.com/badges/inworld-realtime.svg)](https://www.anchorterminal.com/tools/inworld-realtime) ``` Plain link: ```html Inworld Realtime API on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Inworld Realtime API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/inworld-realtime-dark.png - Light: https://www.anchorterminal.com/assets/share/inworld-realtime-light.png --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp