Sarvam
Sarvam AI is an Indian-language AI platform offering a unified REST and WebSocket API across speech-to-text (Saaras / Saarika), text-to-speech (Bulbul, 30+ voices), translation and transliteration (Mayura / Sarvam-Translate) for 22 Indian languages, multilingual chat completion (Sarvam-30B and Sarvam-105B, OpenAI-compatible), and document digitization (Sarvam Vision). The API is authenticated with an api-subscription-key header, billed in Indian Rupees with ₹100 free credits on signup, and shipped with official Python and JavaScript SDKs, published OpenAPI and AsyncAPI specs, a documentation MCP server, a status page, and a dated changelog. Sarvam is backed by Bessemer Venture Partners.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Sarvam the way a machine reads it — 13 machine-readable artifacts across 8 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Sarvam scores 55.2/100 (developing), with a separate agent-readiness read of 71/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Sarvam
Each block below is one kind of artifact we hold for Sarvam. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Sarvam chat API
The chat API from Sarvam — 1 operation(s) for chat.
Sarvam documentIntelligence API
The documentIntelligence API from Sarvam — 5 operation(s) for documentintelligence.
Sarvam pronunciationDictionary API
The pronunciationDictionary API from Sarvam — 2 operation(s) for pronunciationdictionary.
Sarvam speechToText API
The speechToText API from Sarvam — 2 operation(s) for speechtotext.
Sarvam speechToTextJob API
The speechToTextJob API from Sarvam — 5 operation(s) for speechtotextjob.
Sarvam speechToTextTranslateJob API
The speechToTextTranslateJob API from Sarvam — 5 operation(s) for speechtotexttranslatejob.
Sarvam text API
The text API from Sarvam — 3 operation(s) for text.
Sarvam textToSpeech API
The textToSpeech API from Sarvam — 2 operation(s) for texttospeech.
Scroll within the panel for all 8 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
sarvam-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Endpoints
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Sarvam — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/sarvam · machine-readable index on apis.io