agentleFS
sarvamaisarvamai/skills/text-to-speech/SKILL.md

text-to-speech

Skill72 starsChanged 46 days agoApache-2.0View on GitHub

Write correct Sarvam Bulbul TTS code — bulbul:v4-flash persona speaker IDs (voice_language_style), REST, HTTP stream, WebSocket, pronunciation dictionaries, and v3/v4 traps (short names rejected on v4, param ranges). Use this skill when generating speech in an app with Python or JS/TS. For live TTS in chat via MCP, use sarvam-mcp instead.

  • Reads credentials

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use voice-changer, speech-engine and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • wlzhSkill

    voice-changer

    音频变声处理工具 - 使用 RVC AI 模型进行真实的声音转换,支持视频直接输入

    Also in 4 projects that use this

  • RobStrayerSkill

    speech-engine

    Add real-time voice conversations to a custom agent runtime with ElevenLabs Speech Engine. Use when building Speech Engine servers, WebSocket handlers, WebRTC browser clients, conversation token endpoints, interruption-aware streaming responses, or voice-enabled chat agents that connect developer-owned server logic to ElevenLabs speech-to-text and text-to-speech.

    Also in 3 projects that use this

  • RobStrayerSkill

    voice-isolator

    Remove background noise and isolate vocals/speech from audio using ElevenLabs Voice Isolator (audio isolation) API. Use when cleaning up noisy recordings, removing music or background ambience from dialogue, isolating speech from field recordings, preparing audio for transcription, extracting vocals, or any "denoise / clean up / isolate voice" task.

    Also in 3 projects that use this

  • LinHao-citySkill

    setup-api-key

    Guides users through setting up an ElevenLabs API key for ElevenLabs MCP tools. Use when the user needs to configure an ElevenLabs API key, when ElevenLabs tools fail due to missing API key, or when the user mentions needing access to ElevenLabs. First checks whether ELEVENLABS_API_KEY is already configured and valid, and only runs full setup when needed.

    Also in 5 projects that use this

  • LinHao-citySkill

    bfl-api

    BFL FLUX API integration guide covering endpoints, async polling patterns, rate limiting, error handling, webhooks, and regional endpoints with Python and TypeScript code examples.

    Also in 3 projects that use this

  • MoizIbnYousafSkill

    visual-style

    Build a persistent visual brand identity for image generation. Defines how the brand looks visually — aesthetic, lighting, composition, mood — and writes it to brand/creative-kit.md so /image-gen and other creative skills produce consistent on-brand visuals. Three modes: Extract (from website/URL), Build (interview), Reference (mood board/examples). Use when starting any project that needs images, when the user says "visual style", "brand aesthetic", "image style", "visual identity", "how should our images look", "build visual brand", "define our look", or when /image-gen outputs feel generic because no visual style exists yet.

    Also in 4 projects that use this

  • +5 more from LinHao-city

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not copy speaker="ishita" from the Voices “generate your own sample” snippet — that is a v3 short name and fails on v4-flash.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Text-to-Speech — Bulbul

Live in-chat TTS → sarvam-mcp (sarvam_tools_tts_*). This skill = SDK code.

[!IMPORTANT] Auth: api-subscription-key header — NOT Authorization: Bearer. Base URL: https://api.sarvam.ai (NOT /v1 — that prefix is only for the OpenAI-compatible chat endpoint) SDK floor for the code below: Python sarvamai>=0.1.29, JS sarvamai@>=1.1.8. On older versions the TTS param is target_language_code — see Gotchas.

Model

bulbul:v4-flash — latest, use this for new integrations. Same REST / HTTP stream / WebSocket contract as v3. 200+ persona voices (222 IDs).

bulbul:v3 — what the API uses when model is omitted. Short names (shubh, priya). Still the right model for Malayalam and Odia, which have no v4 personas yet.

Speakers (v4 Flash)

IDs are lowercase voice_language_style: aparna_hi_customer, simran_en_customer, shubh_enhi_ads. Omit speaker and the default is shubh_enhi_ads. v2/v3 short names (shubh, priya, ishita, anushka) return 400.

The middle token is a language tag (hi, en, bn, gu, kn, mr, pa, ta, te) or enhi for English–Hindi code-mix. Use an _enhi_ persona when one utterance is genuinely mixed; a few English loanwords in Hindi script do not need it.

language_code still takes the usual BCP-47 values (hi-IN, en-IN, … including ml-IN and od-IN). There are no ml or od persona IDs — for those languages set model="bulbul:v3" and a v3 short name.

Use caseHindiEnglish
Customer careaparna_hi_customeraparna_en_companion
Salesaparna_hi_customer, shubh_hi_customersimran_en_sales
Collectionssimran_hi_recoveryshubh_en_recovery
Hinglish (one utterance)simran_enhi_customer—

Do not copy speaker="ishita" from the Voices “generate your own sample” snippet — that is a v3 short name and fails on v4-flash.

Coverage by language (live-verified 2026-10-06; one working persona each — pick others from the live list):

LanguageExample personaLanguageExample persona
en-INsimran_en_customer, sunny_en_socialmr-INishita_mr_conversational
hi-INaparna_hi_customer, shubh_hi_customergu-INbhavik_gu_conversation
hi-IN (Hinglish)shubh_enhi_ads (the default)kn-INchaitra_kn_conversation
bn-INroopa_bn_conversational, arnab_bn_conversationpa-INanand_pa_conversation
ta-INgokul_ta_narration, aravind_ta_adste-INkavitha_te_conversation

The roster changes. Sarvam renamed voices on 2026-10-06 (bappa_bn_conversation → arnab_bn_conversation, vetri_ta_ads/vetri_ta_suspense → aravind_ta_*), and the old IDs now 400. Do not hardcode IDs from memory or old blog posts. An unknown speaker returns 400 with the full live list, so the list is one bad request away. The API also lists 2 Assamese (_as_) personas that the docs catalog does not.

Quick Start (Python)

from sarvamai import SarvamAI
from sarvamai.play import save

client = SarvamAI()

response = client.text_to_speech.convert(
    text="नमस्ते, आप कैसे हैं?",
    language_code="hi-IN",
    model="bulbul:v4-flash",
    speaker="aparna_hi_customer",
    enable_preprocessing=True,
)
save(response, "output.wav")

# HTTP Stream (lower latency, binary audio)
chunks = []
for chunk in client.text_to_speech.convert_stream(
    text="Hello from Sarvam AI",
    language_code="en-IN",
    model="bulbul:v4-flash",
    speaker="simran_en_customer",
    output_audio_codec="wav",
):
    chunks.append(chunk)
audio = b"".join(chunks)

Quick Start (JavaScript/TypeScript)

import { SarvamAIClient } from "sarvamai";
import { writeFile } from "fs/promises";

const client = new SarvamAIClient({ apiSubscriptionKey: "YOUR_SARVAM_API_KEY" });

// REST
const response = await client.textToSpeech.convert({
    text: "नमस्ते, आप कैसे हैं?",
    language_code: "hi-IN",
    model: "bulbul:v4-flash",
    speaker: "aparna_hi_customer",
    enable_preprocessing: true,
});

// HTTP Stream (lower latency, returns BinaryResponse)
const streamResponse = await client.textToSpeech.convertStream({
    text: "Hello from Sarvam AI",
    language_code: "en-IN",
    model: "bulbul:v4-flash",
    speaker: "simran_en_customer",
    output_audio_codec: "wav",
});
const bytes = await streamResponse.bytes();
await writeFile("output.wav", bytes);

WebSocket Streaming

import asyncio
from sarvamai import AsyncSarvamAI

async def tts_stream():
    client = AsyncSarvamAI()
    async with client.text_to_speech_streaming.connect(model="bulbul:v4-flash") as ws:
        await ws.configure(
            target_language_code="hi-IN",
            speaker="aparna_hi_customer",
            output_audio_codec="wav",
        )
        await ws.convert("Your text here")
        await ws.flush()
        async for message in ws:
            pass  # base64 audio chunks

asyncio.run(tts_stream())

Character Limits

MethodMax Text
REST (convert)2,500 chars
HTTP Stream (convert_stream)3,500 chars
Legacy inputs array (raw REST)500 chars per item — send text instead to get the 2,500 limit
WebSocket2,500 chars/msg (keep <500 for lowest latency; send many messages per connection)

Gotchas

GotchaDetail
Set model or you get v3Omitting model selects bulbul:v3. v3 short names then work; v4 persona IDs do not. New code sets model="bulbul:v4-flash".
v3/v2 short names on v4shubh, priya, ishita, anushka, etc. are rejected. Use voice_language_style. Unknown IDs 400 with the live speaker list.
language_code is version-gatedPython >=0.1.29 and JS >=1.1.8 (both 2026-08-03) take language_code; earlier versions take target_language_code. Hard rename — no alias, no deprecation shim, and the JSON body key changed too, so the wrong name raises TypeError before any request goes out. Check with pip show sarvamai / npm ls sarvamai if you hit that.
WebSocket was not renamedPython ws.configure() still takes target_language_code (mapped to language_code on the wire). Docs that pass language_code= into ws.configure() raise TypeError. JS configureConnection() takes language_code.
JS method nameclient.textToSpeech.convert({...}) and .convertStream({...}) — camelCase. Stream returns BinaryResponse with .stream(), .bytes(), .blob().
pitch / loudness rangespitch −0.5–0.5 (default 0), loudness 0.1–2.5 (default 1), pace 0.5–2.0. Out-of-range values return 400. Bulbul v3 used to reject pitch / loudness; as of 2026-10-06 it accepts them too (live-verified). v2-only ranges in the model-page limits table do not apply.
Streaming codec defaultHTTP stream and WebSocket do not default to WAV. Set output_audio_codec (wav or mp3; also flac / aac on HTTP stream). opus can appear in the schema and currently errors on /text-to-speech.
Sample ratespeech_sample_rate 8000, 16000, 24000 and 48000 verified on v4-flash REST (the returned WAV matches the requested rate).
Sample rate >24kHz32kHz, 44.1kHz, 48kHz only via REST, not streaming. Omitted → 22050 Hz.
REST responseBase64-encoded audio in response.audios[0]. Use sarvamai.play.save() or base64.b64decode(). Writing the raw base64 string to disk is not playable audio.
Speaker must match modelThe mismatch fails both ways: a v3 short name on bulbul:v4-flash and a v4 persona on bulbul:v3 both return 400. Pair model and speaker explicitly.
No SSMLSSML markup is NOT supported. Use pace (and on v4, pitch / loudness) plus sentence-boundary chunking.
Use native scriptRomanized Indic input ("Aapka order confirm ho gaya hai") degrades quality. Write Indic words in native script; keep English loanwords in Latin ("आपका order confirm हो गया है"). With enable_preprocessing=true, do not hand-expand numbers, dates, or currency.
ml-IN / od-IN have no v4 personasCodes are accepted. The catalog has no Malayalam or Odia IDs. Use bulbul:v3 for those languages.
Pronunciation dictionaryPass dict_id on v4-flash the same way as v3 (10 dicts/user, 100 words/dict). Create via Python client.pronunciation_dictionary.create(file=f). JS SDK upload is broken (missing multipart Content-Type) — use raw fetch + FormData with an explicit Blob type. The pronunciation-page limits row that says “v3 only” is stale; the examples on that page send dict_id with bulbul:v4-flash.

Full Docs

Fetch the voice catalog, ranked picks, streaming protocol, and codec options from:

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.