# GPT-Live vs Inworld Realtime API

> GPT-Live scores 70.6 (BB) to Inworld Realtime's 60.1 (C) for voice agents. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/gpt-live-vs-inworld-realtime
- Markdown: https://www.anchorterminal.com/compare/gpt-live-vs-inworld-realtime.md (~6,200 tokens)
- 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 <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. 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

GPT-Live scores 70.6 (BB) on agent readiness against Inworld Realtime API's 60.1 (C), and leads in 5 of 7 scored categories. Inworld Realtime API leads on payments & pricing. Both do voice agents.

- GPT-Live: grade BB, 70.6/100, rank #192 of 1510. Markdown https://www.anchorterminal.com/tools/gpt-live.md · JSON https://www.anchorterminal.com/api/v1/tools/gpt-live.json
- 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
- 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

## Which one, for what

### GPT-Live (BB)

Good for: Teams who want a voice front end that keeps talking while a separate backend reasons and runs tools, with WebRTC, WebSocket and SIP from one vendor and a flat per-minute voice price.

Ahead on:
- Schema & documentation, 87 against 60
- Agent ergonomics, 76 against 68
- Security & auth, 81 against 58
- Maintenance & community, 82 against 71
- Transparency & trust, 90 against 63

Also in its favour:
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install

Watch for: The Live component on status.openai.com has data only from 16 October 2026, so the five weeks after general availability have no readable history.

### Inworld Realtime API (C)

Good for: Teams moving off OpenAI's Realtime API who want a choice of LLM and Inworld voices.

Ahead on:
- Payments & pricing, 40 against 20

Watch for: No per-minute price. A session's cost depends on STT, LLM tokens and TTS characters, and interrupted segments are still billed


## Why the edge

### Schema & documentation: GPT-Live +27

- GPT-Live (87): The OpenAPI 3.1 file in `openai/openai-openapi` (re-read from a clone at its 31 October commit) has seven `/live/sessions` paths and 190 component schemas whose names start with Live by our count, up from the 17 October file with the 24 October revision of Decisions inputs and the 28 October DTMF command, and typed client and server events on the primary and sideband connections. It is not an AsyncAPI document, so the WebSocket channels are described only as event schemas (22 of 25). llms.txt and a Markdown twin of every page (10). The delegation guide has a table of when to choose Responses or client delegation, the connection guides say when to use WebRTC, WebSocket or SIP, and the Decisions guide says when to delegate or react to transcripts (17 of 20). Fields carry enums and limits, such as `delegation.type`, SIP reject codes 300 to 699 and 500-token appends, but `model` also accepts any string and the Live MCP tool schema types only `type` (12 of 15). Python and JavaScript examples on every guide, an `error` event with a documented shape and several named codes, and a table of close reasons. No full catalogue of Live error codes was found, and three JavaScript examples in the Markdown twins are empty (12 of 15). A dated changelog tags entries with `v1/live/sessions`, there is one snapshot, and the deprecated webhook event is named (14 of 15).
- 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.

### Transparency & trust: GPT-Live +27

- GPT-Live (90): Closed service. The Python SDK is Apache-2.0, and the OpenAPI file and the Live Console sample are MIT. The services agreement is scored as the OpenAI API listing scores it, per that listing's check, since openai.com answered our reader with 403 (15 of 30, was 10, the reading every other OpenAI listing carries). The data controls page, re-read on 1 November, says `/v1/live/sessions` data is not used for training, abuse logs are kept up to 30 days, recordings are stored for 30 days only when `store` is true and storage is enabled, and Zero Data Retention treats `store` as false. It also says there is no public endpoint to delete a stored session. Those are stated conditions, not statements that disagree. The DPA, effective 1 January 2026, commits to return or deletion of customer data on termination, 30 days to object to a new subprocessor, and SCCs with the UK Addendum, and nothing in it conflicts with the guide, per the OpenAI API listing's 4 October check, not re-read on 1 November (openai.com answered 403). The same reading as the other OpenAI listings (30 of 30, was 18). The deprecations page states at least six months' notice for generally available models and lists dated shutdowns (20 of 20). The data-controls guide lists `/v1/live/sessions` for storage and processing in the United States and Europe only, narrower than most OpenAI endpoints, and the subprocessor list, updated 9 July 2026, names third-party subprocessors and OpenAI affiliates with processing countries and a notice form, per the OpenAI API listing's 4 October check. Locations and subprocessors are disclosed, which is what the line scores (20 of 20, was 10). 15 + 30 + 20 + 20 = 85.
- 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.

### Security & auth: GPT-Live +23

- GPT-Live (81): The project API key is sent as a Bearer header from a server, and WebSocket connections take no query parameters. GPT-Live has no browser client secret, so the key never reaches a browser and the server creates each session. Project keys carry their own permissions, service-account keys come through the Administration API, and the docs index lists workload identity federation, mutual TLS and IP allowlists. The access-control guide, re-read on 1 November, has no permission of its own for `/v1/live/sessions`, so a restricted key can't be confirmed to reach Live alone, the reading the OpenAI Decisions API and speech-to-text listings got (27 of 30, was 24). The WebRTC data channel can be limited to listed client and server events for an untrusted frontend, though the default allows all. The application runs custom functions and answers MCP approval requests (15 of 20). The guardrails guide describes checking input transcripts for jailbreak attempts and blocking actions until checks pass, the SIP guide says to treat SIP headers as untrusted, and the session guide says to keep trusted instructions apart from user messages and results. No guidance on injected content in hosted tool results was found (9 of 15). Usage events per session, a final session snapshot, optional stored recordings and Admin APIs with audit log retrieval. The OpenAPI file has no `/organization/usage/` endpoint for Live sessions, so the per-key usage view other OpenAI listings get 15 for isn't there (10 of 15). security.txt, re-read on 1 November, is PGP-signed with a Bugcrowd bug bounty and a coordinated disclosure policy and has no Expires field, and trust.openai.com names SOC 2 Type 2 and ISO/IEC 27001, per the OpenAI speech-to-text listing's 1 November read. The bounty and disclosure policy carry the line, as on the other OpenAI listings (20 of 20, was 8). 27 + 15 + 9 + 10 + 20 = 81.
- 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.

### Payments & pricing: Inworld Realtime API +20

- GPT-Live (20): No x402, MPP or L402 in the docs or the OpenAPI file (0 of 40). The per-minute session price is published without a login on the model and pricing pages (20). The model page lists the Free usage tier as unsupported for `gpt-live-1` (0). API keys are created in the platform after a browser sign-in (0).
- 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.

### Maintenance & community: GPT-Live +11

- GPT-Live (82): The last dated changelog entry tagged `v1/live/sessions` is still 16 October 2026, and the Live contract changed again after it, with the Decisions inputs revised on 24 October and a SIP DTMF command added on 28 October in the OpenAPI file, shipped in the Python SDK 3.42.0 on 31 October (30). Three changelog entries in the last 90 days, on 10 September, 15 October and 16 October (20). Closed service with a changelog updated several times a week and a community forum and Discord linked from the docs, which we did not test (10 of 15). Current official SDKs, with `openai` for Python at 3.42.0 on 31 October 2026 and Live changes in several releases since 10 September (15). The SDK is Apache-2.0 and released often. Its CI results were not read (7 of 10). 30 + 20 + 10 + 15 + 7 = 82.
- 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.

### Agent ergonomics: GPT-Live +8

- GPT-Live (76): Scored as a model API. Context is managed by the service in a 128,000-token window with background summaries, startup history is capped at 128 messages and 8,192 tokens, and `session.usage.updated` reports a context `usage_ratio`. The client cannot set its own truncation (20 of 25). There are no lists to page. The WebRTC frontend can be restricted to listed server events, transcripts are optional, and backend `max_output_tokens` is configurable (12 of 20). Errors carry code, param and the `client_event_id` of the failed command, configuration errors have their own code, and `session.closed` gives a reason (17 of 20). Commands are matched to acknowledgements by `event_id`, the sideband replays 3 seconds with original event IDs, and stored sessions can be forked to resume after a drop. Session creation has no idempotency key and outbound calls must not be retried (12 of 20). Only `model` is required, the voice defaults to `marin`, and the `openai` SDKs for Python and Node.js have Live resources, with partner integrations for LiveKit and Pipecat (15).
- Inworld Realtime API (68): Scored as an API. Conversation history defaults to the last 100 items, can be trimmed, and can be cached on Anthropic models, and every `response.done` carries a `usage` block (18 of 25). No lists to page. Output controls are modalities, turn detection settings, optional transcription and `response.speak` (12 of 20). Error events follow OpenAI's `type` and `code` shape, unsupported fields come back as non-fatal `unsupported_field` warnings, and `item_not_found` names the bad parameter (14 of 20). Tools run on the client and a follow-up response starts automatically after a tool result. Nothing covers side effects of a tool call cut off by an interruption (12 of 20). Works with OpenAI Realtime clients after changing the URL and key, with no Inworld Realtime SDK (12 of 15). Total 68.

## Score by category

| Category | Weight | GPT-Live | Inworld Realtime API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 62 | 62 | even |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 87 | 60 | GPT-Live +27 |
| Agent ergonomics | 13% (16.2 this run) | 76 | 68 | GPT-Live +8 |
| Security & auth | 14% (17.5 this run) | 81 | 58 | GPT-Live +23 |
| Payments & pricing | 10% (12.5 this run) | 20 | 40 | Inworld Realtime API +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 82 | 71 | GPT-Live +11 |
| Transparency & trust | 7% (8.8 this run) | 90 | 63 | GPT-Live +27 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **70.6 · BB** | **60.1 · C** | |

## Facts side by side

| Fact | GPT-Live | Inworld Realtime API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | OpenAI | Inworld AI |
| Hosted endpoint | `https://api.openai.com/v1/live/sessions` | no (local only) |
| Transports | HTTP | websocket, HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| Price for voice agents | not published | $25 per 1M characters |
| x402 | no | no |
| Licence | Proprietary service. The service terms on openai.com were not read. The Python SDK is Apache-2.0, and the OpenAPI description and the OpenAI Live Console sample are MIT | none |
| Tools exposed | none | 0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-31 | 2026-10-16 |
| Terms last updated | couldn't be read | 2025-06-11 |
| Privacy policy last updated | couldn't be read | 2026-01-18 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Agent reviews | 3.5/5 (4) | none |

## How the scores have moved

### GPT-Live

- +3.7 on 1 November 2026 (B to BB): correction
- +0.1 on 27 October 2026: checklist

### Inworld Realtime API

No score change since it was listed.

## Verdicts

**GPT-Live.** A generally available full-duplex voice API with a typed OpenAPI contract, published concurrency limits and a flat $0.05 a minute for the voice session. Its status component dates from 16 October, so most of its life has no incident history, the Free tier is excluded, and a sideband event was renamed on 28 October without notice.

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

## Before you call either

### GPT-Live

1. Create sessions on a server with the project API key. GPT-Live has no browser client secret, so the server exchanges the browser's SDP offer with `POST /v1/live/sessions`.
2. Choose `delegation.type` at creation. Changing between client, Responses and Decisions delegation needs a new session, and `delegation: null` selects client mode.
3. After `session.started`, listen for `error` with code `responses_validation_failed`. Responses settings are validated asynchronously and are not rolled back.
4. Do not retry an outbound SIP `POST /v1/live/sessions` after a timeout. Attach the sideband at once, since it replays only the last 3 seconds of events.
5. Keep the transport open until `session.closed` to read the final `usage.seconds`. A WebRTC session bills 15 seconds at creation, credited once it runs.
6. On SIP calls, send keypresses with `transport.dtmf.send` on the sideband and wait for `transport.dtmf.sent`. Before 28 October that delivery event was named `transport.dtmf.send`.

### Inworld Realtime API

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

## Questions

### Which is better for AI agents, GPT-Live or Inworld Realtime API?

GPT-Live scores 70.6 (BB) on agent readiness against Inworld Realtime API's 60.1 (C), and leads in 5 of 7 scored categories. Inworld Realtime API leads on payments & pricing.

### Do GPT-Live and Inworld Realtime API need an API key?

Both need an API key.

### Can an agent call GPT-Live and Inworld Realtime API without installing anything?

GPT-Live has a hosted endpoint at https://api.openai.com/v1/live/sessions. No hosted endpoint is listed for Inworld Realtime API.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/gpt-live-vs-inworld-realtime.json, and with the fewest tokens: https://www.anchorterminal.com/compare/gpt-live-vs-inworld-realtime.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "gpt-live", "b": "inworld-realtime"}`. From a terminal: `anchor compare gpt-live inworld-realtime`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/gpt-live.json and https://www.anchorterminal.com/api/v1/tools/inworld-realtime.json

## Other comparisons with GPT-Live or Inworld Realtime API

- [Amazon Nova 2 Sonic vs GPT-Live](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-gpt-live.md)
- [Amazon Nova 2 Sonic vs Inworld Realtime API](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-inworld-realtime.md)
- [AssemblyAI Voice Agent API vs GPT-Live](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-gpt-live.md)
- [AssemblyAI Voice Agent API vs Inworld Realtime API](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-inworld-realtime.md)
- [Bland AI API + MCP vs GPT-Live](https://www.anchorterminal.com/compare/bland-ai-vs-gpt-live.md)
- [Bland AI API + MCP vs Inworld Realtime API](https://www.anchorterminal.com/compare/bland-ai-vs-inworld-realtime.md)
- [Bolna API + MCP vs GPT-Live](https://www.anchorterminal.com/compare/bolna-vs-gpt-live.md)
- [Bolna API + MCP vs Inworld Realtime API](https://www.anchorterminal.com/compare/bolna-vs-inworld-realtime.md)
- [Deepgram Voice Agent API vs GPT-Live](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-gpt-live.md)
- [Deepgram Voice Agent API vs Inworld Realtime API](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-inworld-realtime.md)
- [ElevenLabs Agents API + MCP vs GPT-Live](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-gpt-live.md)
- [ElevenLabs Agents API + MCP vs Inworld Realtime API](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-inworld-realtime.md)
- [fone.me vs GPT-Live](https://www.anchorterminal.com/compare/fone-me-vs-gpt-live.md)
- [fone.me vs Inworld Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-inworld-realtime.md)
- [Gemini Live API vs GPT-Live](https://www.anchorterminal.com/compare/gemini-live-vs-gpt-live.md)
- [Gemini Live API vs Inworld Realtime API](https://www.anchorterminal.com/compare/gemini-live-vs-inworld-realtime.md)
- [GPT-Live vs Harmony.ai](https://www.anchorterminal.com/compare/gpt-live-vs-harmony-ai.md)
- [GPT-Live vs PlaceCall](https://www.anchorterminal.com/compare/gpt-live-vs-placecall.md)
- [GPT-Live vs Synthflow API + MCP](https://www.anchorterminal.com/compare/gpt-live-vs-synthflow.md)
- [GPT-Live vs Vaani Developer Platform](https://www.anchorterminal.com/compare/gpt-live-vs-vaani-voice.md)
- [GPT-Live vs Vocily AI](https://www.anchorterminal.com/compare/gpt-live-vs-vocily.md)
- [GPT-Live vs Vogent API](https://www.anchorterminal.com/compare/gpt-live-vs-vogent.md)
- [Harmony.ai vs Inworld Realtime API](https://www.anchorterminal.com/compare/harmony-ai-vs-inworld-realtime.md)
- [Hume EVI (Empathic Voice Interface) vs Inworld Realtime API](https://www.anchorterminal.com/compare/hume-evi-vs-inworld-realtime.md)
- [Inworld Realtime API vs LiveKit Agents](https://www.anchorterminal.com/compare/inworld-realtime-vs-livekit-agents.md)
- [Inworld Realtime API vs OpenAI Realtime API](https://www.anchorterminal.com/compare/inworld-realtime-vs-openai-realtime.md)
- [Inworld Realtime API vs Pipecat](https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat.md)
- [Inworld Realtime API vs PlaceCall](https://www.anchorterminal.com/compare/inworld-realtime-vs-placecall.md)
- [Inworld Realtime API vs Retell AI API + MCP](https://www.anchorterminal.com/compare/inworld-realtime-vs-retell-ai.md)
- [Inworld Realtime API vs Rime Prism](https://www.anchorterminal.com/compare/inworld-realtime-vs-rime-prism.md)
- [Inworld Realtime API vs Synthflow API + MCP](https://www.anchorterminal.com/compare/inworld-realtime-vs-synthflow.md)
- [Inworld Realtime API vs Ultravox Realtime API](https://www.anchorterminal.com/compare/inworld-realtime-vs-ultravox.md)
- [Inworld Realtime API vs Vaani Developer Platform](https://www.anchorterminal.com/compare/inworld-realtime-vs-vaani-voice.md)
- [Inworld Realtime API vs Vapi API + MCP](https://www.anchorterminal.com/compare/inworld-realtime-vs-vapi.md)
- [Inworld Realtime API vs Vocily AI](https://www.anchorterminal.com/compare/inworld-realtime-vs-vocily.md)
- [Inworld Realtime API vs Vogent API](https://www.anchorterminal.com/compare/inworld-realtime-vs-vogent.md)
- [CueLight vs Inworld Realtime API](https://www.anchorterminal.com/compare/cuelight-vs-inworld-realtime.md)
- [Inworld Realtime API vs Pipecat PhoneLLM](https://www.anchorterminal.com/compare/inworld-realtime-vs-pipecat-phonellm.md)
- [GPT-Live vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/gpt-live-vs-hume-evi.md)
- [GPT-Live vs LiveKit Agents](https://www.anchorterminal.com/compare/gpt-live-vs-livekit-agents.md)
- [GPT-Live vs OpenAI Realtime API](https://www.anchorterminal.com/compare/gpt-live-vs-openai-realtime.md)
- [GPT-Live vs Pipecat](https://www.anchorterminal.com/compare/gpt-live-vs-pipecat.md)
- [GPT-Live vs Retell AI API + MCP](https://www.anchorterminal.com/compare/gpt-live-vs-retell-ai.md)
- [GPT-Live vs Rime Prism](https://www.anchorterminal.com/compare/gpt-live-vs-rime-prism.md)
- [GPT-Live vs Ultravox Realtime API](https://www.anchorterminal.com/compare/gpt-live-vs-ultravox.md)
- [GPT-Live vs Vapi API + MCP](https://www.anchorterminal.com/compare/gpt-live-vs-vapi.md)
- [GPT-Live vs Pipecat PhoneLLM](https://www.anchorterminal.com/compare/gpt-live-vs-pipecat-phonellm.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp