Vocode

Documented custom tool support in the open source library. Actions are tools the agent runs mid conversation through function calling (or when it says a configured phrase), built by subclassing BaseAction, and External Actions send a JSON schema payload to any API the builder names and feed the response back to the agent, with request signing; the docs note actions work with ChatGPTAgent.

SourceVocode, docs.vocode.dev (Adding Actions to Agents, External Actions, Action Triggers)read 2026-09-27

A fixed conversation pipeline, no workflow model. A StreamingConversation runs a transcriber, an agent and a synthesizer with endpointing, interruption handling and conversation speed settings, and actions run through an ActionsWorker queue; nothing sequences multi step work the builder designs, and the LangChain agent option hands response logic to LangChain, which is LangChain's capability.

SourceVocode, docs.vocode.dev (How it works, Conversation Mechanics, LangChain Agent)read 2026-09-27

No retrieval over the customer's content in the open source library. Its docs cover conversations, providers, telephony, actions and logging; context reaches the agent through the prompt and action results. The [Beta] Vector databases page connects an agent to the customer's Pinecone index, but only through the hosted API (vocode_client.agents.update_agent), whose host api.vocode.dev no longer resolves, so a buyer cannot receive it today.

SourceVocode, docs.vocode.dev (llms.txt, Vector databases)read 2026-09-27

No oversight or handoff documented for the open source library. Actions run when the model calls them or when the agent says a configured phrase, and nothing holds an action for a person or limits it beyond the builder's own code. The hosted docs describe a [Beta] warm transfer and a HIPAA flag, both on the hosted API, whose host no longer resolves, and the repository's source includes a transfer call action that the open source docs do not describe.

SourceVocode, docs.vocode.dev (Action Triggers, Adding Actions to Agents, Warm Transfer)read 2026-09-27

Nothing documented. The library is MIT licensed code the builder runs, so identity, access and compliance are the builder's; the docs name no access model and no attestation. External Actions can sign requests with a shared secret, which authenticates an integration call rather than governing who uses the agent, and the HIPAA flag belongs to the hosted API, whose host no longer resolves.

SourceVocode, docs.vocode.dev (External Actions, HIPAA Compliance) and the vocode-core repository; github.com/vocodedev/vocode-coreread 2026-09-27

Performance spans and event hooks, with the per call record left to the builder. A [Beta] Sentry integration sends Vocode's custom spans for each conversation to the builder's Sentry, the Events Manager emits transcript, action and call events for the builder to handle, and a logging guide covers local and production runs; no store of what each agent did per call is documented.

SourceVocode, docs.vocode.dev ([Beta] Sentry Integration, Events manager, llms.txt)read 2026-09-27

Conversation state inside a call. The agent works from the call's transcript, and each action's result is added to that transcript and shapes later turns; the telephony server keeps each call's configuration in the builder's Redis. Nothing carries into the next call and no memory layer with a scope and lifetime is documented.

SourceVocode, docs.vocode.dev (Adding Actions to Agents, Working with phone calls)read 2026-09-27

Runs wherever the builder deploys it. The MIT licensed library installs from PyPI into the builder's own environment, the telephony server runs under Docker or directly with Python, and a documented fully local setup runs transcription, the LLM and synthesis on the builder's own machine without internet access. The hosted option no longer resolves.

SourceVocode, docs.vocode.dev (Fully local conversation, Working with phone calls)read 2026-09-27

No packaged agents. Vocode offers quickstarts, playground scripts and the repository's apps (a telephony server, a LiveKit app, a Telegram bot, a React client backend, a LangChain agent, a voice RAG demo), which are scaffolds for channels and integrations rather than agents for a job.

SourceVocode, docs.vocode.dev (Open Source Quickstarts, Playground) and the vocode-core repository; github.com/vocodedev/vocode-coreread 2026-09-27

Phone, web and meeting channels, no autonomous wake. The self hosted TelephonyServer answers inbound Twilio calls through a webhook and places outbound calls when the builder's script runs OutboundCall; agents also dial into Zoom, talk over WebSockets from the React client, and run over WebRTC through LiveKit. Every session starts with a caller or the builder's code, and no schedule, event or queue that wakes an agent is documented. The hosted API also offered call automation, but its host no longer resolves.

SourceVocode, docs.vocode.dev (Working with phone calls, Using WebRTC with LiveKit) and the vocode-core READMEread 2026-09-27

The builder chooses every provider. Out of the box transcribers (AssemblyAI, Deepgram, Gladia, Google Cloud, Microsoft Azure, Rev.ai, Whisper, whisper.cpp), LLMs (OpenAI, Anthropic) and synthesizers (Rime, Azure, Google Cloud, Play.ht, ElevenLabs, Cartesia, Coqui, AWS Polly and more) are set per conversation in config, open source models run locally, and a custom agent can wrap any text in, text out model.

SourceVocode, vocode-core README and docs.vocode.dev (How it works, Create your own AI Agent, Fully local conversation); github.com/vocodedev/vocode-coreread 2026-09-27

The SDK is the product. vocode on PyPI is an MIT licensed Python library with documented extension points for custom agents, actions, transcribers and synthesizers, a FastAPI telephony server, and a React client library. The Node SDK belonged to the hosted API.

SourceVocode, vocode-core repository and docs.vocode.dev (Create your own AI Agent, Adding Actions to Agents, React Quickstart); github.com/vocodedev/vocode-coreread 2026-09-27

No evaluation of agent behavior. Playground scripts let a developer try a transcriber, agent or synthesizer by hand, which is inspection rather than a scored test or quality gate, and no evaluation harness is documented.

SourceVocode, docs.vocode.dev (Playground, llms.txt)read 2026-09-27

The browser appears only as a client for voice conversations through the React library, and no browser, desktop or computer control is documented.

SourceVocode, docs.vocode.dev (llms.txt, React Quickstart)read 2026-09-27