Change Log

You can now connect third-party tools to Sarvam and use them in your voice agents. Open Integrations in the sidebar to browse or search the catalogue, connect a tool once for the whole workspace by approving access on the vendor’s consent screen, or add any other MCP server by its endpoint URL. To use one, open Add a tool in the agent editor, choose MCP, and tick the actions that agent should be able to call — each parameter can be a fixed value, an agent variable, or decided from the conversation.

You can now add files up to 5 GB to a knowledge base, up from the 100 MB the upload dialog was quietly allowing. Files that are too large or the wrong type are now flagged with a clear message instead of disappearing without explanation. See Knowledge Bases.

deepseekv4.1-flash-1017 is now generally available on POST /v2/chat/completions and POST /v2/responses. Your API key no longer needs beta access. It reasons at high by default (reasoning_effort: "none" turns thinking off), accepts text and image input, and has a 1,048,576-token context window.

Pricing is unchanged: ₹25 input, ₹0.5 cached input, and ₹105 output per 1M tokens. See Pricing.

You can now store the keys for your own HTTPS APIs in Cowork and use them in your personal chats and on agents you own, so an agent can call a service you already pay for without anyone re-entering credentials. Saved keys stay private to the person who added them. See Connectors.

When you click Download CSV in Call Logs, we now email you a download link once your file is ready. You can also find your exports from the last 7 days under Recent exports.

You can now exclude contacts already on a campaign with Exclude cohort. Upload a CSV of users to remove — matched by user identifier or phone number — via the same cohort upload endpoint with cohort_category set to stop_file. An exclude cohort only removes contacts already on that campaign; it does not filter users added later. See Exclude cohort.

language_code / target_language_code is now optional on POST /voices/clone, POST /voices/clone/stream, and GET /voices/clone/ws. Omit it to detect the language from text. Pass the code when pronunciation has to be exact — detection can be wrong on short or code-mixed text, romanized Indic and Urdu return 400, and short Assamese without ৰ or ৱ is often detected as Bengali. On the WebSocket the first detection stays locked until you send a new config with an explicit code. See Supported languages.

You can now connect GitHub App as a Cowork connector and choose exactly which repositories your agent can reach. In our tests it finished tasks 26% faster and used 40% fewer tokens than the old connector. See Connectors.

Agent pages now have a Mine / Team toggle, so you can see your own recent sessions or those of your teammates in the same workspace. Any session opens as a read-only transcript you can review after the run finishes.

POST /v2/chat/completions and POST /v2/responses are now generally available with GLM-5.3, Gemma 4 31B, and DeepSeek V4.1 Flash, alongside sarvam-105b. No beta whitelisting is required for these endpoints or models. See Beta APIs and Models for anything still in beta.

New open-weight models are available on POST /v2/chat/completions and POST /v2/responses.

Generally available:

• glm5.3-flash: a faster GLM-5.3 with image input, log probabilities, and n > 1. Reasons by default. 1,048,576-token context.

In beta:

POST /v2/chat/completions and POST /v2/responses are now generally available with sarvam-105b, glm5.3, glm5.3-flash, and gemma4. Your API key no longer needs to be whitelisted. The new models in the entry above are in beta; see Beta models.

Call recordings are now captured in stereo, with the user on the left channel and the agent on the right. Mono recordings mixed both speakers onto a single channel, so overlapping speech was summed and could clip; in stereo each speaker stays isolated, which makes recordings easier to listen to and better suited for downstream processing (transcription, analytics). This is now enabled for all calls. See Call recordings.

The Analytics API now gives you more of what happened on each call. Get forwarded recording returns the recording of the part of a call after your agent transferred it, currently for transfers made through Vobiz, and Get trace returns a call’s step-by-step event trace: the speech recognition, LLM, tool-call, and text-to-speech events of every turn, plus the conversation’s start, end, and post-call analysis. List attempts and List interactions now include provider details for each call, channel_provider (the telephony provider that carried it) and provider_identifier (that provider’s own call ID, such as a call SID), so you can match calls to your provider’s records. Both also add deployment_id, app_version, bot_contact_identifier (your agent’s own number), and goal results in goal_overall_status and goal_criteria. You can also sort by attempted_at, and filter on app_version and goal_overall_status.

You can now save up to 50 cloned voices on the Starter plan, up from 5. Pro and Enterprise plans have higher limits. Voices are counted across your whole organization, in Content Studio and the API, and deleting a voice frees up a slot. See Managing Your Voice Library.

Genie, the AI assistant in Voice Agents, now goes beyond creating and editing agents. It is available from every Voice Agents page through Ask Genie, in a panel that stays open as you move between pages, so you can build an agent, deploy it, and check its calls in a single chat. Genie can now put an agent live on one of your connected phone numbers for inbound calls and place a test call to your phone. It can also create outbound campaigns, upload contact lists from a CSV, and pause, resume, edit, or cancel campaigns. To analyze calls, Genie can summarize performance and connect rates, explain why calls didn’t connect, read transcripts, check tool errors, and build Boards. Within an agent, it can also set up knowledge bases and test suites. Genie asks you to confirm before anything that places calls, affects live traffic, or can’t be undone. See Genie.

Bulbul V3 reaches end of life on Voice Agents on November 10, 2026. Switch every agent that speaks with Bulbul V3 to Bulbul V4 before that date. In the agent’s Settings, set the model under Speaking to Bulbul V4 and pick a voice. To keep a voice you use today, find its Bulbul V4 name in Voice name changes from V3 to V4. This change applies to Voice Agents only. Bulbul V3 stays available on the Text-to-Speech API.

You can now control how loud your voice agent sounds. A new Volume slider in the agent’s voice settings (Sarvam / Bulbul voices) sets the loudness of the agent’s speech, from 0.7 (quieter) to 2.0 (louder), with 1.0 as the natural level. The volume is stored with the agent’s voice configuration and applied on every call, so it can be set once and manipulated later. See Speakers & voice.

You can now edit the presentations and documents your agent creates, right in the app. Every edit you make becomes the next version, and any document can be exported as a PDF.

The sarvamai Python and TypeScript SDKs now expose Instant Voice Cloning (beta) with the same call shape as Bulbul Text-to-Speech: voice_cloning.convert / voiceCloning.convert for one-shot synthesis, convert_stream / convertStream for HTTP streaming, and voice_cloning_streaming / voiceCloningStreaming for WebSocket sessions (configure → convert → flush). Voice lifecycle helpers (create_voice, list_voices, get_voice, delete_voice) live on the same voice_cloning client. Paths stay under /voices/*. Requires the text_to_speech_voice_cloning capability. See the Instant Voice Cloning overview and install sarvamai ≥ 0.1.37 (Python) or sarvamai ≥ 1.1.12 (TypeScript). Older alphas such as 0.1.31a7 do not include the full streaming APIs.