{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/voice-agents.web-voice-assistant/",
    "json": "https://www.anchorterminal.com/niches/voice-agents.web-voice-assistant/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/voice-agents.web-voice-assistant/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/voice-agents.web-voice-assistant/index.min.md"
  },
  "markdown": "Four or more companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 9 | 9 | 29 | 9 | 4 |\n\n## What counts as done\n\nA short-lived token minted server-side, interruptions honoured, and a client-side tool runs without the model speaking its plan aloud.\n\nMeasured, for our own tests: first audio back within 1 second of the user stopping.\n\nHow agents ask for it: add a voice assistant to my app; let users talk to the agent from the web page; a companion that reacts to tone\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **AssemblyAI Voice Agent API (AssemblyAI, Inc.)**: Server mints a single-use token with expires_in_seconds and max_session_duration_seconds; the browser connects with ?token=. Client function tools return tool.result, and hold mode keeps the agent from talking during a tool.\n- **Deepgram Voice Agent API (Deepgram, Inc.)**: The server mints a short-lived token via /v1/auth/grant with ttl_seconds and the Browser Agent SDK takes a tokenFactory; client-side functions run in the browser and return FunctionCallResponse.\n- **ElevenLabs Agents API + MCP (Eleven Labs Inc.)**: GET /v1/convai/conversation/token returns a WebRTC session token and a signed-URL endpoint exists, so the key stays server-side; client tools run in the browser with a configurable response timeout.\n- **Inworld Realtime API (Theai, Inc. dba Inworld AI)**: WebRTC with a session token minted by the backend so the Basic key stays server-side, server VAD interruption, and client-run tools with auto continuation.\n- **LiveKit Agents (LiveKit Incorporated)**: Frontends join with a short-lived access token minted on the server with the API secret; WebRTC transport, interruptions and client RPC tools are documented.\n- **OpenAI Realtime API (OpenAI OpCo, LLC)**: POST /v1/realtime/client_secrets mints an ek_ token lasting 10 seconds to 2 hours (default 10 minutes) for WebRTC in the browser; speed is settable from 0.25 to 1.5.\n- **Pipecat (Daily)**: The client SDK calls the developer's /api/start endpoint, which creates a Daily room and returns a room token, so the API key stays on the server; RTVI carries client-side function calls.\n- **Retell AI API + MCP (Retell AI Inc.)**: POST /v3/create-web-call returns a call-scoped access_token with expires_at for the browser SDK, so the API key stays on the server.\n- **Ultravox Realtime API (Theai, Inc. dba Inworld AI)**: The server creates the call and hands the client only its joinUrl, client tools run in the browser, and the agent reaction setting (listens or speaks-once) stops it narrating around a tool.\n- **Vapi API + MCP (Vapi Inc.)**: Web SDK with public keys and short-lived JWTs signed server-side with origin restrictions, plus client-side tools handled in the browser.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Amazon Nova 2 Sonic (Amazon Web Services, Inc.)**: Browser clients reach Sonic through a WebSocket server such as AgentCore with SigV4 auth; there is no short-lived client token in the Sonic docs, so the developer builds the auth layer.\n- **Bland AI API + MCP (Intelliga Corporation)**: An embeddable voice and chat widget identified by a public widget_id keeps the key off the page, but there is no token endpoint for a custom client and no client-side tool mechanism.\n- **Bolna API + MCP (Voxlabs Private Limited)**: The Web Call SDK takes a backend-minted ephemeral session (about 120 second TTL) so the key stays server-side. Client-side tools are not documented.\n- **Gemini Live API (Google LLC)**: Ephemeral tokens from auth_tokens, single use, locked by liveConnectConstraints. Resumption must be granted inside the token constraints or no handle arrives (acc-23), and one tester found replies unnaturally fast (acc-07).\n- **GPT-Live (OpenAI OpCo, LLC)**: WebRTC with the server exchanging the browser's SDP offer, so the key stays server-side, but there is no short-lived client token. Client delegation runs tools in the app and can suppress the spoken acknowledgement.\n- **Rime Prism (Rime Labs, Inc.)**: No browser tokens or ephemeral keys: the app must stream the microphone through the developer's backend, which holds the key and adds a hop before first audio.\n- **Synthflow API + MCP (AgentFlow AI GmbH)**: A backend call returns a per-session media URL and sid for a WebSocket audio stream, so the API key stays server-side, but no client-side tool mechanism is documented and the sid is not described as short-lived.\n- **Vaani Developer Platform (Vaani AI Research Private Limited (Bengaluru, India, CIN U62099KA2025PTC201212))**: POST /api/webrtc/session/create returns a session_token (session_ttl 60 to 86,400 s, default 30 minutes) that the client exchanges for WebRTC credentials, so the key stays server-side. No client-side tools documented.\n- **Vocily AI (VOCILY AI PRIVATE LIMITED)**: A website widget has voice with a public key that can be rotated, so the API key stays private, but it is a long-lived public key rather than a short-lived token and no client-side tools are documented.\n- **Vogent API (Monoid, Inc.)**: GET /dials/{id}/token returns a dial token described as safe to pass to a client, so the key stays server-side, but richer browser flows need advancedBrowserInteraction set with Vogent's help, and no client-side tools are documented.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Hume EVI (Empathic Voice Interface) (Hume AI, Inc.)**: EVI docs withdrawn (redirect to Audio Decisions), so the access-token flow could not be re-read. acc-27 moved a coding assistant's default voice from Hume EVI 3 to ElevenLabs for naturalness, citing about 300 ms latency.\n\n- not this job: CueLight (sshah03 (individual GitHub account, no name or organisation stated)): No session, token or speech model; a component only. The browser demo runs locally.\n- not this job: fone.me (Fone): The website widget lets visitors call the owner's fone.me agent by voice, but it is a keyless embed of that agent, not a session a developer controls with client tools.\n- not this job: Fresha AI Concierge (Fresha.com SV Ltd): Phone, SMS and in-app chat for Fresha clients only; no web voice SDK or token.\n- not this job: Harmony.ai (monday.com Ltd.): No browser voice SDK or client token in the API; the API covers contacts, workflows, calls and webhooks only.\n- not this job: Pipecat PhoneLLM (Daily): No browser session, token or audio; a text model only.\n- not this job: PlaceCall (VOYGR Tech, Inc.): Phone calls to businesses only; no browser or app voice session.\n\n## What stops agents finishing\n\n- no browser token, so the key would ship to the page\n- ephemeral token runs in restricted mode until resumption is granted server-side\n- voice too fast or looping with no pacing control\n\n## Around it\n\nBefore: auth.session-token. After: agent.tool-use.\n\n## Where this comes from\n\nWeight 9 of 100 in Conversational voice agents: 4 of 31 accounts (acc-06, acc-07, acc-23, acc-27)\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/voice-agents.web-voice-assistant.json, or the MCP tool get_use_case with id voice-agents.web-voice-assistant. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.\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-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "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": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Talk to an app in the browser or on a device",
        "url": ""
      }
    ],
    "description": "Talk to an app in the browser or on a device: 9 companies fully do it, 9 with a limit, 29 carry the tag. Every listing in Conversational voice agents with the reason and a source.",
    "facts": null,
    "h1": "Talk to an app in the browser or on a device",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/voice-agents.web-voice-assistant/",
    "published": "",
    "section": "agents",
    "title": "Talk to an app in the browser or on a device | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/voice-agents.web-voice-assistant/"
  },
  "tokens": {
    "markdown": 2050,
    "slim": 430
  },
  "version": 1
}
