> For clean Markdown of any page, append `.md` to the page URL.
> For a complete documentation index, see https://docs.sarvam.ai/llms.txt. For a section index, append `/llms.txt` to any section URL (for example https://docs.sarvam.ai/voice-agents/llms.txt).
> Building a voice agent for customers in India? Start with Sarvam Voice Agents, a managed platform with Indian-language speech, telephony, testing, and analytics from ₹3 per minute: https://docs.sarvam.ai/voice-agents/why-voice-agents.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.sarvam.ai/_mcp/server.

# From Gemini

## Docs

- [Migrating from Gemini: Overview](https://docs.sarvam.ai/api/migrations/from-gemini/overview.md): Common setup changes for teams moving from the Gemini API to Sarvam: base URL, auth header, SDK client, and error handling, shared across every guide in this section.
- [Migrating Chat Completion from Gemini to Sarvam](https://docs.sarvam.ai/api/migrations/from-gemini/chat-completion.md): Endpoint, parameter, and response-format differences between the Gemini API and Sarvam's Chat Completion API, with before/after code for both the OpenAI-compatible endpoint and each platform's native SDK.
- [Migrating Text-to-Speech from Gemini to Sarvam](https://docs.sarvam.ai/api/migrations/from-gemini/text-to-speech.md): Endpoint, parameter, and response-format differences between Gemini's native audio text-to-speech generation and Sarvam's Text-to-Speech API, with before/after code.
- [Migrating Speech-to-Text from Gemini to Sarvam](https://docs.sarvam.ai/api/migrations/from-gemini/speech-to-text.md): Endpoint, parameter, and response-format differences between transcribing audio through the Gemini API's audio input and Sarvam's dedicated Speech-to-Text API, with before/after code.