{ "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": "Pipecat scores 65.2 (B) on agent readiness against Inworld Realtime API's 60.1 (C), and leads in every scored category.", "b": { "slug": "pipecat", "name": "Pipecat", "vendor": "Daily", "vendorUrl": "https://www.pipecat.ai/", "kind": "framework", "category": "voice-agents", "summary": "Pipecat is Daily's open-source Python framework for real-time voice and multimodal agents, built as pipelines of transport, speech-to-text, LLM and text-to-speech services, with client SDKs and optional hosting on Pipecat Cloud.", "url": "https://www.anchorterminal.com/tools/pipecat", "markdownUrl": "https://www.anchorterminal.com/tools/pipecat.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/pipecat.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/pipecat.json", "dns": "pipecat.grade.anchorterminal.com", "repo": "https://github.com/pipecat-ai/pipecat", "license": "BSD-2-Clause for the framework. Pipecat Cloud is a hosted service under Daily's terms of service", "transports": [], "packages": [ { "registry": "pypi", "name": "pipecat-ai" }, { "registry": "npm", "name": "@pipecat-ai/client-js" } ], "auth": "none", "authNotes": "The framework has no account or key of its own and runs in the developer's process. Each service takes its provider's key, such as `DEEPGRAM_API_KEY` or `CARTESIA_API_KEY`, passed in code. Pipecat Cloud uses public and private API keys as bearer tokens, CLI login and email with a one-time code for the dashboard.", "pricing": "free", "pricingNotes": "Free under BSD-2-Clause, with no signup. The developer pays each model, speech and transport provider. Pipecat Cloud, if used, bills from $0.01 per active agent minute for agent-1x, with Daily PSTN at $0.018 a minute and 1:1 Daily WebRTC voice free (https://www.daily.co/pricing/pipecat-cloud/, read 17 October 2026).", "priceSummary": "Free · OSS", "where": "library", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the framework source, the docs or the Pipecat Cloud pricing page (checked 17 October 2026).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 16314, "npmWeekly": 97617, "pypiWeekly": 302047, "asOf": "2026-10-17" }, "docsUrl": "https://docs.pipecat.ai", "llmsTxt": "https://docs.pipecat.ai/llms.txt", "capabilities": [ "voice.agent", "voice.pipeline", "voice.speech-to-speech", "voice.tools", "voice.telephony", "agent.mcp-client", "agent.multi-agent" ], "tags": [ "framework", "open-source", "self-hosted", "python", "free", "no-card", "bsd-2-clause", "llms-txt", "mcp-client", "pipeline", "speech-to-speech", "telephony", "webrtc", "no-telemetry" ], "lastRelease": "2026-10-28", "graded": true, "anchor": { "graded": true, "score": 65.2, "grade": "B", "agentReady": false, "rank": 428, "ranked": true, "rankOf": 1510, "categoryRank": 9, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 85, "payments": 60, "reliability": 68, "schema": 92, "security": 67, "transparency": 83 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": -9, "negativeNotes": [ "2025-11-10 to 2026-06-17. Three published advisories, fixed and between four and eleven months old, so 1 point each. Remote code execution through `pickle.loads()` in the optional, deprecated LivekitFrameSerializer (GHSA-c2jg-5cp7-6wc7, CVE-2025-62373, critical, fixed in 0.0.94 on 10 November 2025, advisory published 23 April 2026), arbitrary file read through the development runner's `/files` endpoint (GHSA-3363-2ph6-35wh, high, fixed in 1.2.0 on 14 May 2026) and unauthenticated call control through the runner's telephony `/ws` endpoint (GHSA-j8cv-x86q-rj85, high, fixed in 1.4.0 on 17 June 2026). The moderate GHSA-hqm2-cfx2-2vgh of 15 October 2026 covers behaviour documented as by design and isn't deducted. https://osv.dev/vulnerability/GHSA-c2jg-5cp7-6wc7, https://osv.dev/vulnerability/GHSA-3363-2ph6-35wh, https://osv.dev/vulnerability/GHSA-j8cv-x86q-rj85", "-3, 26 August to 28 October 2026. pipecat-ai keeps shipping breaking changes in minor releases with no advance notice, while its changelog states semantic versioning. The changelog flags 16 in 1.8.0 (26 August), 4 in 1.9.0, 4 in 1.10.0, 6 in 1.13.0 (18 October, among them `get_llm_invocation_params()` turning async and `BackendOutput` losing `is_final`), 1 in 1.14.0 and 5 in 1.15.0 (28 October, among them several stop strategies now all having to agree before a user turn ends). Repeated breaks in the framework's own package fold into one term. https://github.com/pipecat-ai/pipecat/blob/main/CHANGELOG.md", "-3, 16 to 23 October 2026. 1.13.0 (18 October) fixed OpenAI-compatible provider services sending `OPENAI_API_KEY` to other providers when given no `api_key` (merged on 16 October) and error messages carrying API keys, tokens and signed URLs, and 1.14.0 (23 October) closed a gap in that masking. All three are under Security in the changelog, and OSV lists no advisory for them on 1 November. A credential sent to another provider, fixed and described with no advisory, takes its own term apart from the breaking changes, as terraform-mcp's redirectable bearer token and stackone's unadvised fixes did. https://github.com/pipecat-ai/pipecat/blob/main/CHANGELOG.md" ], "verdict": "A BSD-2-Clause Python framework with dozens of speech, model and transport integrations, an MCP client that filters tools and pins arguments, and nine releases in 90 days. It has no tool-approval step or prompt-injection guidance, and minor releases keep removing and renaming APIs although the changelog states semver.", "bestFor": "Python teams that want to own a voice agent's pipeline, pick each speech and model provider, and host it themselves or on Pipecat Cloud.", "strengths": [ "BSD-2-Clause framework, with 23 speech-to-text, 25 LLM, 31 text-to-speech and 6 speech-to-speech services listed in the README", "Nine releases in the 90 days to 1 November 2026, with a dated Keep a Changelog file and pull-request links", "`MCPClient` takes a tool allowlist, per-tool output filters and fixed arguments hidden from the model", "No telemetry found in the source. OpenTelemetry tracing is off by default and needs an exporter the developer supplies", "Since 1.13.0, OpenAI-compatible provider services require an explicit key, and error messages mask credentials" ], "weaknesses": [ "No tool-approval or confirmation step, and no prompt-injection guidance, for tools that act on a caller's speech", "Up to 1.12.0, OpenAI-compatible provider services sent `OPENAI_API_KEY` to other providers. Fixed in 1.13.0 on 18 October 2026, with no advisory", "Three high or critical advisories fixed since November 2025, in an optional serialiser and the development runner", "Breaking changes ship in minor releases, 16 flagged in 1.8.0 and 5 in 1.15.0, although the changelog says it follows semver", "The optional ai-coustics filter registers a Pipecat identifier with that vendor's SDK, which the docs don't mention" ], "agentNotes": [ "Upgrade to 1.13.0 or later and pass `api_key` explicitly to every OpenAI-compatible service such as Groq, Cerebras or OpenRouter. Earlier versions send `OPENAI_API_KEY` to that provider when no key is given", "Pass `tools_filter` to `MCPClient` so only the tools the call needs reach the model, and use `tools_arguments` for values the model must not choose", "Gate tools that book, pay or send in your own handler. Pipecat has no approval step, and a caller's speech goes straight to the model", "Keep the development runner on localhost. Its `/start`, `/daily` and dial-in webhook endpoints take requests from anyone by design", "Pin a minor version and read the warning-flagged entries in CHANGELOG.md before upgrading. 1.15.0 changed how several user turn stop strategies combine" ], "metrics": { "kind": "library", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 65.2 } ], "editorialScores": { "ergonomics": 72, "maintenance": 85, "payments": 60, "reliability": 68, "schema": 92, "security": 67, "transparency": 85 }, "provenanceScore": 80, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install pipecat-ai # or: uv tool install \"pipecat-ai[cli]\" \u0026\u0026 pipecat init" }, "letme": { "capability": "https://letme.dev/voice.agent", "tool": "https://letme.dev/pipecat" }, "sameCompany": [ "pipecat-phonellm" ], "area": "voice", "unitPrices": [ { "item": "Pipecat Cloud agent-1x (0.5 vCPU, 1 GB)", "unit": "call-minute", "usd": 0.01, "note": "per active agent minute, reserved agents $0.0005 a minute" }, { "item": "Pipecat Cloud agent-2x (1 vCPU, 2 GB)", "unit": "call-minute", "usd": 0.02, "note": "per active agent minute, reserved agents $0.001 a minute" }, { "item": "Pipecat Cloud agent-3x (1.5 vCPU, 3 GB)", "unit": "call-minute", "usd": 0.03, "note": "per active agent minute, reserved agents $0.0015 a minute" }, { "item": "Daily WebRTC voice and video", "unit": "call-minute", "usd": 0.004, "note": "per participant minute, 1:1 voice sessions on Pipecat Cloud free" }, { "item": "Daily PSTN dial-in or dial-out", "unit": "call-minute", "usd": 0.018, "note": "SIP included, SIP alone $0.003 to $0.02 a minute" }, { "item": "SIP REFER call transfer", "unit": "tx", "usd": 0.2, "note": "per transfer event" }, { "item": "Audio recording", "unit": "audio-minute", "usd": 0.005, "note": "storage $0.003 a minute" } ], "provenance": { "legalEntity": "Daily", "domain": "pipecat.ai", "domainRegistered": "2024-05-01", "endpointOnVendorDomain": null, "terms": "https://www.daily.co/legal/terms-of-service/", "privacy": "https://www.daily.co/legal/privacy/", "statusPage": "https://status.pipecat.daily.co", "changelog": "https://github.com/pipecat-ai/pipecat/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-11-01", "notes": [ "LICENSE reads 'Copyright (c) 2024–2026, Daily'. The terms of service (last updated 31 March 2025) say Daily and name Pipecat Cloud and Daily's open-source frameworks among its services. The DPA (last updated 1 May 2025) names the company 'Daily, Co.' at 548 Market St., San Francisco.", "RDAP gives pipecat.ai a registration date of 1 May 2024. The docs are at docs.pipecat.ai and the code under GitHub's pipecat-ai organisation.", "security.txt returns 404 on www.pipecat.ai, docs.pipecat.ai and www.daily.co. SECURITY.md and the Pipecat Cloud security guide route reports to an email address at Daily, which the guide says is acknowledged within a week. Daily publishes a responsible disclosure policy with no bounty.", "The privacy policy is effective 6 January 2025. The sub-processor list is dated 1 September 2026.", "The status page covers Pipecat Cloud, not the framework.", "WebFetch refused docs.pipecat.ai and github.com, so docs.pipecat.ai, www.daily.co, status.pipecat.daily.co, developers.cloudflare.com, huggingface.co, pypi.org, api.osv.dev, pypistats.org, repos.ecosyste.ms, issues.ecosyste.ms, the npm registry, the MCP registry and rdap.org were read with curl after their robots.txt. GitHub's own pages answered 403 through the session's proxy." ], "score": 80 }, "requirements": { "setupChecked": true, "complianceChecked": true, "card": "unknown", "freeTier": true, "minutes": 20, "credential": "api-key", "hosting": [ "self-hosted" ], "euResidency": "unknown", "trainsOnData": "no", "zeroRetention": "unknown", "dpa": true, "selfHost": "yes" }, "pageJsonUrl": "https://www.anchorterminal.com/tools/pipecat.json", "live": { "slug": "pipecat", "vendorStatus": { "page": "https://status.pipecat.daily.co", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:23:16.830139271Z" }, "versions": [ { "registry": "github", "name": "pipecat-ai/pipecat", "version": "v1.15.0", "released": "2026-10-29", "seenAt": "2026-11-06T23:56:17.95033308Z" }, { "registry": "npm", "name": "@pipecat-ai/client-js", "version": "1.16.0", "seenAt": "2026-11-06T23:56:17.115559884Z" }, { "registry": "pypi", "name": "pipecat-ai", "version": "1.15.0", "released": "2026-10-29", "seenAt": "2026-11-06T23:56:16.870846918Z" } ], "githubStars": 17101, "npmWeekly": 129192, "pypiWeekly": 374140, "securityTxt": { "url": "https://pipecat.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:50.311611328Z" }, "llmsTxt": { "url": "https://docs.pipecat.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:38.227872926Z" }, "domain": { "domain": "pipecat.ai", "registered": "2024-05-01", "source": "https://rdap.identitydigital.services/rdap/domain/pipecat.ai", "checkedAt": "2026-11-01T14:20:09.941363148Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/pipecat-ai/pipecat/main/CHANGELOG.md", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-07T14:22:55.571520023Z", "changedAt": "2026-10-30T05:50:02.946504107Z", "fingerprint": "13e9874e9ea5" }, { "url": "https://www.daily.co/pricing/pipecat-cloud/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:27:45.084757238Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "06f32f71f3dd" } ], "github": { "repo": "pipecat-ai/pipecat", "checkedAt": "2026-11-02T09:16:35.354291053Z", "stars": 16992, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-02T03:32:17Z", "openIssues": 142, "openPRs": 371, "issuesOpened90d": 199, "issuesClosed90d": 141, "prsMerged90d": 676, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-10-30T18:11:51Z" }, "advisories": [ { "ghsa": "GHSA-hqm2-cfx2-2vgh", "cve": "CVE-2026-102682", "severity": "medium", "published": "2026-09-29T17:39:30Z" }, { "ghsa": "GHSA-j8cv-x86q-rj85", "cve": "CVE-2026-54695", "severity": "high", "published": "2026-06-17T14:39:37Z" }, { "ghsa": "GHSA-3363-2ph6-35wh", "cve": "CVE-2026-44716", "severity": "high", "published": "2026-05-15T02:17:30Z" }, { "ghsa": "GHSA-c2jg-5cp7-6wc7", "cve": "CVE-2025-62373", "severity": "critical", "published": "2026-04-23T12:55:15Z" } ], "replies": { "sampled": 25, "unanswered": 20, "medianDays": 0 } }, "updatedAt": "2026-11-07T19:23:16.830139271Z" } }, "edges": [ { "by": 32, "category": "schema", "leads": "pipecat", "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": "Framework reading. Typed Python (py.typed) with an API reference page per service, transport, frame type and utility (25). llms.txt, Markdown copies of each page and llms-full.txt (4.7 MB on 1 November) (10). Guides say when to reach for Flows, multiple LLM agents or a single pipeline, and the error-handling page says which failures are worth retrying. The OpenTelemetry reference now gives `PipelineWorker` defaults of `enable_tracing` False and `enable_turn_tracking` True, matching the 1.15.0 source, so the mismatch the 17 October check found is gone (16 of 20, was 14). Pydantic `Settings` classes per service, a provider-neutral `FunctionSchema`, and an `ErrorCategory` enum (12 of 15). Example folders from function calling and MCP to telephony, and documented error categories and Pipecat Cloud error codes (14 of 15). Dated changelog with pull-request links, towncrier fragments and a migration guide to 1.0 (15). 25 + 10 + 16 + 12 + 14 + 15 = 92." }, "scores": { "a": 60, "b": 92 } }, { "by": 20, "category": "payments", "leads": "pipecat", "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). Read with the self-hosted rule, with the pricing line scored on Pipecat Cloud, the paid option. Its per-minute prices by agent size, transport, telephony and recording are published without a login, re-read on 1 November ($0.01 an active minute for agent-1x, $0.018 a minute for Daily PSTN) (20). The BSD-2-Clause package installs with no card. Pipecat Cloud needs billing credentials or a trial code before sessions start (20, on the package). The framework runs with no account, on the developer's own provider keys (20). 0 + 20 + 20 + 20 = 60." }, "scores": { "a": 40, "b": 60 } }, { "by": 20, "category": "transparency", "leads": "pipecat", "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": "BSD-2-Clause (30). The framework keeps no data. Daily's privacy policy (6 January 2025) keeps personal data while an account is open, the Pipecat Cloud security guide says session data is removed when a session ends, logs are stored by default and administrative API calls are kept a year, and Daily publishes a DPA (1 May 2025) and a sub-processor list (1 September 2026), per the 17 October check. Control-plane data is in the US whatever the agent's region (24 of 30). The changelog has Deprecated sections in most releases, and recent entries name removal in 2.0.0, with a migration guide to 1.0, but no dated removal windows (13 of 20). No telemetry found, and tracing is opt-in, which the OpenTelemetry reference now states too. The optional ai-coustics filter still registers a Pipecat identifier with that vendor's SDK in 1.15.0, which the docs don't mention (18 of 20, was 16). 30 + 24 + 13 + 18 = 85." }, "scores": { "a": 63, "b": 83 } }, { "by": 14, "category": "maintenance", "leads": "pipecat", "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": "pipecat-ai 1.15.0, dated 28 October 2026 in the changelog and tagged that day, 4 days before the check (30). Nine releases in the 90 days to 1 November, 1.8.0 on 26 August to 1.15.0 (20). Issue and pull-request reply times couldn't be read, since GitHub's pages answer 403, and the 17 October figures came from a third-party copy of GitHub data, now struck. The clone shows 151 pull requests from outside forks merged in the 90 days to 1 November, fixes that cite the issues they close, and a needs-repro workflow that labels issues (13 of 25, was 15). The Python framework and the JavaScript client (`@pipecat-ai/client-js` 1.16.0, tagged 28 October) are current, with client SDKs in six languages (15). CI, coverage, a licence check, a uv lockfile and trusted publishing to PyPI are configured. Dependabot was added on 23 October, for the pinned GitHub Actions only, and a passing main wasn't confirmed (7 of 10). 30 + 20 + 13 + 15 + 7 = 85." }, "scores": { "a": 71, "b": 85 } }, { "by": 9, "category": "security", "leads": "pipecat", "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": "Framework reading, as for the frameworks category. We found no telemetry in the source, and tracing is off by default and needs an exporter the developer supplies. The two credential flaws the 17 October check found on 1.12.0 are fixed in released versions. 1.13.0 (18 October) makes the services for OpenAI-compatible providers raise an error when given no key instead of falling back to `OPENAI_API_KEY`, and masks API keys, tokens and signed URLs in error messages, and 1.14.0 (23 October) closes a gap in that masking (30 of 30, was 20). No tool-approval or confirmation primitive. `tools_filter` allowlists MCP tools and `tools_arguments` pins values the model cannot change (8 of 20). A caller's speech and MCP tool results go to the model, and we found no prompt-injection guidance in the docs, re-searched in llms-full.txt on 1 November (3 of 15). OpenTelemetry spans per service and tool call, with `FunctionCallObserver` and `LLMLogObserver` for per-call visibility (15). SECURITY.md routes reports to an email address at Daily, and GitHub advisories are published with CVEs and fixed versions, four since April 2026 (OSV, re-read on 1 November, lists no new one). The `OPENAI_API_KEY` fix shipped without an advisory. No security.txt or bug bounty. Daily states SOC 2 Type 2, which isn't scored for a framework (11 of 20). 30 + 8 + 3 + 15 + 11 = 67." }, "scores": { "a": 58, "b": 67 } }, { "by": 6, "category": "reliability", "leads": "pipecat", "name": "Reliability", "reasons": { "a": "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.", "b": "Local-software reading of the framework. pipecat-ai installs from PyPI with Python 3.11 or later declared (1.15.0's pyproject), and a compatibility workflow builds it on 3.11 to 3.14 (20). A public tests workflow runs pytest (406 Python files under tests/ in 1.15.0), on pushes to main and on pull requests, with coverage and licence-check jobs, but GitHub's Actions pages weren't readable on 17 October or 1 November, so a green main is not confirmed (15 of 25). The issue tracker couldn't be read, since GitHub's pages answer 403. The 17 October reading of open issues came from a third-party copy of GitHub data, which we no longer use, so it is struck. The clone shows 3,539 commits in the 90 days to 1 November, fixes that cite the issues they close (#6162 on 15 October, #6256 on 20 October, #6410 from an outside contributor on 28 October) and 151 merged pull requests from outside forks, so 8 of 25 on that evidence alone (was 12). Keep a Changelog with dates, semver stated and breaking changes flagged with a warning sign, but minor releases keep carrying them, 16 flagged in 1.8.0, 4 in 1.9.0, 4 in 1.10.0, 6 in 1.13.0, 1 in 1.14.0 and 5 in 1.15.0 (10 of 15). 1.15.0, classed Production/Stable (15). 20 + 15 + 8 + 10 + 15 = 68." }, "scores": { "a": 62, "b": 68 } } ], "facts": [ { "a": "HTTP API", "b": "Agent framework", "name": "Kind" }, { "a": "Inworld AI", "b": "Daily", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "websocket, HTTP", "b": "", "name": "Transports" }, { "a": "API key", "b": "None", "name": "Auth" }, { "a": "Pay per use", "b": "Free", "name": "Pricing" }, { "a": "$25 per 1M characters", "b": "$0.01 per minute of call", "name": "Price for voice agents" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "BSD-2-Clause for the framework. Pipecat Cloud is a hosted service under Daily's terms of service", "name": "Licence" }, { "a": "0", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-16", "b": "2026-10-28", "name": "Last release" }, { "a": "2025-06-11", "b": "2025-03-31", "name": "Terms last updated" }, { "a": "2026-01-18", "b": "2025-01-06", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "16k stars, 98k npm/wk, 302k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Pipecat scores 65.2 (B) on agent readiness against Inworld Realtime API's 60.1 (C), and leads in every scored category.", "question": "Which is better for AI agents, Inworld Realtime API or Pipecat?" }, { "answer": "No hosted endpoint is listed for Inworld Realtime API. No hosted endpoint is listed for Pipecat.", "question": "Can an agent call Inworld Realtime API and Pipecat without installing anything?" }, { "answer": "No open-source release is listed for Inworld Realtime API. Pipecat is open source (BSD-2-Clause for the framework. Pipecat Cloud is a hosted service under Daily's terms of service).", "question": "Are Inworld Realtime API and Pipecat open source?" } ], "goodFor": [ { "aheadOn": null, "also": [ "No incidents deducted, where Pipecat loses 9 points for them" ], "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": [ "Reliability, 68 against 62", "Schema \u0026 documentation, 92 against 60", "Security \u0026 auth, 67 against 58", "Payments \u0026 pricing, 60 against 40", "Maintenance \u0026 community, 85 against 71", "Transparency \u0026 trust, 83 against 63" ], "also": [ "No key needed to call it", "Free to start without a card", "Open source" ], "goodFor": "Python teams that want to own a voice agent's pipeline, pick each speech and model provider, and host it themselves or on Pipecat Cloud.", "slug": "pipecat", "watchFor": "No tool-approval or confirmation step, and no prompt-injection guidance, for tools that act on a caller's speech" } ], "history": { "inworld-realtime": null, "pipecat": [ { "causes": [ "security", "product", "correction", "event" ], "date": "2026-11-01", "delta": -3.8, "from": 69, "fromGrade": "B", "to": 65.2, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-30", "delta": -0.1, "from": 69.1, "fromGrade": "B", "to": 69, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 68.9, "fromGrade": "B", "to": 69.1, "toGrade": "B" } ] }, "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-pipecat.json", "title": "Amazon Nova 2 Sonic vs Pipecat", "url": "https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-pipecat" }, { "json": "https://www.anchorterminal.com/compare/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-pipecat.json", "title": "AssemblyAI Voice Agent API vs Pipecat", "url": "https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-pipecat" }, { "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-pipecat.json", "title": "Bland AI API + MCP vs Pipecat", "url": "https://www.anchorterminal.com/compare/bland-ai-vs-pipecat" }, { "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-pipecat.json", "title": "Bolna API + MCP vs Pipecat", "url": "https://www.anchorterminal.com/compare/bolna-vs-pipecat" }, { "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-pipecat.json", "title": "Deepgram Voice Agent API vs Pipecat", "url": "https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-pipecat" }, { "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-pipecat.json", "title": "ElevenLabs Agents API + MCP vs Pipecat", "url": "https://www.anchorterminal.com/compare/elevenlabs-agents-vs-pipecat" }, { "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-pipecat.json", "title": "fone.me vs Pipecat", "url": "https://www.anchorterminal.com/compare/fone-me-vs-pipecat" }, { "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-pipecat.json", "title": "Gemini Live API vs Pipecat", "url": "https://www.anchorterminal.com/compare/gemini-live-vs-pipecat" }, { "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/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-pipecat.json", "title": "Harmony.ai vs Pipecat", "url": "https://www.anchorterminal.com/compare/harmony-ai-vs-pipecat" }, { "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-pipecat.json", "title": "Hume EVI (Empathic Voice Interface) vs Pipecat", "url": "https://www.anchorterminal.com/compare/hume-evi-vs-pipecat" }, { "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-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/inworld-realtime-vs-vogent.json", "title": "Inworld Realtime API vs Vogent API", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent" }, { "json": "https://www.anchorterminal.com/compare/livekit-agents-vs-pipecat.json", "title": "LiveKit Agents vs Pipecat", "url": "https://www.anchorterminal.com/compare/livekit-agents-vs-pipecat" }, { "json": "https://www.anchorterminal.com/compare/openai-realtime-vs-pipecat.json", "title": "OpenAI Realtime API vs Pipecat", "url": "https://www.anchorterminal.com/compare/openai-realtime-vs-pipecat" }, { "json": "https://www.anchorterminal.com/compare/pipecat-vs-placecall.json", "title": "Pipecat vs PlaceCall", "url": "https://www.anchorterminal.com/compare/pipecat-vs-placecall" }, { "json": "https://www.anchorterminal.com/compare/pipecat-vs-retell-ai.json", "title": "Pipecat vs Retell AI API + MCP", "url": "https://www.anchorterminal.com/compare/pipecat-vs-retell-ai" }, { "json": "https://www.anchorterminal.com/compare/pipecat-vs-rime-prism.json", "title": "Pipecat vs Rime Prism", "url": "https://www.anchorterminal.com/compare/pipecat-vs-rime-prism" }, { "json": "https://www.anchorterminal.com/compare/pipecat-vs-synthflow.json", "title": "Pipecat vs Synthflow API + MCP", "url": "https://www.anchorterminal.com/compare/pipecat-vs-synthflow" }, { "json": "https://www.anchorterminal.com/compare/pipecat-vs-ultravox.json", "title": "Pipecat vs Ultravox Realtime API", "url": "https://www.anchorterminal.com/compare/pipecat-vs-ultravox" }, { "json": "https://www.anchorterminal.com/compare/pipecat-vs-vaani-voice.json", "title": "Pipecat vs Vaani Developer Platform", "url": "https://www.anchorterminal.com/compare/pipecat-vs-vaani-voice" }, { "json": "https://www.anchorterminal.com/compare/pipecat-vs-vapi.json", "title": "Pipecat vs Vapi API + MCP", "url": "https://www.anchorterminal.com/compare/pipecat-vs-vapi" }, { "json": "https://www.anchorterminal.com/compare/pipecat-vs-vocily.json", "title": "Pipecat vs Vocily AI", "url": "https://www.anchorterminal.com/compare/pipecat-vs-vocily" }, { "json": "https://www.anchorterminal.com/compare/pipecat-vs-vogent.json", "title": "Pipecat vs Vogent API", "url": "https://www.anchorterminal.com/compare/pipecat-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-pipecat.json", "title": "CueLight vs Pipecat", "url": "https://www.anchorterminal.com/compare/cuelight-vs-pipecat" }, { "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-vs-pipecat-phonellm.json", "title": "Pipecat vs Pipecat PhoneLLM", "url": "https://www.anchorterminal.com/compare/pipecat-vs-pipecat-phonellm" }, { "json": "https://www.anchorterminal.com/compare/gpt-live-vs-pipecat.json", "title": "GPT-Live vs Pipecat", "url": "https://www.anchorterminal.com/compare/gpt-live-vs-pipecat" } ], "panel": null, "scores": [ { "by": 6, "edge": "pipecat", "inworld-realtime": 62, "key": "reliability", "name": "Reliability", "pipecat": 68, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 32, "edge": "pipecat", "inworld-realtime": 60, "key": "schema", "name": "Schema \u0026 documentation", "pipecat": 92, "weight": 13 }, { "by": 4, "edge": "pipecat", "inworld-realtime": 68, "key": "ergonomics", "name": "Agent ergonomics", "pipecat": 72, "weight": 13 }, { "by": 9, "edge": "pipecat", "inworld-realtime": 58, "key": "security", "name": "Security \u0026 auth", "pipecat": 67, "weight": 14 }, { "by": 20, "edge": "pipecat", "inworld-realtime": 40, "key": "payments", "name": "Payments \u0026 pricing", "pipecat": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 14, "edge": "pipecat", "inworld-realtime": 71, "key": "maintenance", "name": "Maintenance \u0026 community", "pipecat": 85, "weight": 7 }, { "by": 20, "edge": "pipecat", "inworld-realtime": 63, "key": "transparency", "name": "Transparency \u0026 trust", "pipecat": 83, "weight": 7 } ], "summary": "Pipecat scores 65.2 (B) on agent readiness against Inworld Realtime API's 60.1 (C), and leads in every scored category. 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.", "pipecat": "A BSD-2-Clause Python framework with dozens of speech, model and transport integrations, an MCP client that filters tools and pins arguments, and nine releases in 90 days. It has no tool-approval step or prompt-injection guidance, and minor releases keep removing and renaming APIs although the changelog states semver." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat", "json": "https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat.min.md" }, "markdown": "Pipecat scores 65.2 (B) on agent readiness against Inworld Realtime API's 60.1 (C), and leads in every scored category. 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- Pipecat: grade B, 65.2/100, rank #428 of 1510. Markdown https://www.anchorterminal.com/tools/pipecat.md · JSON https://www.anchorterminal.com/api/v1/tools/pipecat.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\nAlso in its favour:\n- No incidents deducted, where Pipecat loses 9 points for them\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### Pipecat (B)\n\nGood for: Python teams that want to own a voice agent's pipeline, pick each speech and model provider, and host it themselves or on Pipecat Cloud.\n\nAhead on:\n- Reliability, 68 against 62\n- Schema \u0026 documentation, 92 against 60\n- Security \u0026 auth, 67 against 58\n- Payments \u0026 pricing, 60 against 40\n- Maintenance \u0026 community, 85 against 71\n- Transparency \u0026 trust, 83 against 63\n\nAlso in its favour:\n- No key needed to call it\n- Free to start without a card\n- Open source\n\nWatch for: No tool-approval or confirmation step, and no prompt-injection guidance, for tools that act on a caller's speech\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Pipecat +32\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- Pipecat (92): Framework reading. Typed Python (py.typed) with an API reference page per service, transport, frame type and utility (25). llms.txt, Markdown copies of each page and llms-full.txt (4.7 MB on 1 November) (10). Guides say when to reach for Flows, multiple LLM agents or a single pipeline, and the error-handling page says which failures are worth retrying. The OpenTelemetry reference now gives `PipelineWorker` defaults of `enable_tracing` False and `enable_turn_tracking` True, matching the 1.15.0 source, so the mismatch the 17 October check found is gone (16 of 20, was 14). Pydantic `Settings` classes per service, a provider-neutral `FunctionSchema`, and an `ErrorCategory` enum (12 of 15). Example folders from function calling and MCP to telephony, and documented error categories and Pipecat Cloud error codes (14 of 15). Dated changelog with pull-request links, towncrier fragments and a migration guide to 1.0 (15). 25 + 10 + 16 + 12 + 14 + 15 = 92.\n\n### Payments \u0026 pricing: Pipecat +20\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- Pipecat (60): No x402, MPP or L402 (0). Read with the self-hosted rule, with the pricing line scored on Pipecat Cloud, the paid option. Its per-minute prices by agent size, transport, telephony and recording are published without a login, re-read on 1 November ($0.01 an active minute for agent-1x, $0.018 a minute for Daily PSTN) (20). The BSD-2-Clause package installs with no card. Pipecat Cloud needs billing credentials or a trial code before sessions start (20, on the package). The framework runs with no account, on the developer's own provider keys (20). 0 + 20 + 20 + 20 = 60.\n\n### Transparency \u0026 trust: Pipecat +20\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- Pipecat (83): BSD-2-Clause (30). The framework keeps no data. Daily's privacy policy (6 January 2025) keeps personal data while an account is open, the Pipecat Cloud security guide says session data is removed when a session ends, logs are stored by default and administrative API calls are kept a year, and Daily publishes a DPA (1 May 2025) and a sub-processor list (1 September 2026), per the 17 October check. Control-plane data is in the US whatever the agent's region (24 of 30). The changelog has Deprecated sections in most releases, and recent entries name removal in 2.0.0, with a migration guide to 1.0, but no dated removal windows (13 of 20). No telemetry found, and tracing is opt-in, which the OpenTelemetry reference now states too. The optional ai-coustics filter still registers a Pipecat identifier with that vendor's SDK in 1.15.0, which the docs don't mention (18 of 20, was 16). 30 + 24 + 13 + 18 = 85.\n\n### Maintenance \u0026 community: Pipecat +14\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- Pipecat (85): pipecat-ai 1.15.0, dated 28 October 2026 in the changelog and tagged that day, 4 days before the check (30). Nine releases in the 90 days to 1 November, 1.8.0 on 26 August to 1.15.0 (20). Issue and pull-request reply times couldn't be read, since GitHub's pages answer 403, and the 17 October figures came from a third-party copy of GitHub data, now struck. The clone shows 151 pull requests from outside forks merged in the 90 days to 1 November, fixes that cite the issues they close, and a needs-repro workflow that labels issues (13 of 25, was 15). The Python framework and the JavaScript client (`@pipecat-ai/client-js` 1.16.0, tagged 28 October) are current, with client SDKs in six languages (15). CI, coverage, a licence check, a uv lockfile and trusted publishing to PyPI are configured. Dependabot was added on 23 October, for the pinned GitHub Actions only, and a passing main wasn't confirmed (7 of 10). 30 + 20 + 13 + 15 + 7 = 85.\n\n### Security \u0026 auth: Pipecat +9\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- Pipecat (67): Framework reading, as for the frameworks category. We found no telemetry in the source, and tracing is off by default and needs an exporter the developer supplies. The two credential flaws the 17 October check found on 1.12.0 are fixed in released versions. 1.13.0 (18 October) makes the services for OpenAI-compatible providers raise an error when given no key instead of falling back to `OPENAI_API_KEY`, and masks API keys, tokens and signed URLs in error messages, and 1.14.0 (23 October) closes a gap in that masking (30 of 30, was 20). No tool-approval or confirmation primitive. `tools_filter` allowlists MCP tools and `tools_arguments` pins values the model cannot change (8 of 20). A caller's speech and MCP tool results go to the model, and we found no prompt-injection guidance in the docs, re-searched in llms-full.txt on 1 November (3 of 15). OpenTelemetry spans per service and tool call, with `FunctionCallObserver` and `LLMLogObserver` for per-call visibility (15). SECURITY.md routes reports to an email address at Daily, and GitHub advisories are published with CVEs and fixed versions, four since April 2026 (OSV, re-read on 1 November, lists no new one). The `OPENAI_API_KEY` fix shipped without an advisory. No security.txt or bug bounty. Daily states SOC 2 Type 2, which isn't scored for a framework (11 of 20). 30 + 8 + 3 + 15 + 11 = 67.\n\n### Reliability: Pipecat +6\n\n- Inworld Realtime API (62): 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.\n- Pipecat (68): Local-software reading of the framework. pipecat-ai installs from PyPI with Python 3.11 or later declared (1.15.0's pyproject), and a compatibility workflow builds it on 3.11 to 3.14 (20). A public tests workflow runs pytest (406 Python files under tests/ in 1.15.0), on pushes to main and on pull requests, with coverage and licence-check jobs, but GitHub's Actions pages weren't readable on 17 October or 1 November, so a green main is not confirmed (15 of 25). The issue tracker couldn't be read, since GitHub's pages answer 403. The 17 October reading of open issues came from a third-party copy of GitHub data, which we no longer use, so it is struck. The clone shows 3,539 commits in the 90 days to 1 November, fixes that cite the issues they close (#6162 on 15 October, #6256 on 20 October, #6410 from an outside contributor on 28 October) and 151 merged pull requests from outside forks, so 8 of 25 on that evidence alone (was 12). Keep a Changelog with dates, semver stated and breaking changes flagged with a warning sign, but minor releases keep carrying them, 16 flagged in 1.8.0, 4 in 1.9.0, 4 in 1.10.0, 6 in 1.13.0, 1 in 1.14.0 and 5 in 1.15.0 (10 of 15). 1.15.0, classed Production/Stable (15). 20 + 15 + 8 + 10 + 15 = 68.\n\n## Score by category\n\n| Category | Weight | Inworld Realtime API | Pipecat | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 62 | 68 | Pipecat +6 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 60 | 92 | Pipecat +32 |\n| Agent ergonomics | 13% (16.2 this run) | 68 | 72 | Pipecat +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 58 | 67 | Pipecat +9 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 60 | Pipecat +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 71 | 85 | Pipecat +14 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 83 | Pipecat +20 |\n| Negative events | ≤15 | 0 | -9 | |\n| **Total** | | **60.1 · C** | **65.2 · B** | |\n\n## Facts side by side\n\n| Fact | Inworld Realtime API | Pipecat |\n| --- | --- | --- |\n| Kind | HTTP API | Agent framework |\n| Vendor | Inworld AI | Daily |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | websocket, HTTP | |\n| Auth | API key | None |\n| Pricing | Pay per use | Free |\n| Price for voice agents | $25 per 1M characters | $0.01 per minute of call |\n| x402 | no | no |\n| Licence | none | BSD-2-Clause for the framework. Pipecat Cloud is a hosted service under Daily's terms of service |\n| Tools exposed | 0 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-16 | 2026-10-28 |\n| Terms last updated | 2025-06-11 | 2025-03-31 |\n| Privacy policy last updated | 2026-01-18 | 2025-01-06 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | none | 16k stars, 98k npm/wk, 302k PyPI/wk |\n| Agent reviews | none | 3/5 (4) |\n\n## How the scores have moved\n\n### Inworld Realtime API\n\nNo score change since it was listed.\n\n### Pipecat\n\n- -3.8 on 1 November 2026: security, product, correction, negative event\n- -0.1 on 30 October 2026: checklist\n- +0.2 on 27 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**Pipecat.** A BSD-2-Clause Python framework with dozens of speech, model and transport integrations, an MCP client that filters tools and pins arguments, and nine releases in 90 days. It has no tool-approval step or prompt-injection guidance, and minor releases keep removing and renaming APIs although the changelog states semver.\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### Pipecat\n\n1. Upgrade to 1.13.0 or later and pass `api_key` explicitly to every OpenAI-compatible service such as Groq, Cerebras or OpenRouter. Earlier versions send `OPENAI_API_KEY` to that provider when no key is given\n2. Pass `tools_filter` to `MCPClient` so only the tools the call needs reach the model, and use `tools_arguments` for values the model must not choose\n3. Gate tools that book, pay or send in your own handler. Pipecat has no approval step, and a caller's speech goes straight to the model\n4. Keep the development runner on localhost. Its `/start`, `/daily` and dial-in webhook endpoints take requests from anyone by design\n5. Pin a minor version and read the warning-flagged entries in CHANGELOG.md before upgrading. 1.15.0 changed how several user turn stop strategies combine\n\n## Questions\n\n### Which is better for AI agents, Inworld Realtime API or Pipecat?\n\nPipecat scores 65.2 (B) on agent readiness against Inworld Realtime API's 60.1 (C), and leads in every scored category.\n\n### Can an agent call Inworld Realtime API and Pipecat without installing anything?\n\nNo hosted endpoint is listed for Inworld Realtime API. No hosted endpoint is listed for Pipecat.\n\n### Are Inworld Realtime API and Pipecat open source?\n\nNo open-source release is listed for Inworld Realtime API. Pipecat is open source (BSD-2-Clause for the framework. Pipecat Cloud is a hosted service under Daily's terms of service).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat.json, and with the fewest tokens: https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"inworld-realtime\", \"b\": \"pipecat\"}`. From a terminal: `anchor compare inworld-realtime pipecat`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/inworld-realtime.json and https://www.anchorterminal.com/api/v1/tools/pipecat.json\n\n## Other comparisons with Inworld Realtime API or Pipecat\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 Pipecat](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-pipecat.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 Pipecat](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-pipecat.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 Pipecat](https://www.anchorterminal.com/compare/bland-ai-vs-pipecat.md)\n- [Bolna API + MCP vs Inworld Realtime API](https://www.anchorterminal.com/compare/bolna-vs-inworld-realtime.md)\n- [Bolna API + MCP vs Pipecat](https://www.anchorterminal.com/compare/bolna-vs-pipecat.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 Pipecat](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-pipecat.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 Pipecat](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-pipecat.md)\n- [fone.me vs Inworld Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-inworld-realtime.md)\n- [fone.me vs Pipecat](https://www.anchorterminal.com/compare/fone-me-vs-pipecat.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 Pipecat](https://www.anchorterminal.com/compare/gemini-live-vs-pipecat.md)\n- [GPT-Live vs Inworld Realtime API](https://www.anchorterminal.com/compare/gpt-live-vs-inworld-realtime.md)\n- [Harmony.ai vs Inworld Realtime API](https://www.anchorterminal.com/compare/harmony-ai-vs-inworld-realtime.md)\n- [Harmony.ai vs Pipecat](https://www.anchorterminal.com/compare/harmony-ai-vs-pipecat.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 Pipecat](https://www.anchorterminal.com/compare/hume-evi-vs-pipecat.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 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- [Inworld Realtime API vs Vogent API](https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent.md)\n- [LiveKit Agents vs Pipecat](https://www.anchorterminal.com/compare/livekit-agents-vs-pipecat.md)\n- [OpenAI Realtime API vs Pipecat](https://www.anchorterminal.com/compare/openai-realtime-vs-pipecat.md)\n- [Pipecat vs PlaceCall](https://www.anchorterminal.com/compare/pipecat-vs-placecall.md)\n- [Pipecat vs Retell AI API + MCP](https://www.anchorterminal.com/compare/pipecat-vs-retell-ai.md)\n- [Pipecat vs Rime Prism](https://www.anchorterminal.com/compare/pipecat-vs-rime-prism.md)\n- [Pipecat vs Synthflow API + MCP](https://www.anchorterminal.com/compare/pipecat-vs-synthflow.md)\n- [Pipecat vs Ultravox Realtime API](https://www.anchorterminal.com/compare/pipecat-vs-ultravox.md)\n- [Pipecat vs Vaani Developer Platform](https://www.anchorterminal.com/compare/pipecat-vs-vaani-voice.md)\n- [Pipecat vs Vapi API + MCP](https://www.anchorterminal.com/compare/pipecat-vs-vapi.md)\n- [Pipecat vs Vocily AI](https://www.anchorterminal.com/compare/pipecat-vs-vocily.md)\n- [Pipecat vs Vogent API](https://www.anchorterminal.com/compare/pipecat-vs-vogent.md)\n- [CueLight vs Inworld Realtime API](https://www.anchorterminal.com/compare/cuelight-vs-inworld-realtime.md)\n- [CueLight vs Pipecat](https://www.anchorterminal.com/compare/cuelight-vs-pipecat.md)\n- [Inworld Realtime API vs Pipecat PhoneLLM](https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat-phonellm.md)\n- [Pipecat vs Pipecat PhoneLLM](https://www.anchorterminal.com/compare/pipecat-vs-pipecat-phonellm.md)\n- [GPT-Live vs Pipecat](https://www.anchorterminal.com/compare/gpt-live-vs-pipecat.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 Pipecat", "url": "" } ], "description": "Pipecat scores 65.2 (B) to Inworld Realtime's 60.1 (C) for voice agents. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Inworld Realtime API C 60.1", "Pipecat B 65.2", "scores" ], "h1": "Inworld Realtime API vs Pipecat", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/inworld-realtime-vs-pipecat", "published": "2026-10-01", "section": "tools", "title": "Inworld Realtime vs Pipecat for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat" }, "tokens": { "markdown": 5800, "slim": 3130 }, "version": 1 }