Sarvam 2B

Cost & access

Sarvam 2B weights are available under Proprietary. Direct API cost may be $0 if you self-host; budget for GPUs, storage, and engineering instead. Hosted endpoints (Together, Fireworks, Groq, etc.) charge per token—shop providers for sarvam-2b latency and region. With a 128K tokens context window, long PDFs or chat histories increase input tokens quickly—trim history or summarize older turns in production.

Functional understanding

• Indian language small LM.
• Modalities: text · License: Proprietary · Released 2024-08-01.
• Best-fit workflows for this model:
• • High-throughput, low-cost inference at the edge or on a single GPU with Sarvam 2B.
• • Classification, routing, and guardrail checks before calling a larger model.
• • On-prem or VPC deployment when data cannot leave your network.

Technical foundation

• Sarvam AI reports Undisclosed parameters; training data: Undisclosed.
• Context: 128K tokens. Open weights: yes.
• Sarvam 2B is sized for efficient inference; pair with a larger model when quality plateaus.

First API call

Run Sarvam 2B locally with Ollama or Hugging Face transformers (weights under Proprietary).

# Ollama (if model is published there)
# ollama run sarvam-2b

# Or Hugging Face transformers:
from transformers import pipeline

pipe = pipeline("text-generation", model="sarvam-2b", device_map="auto")
print(pipe("Hello from Sarvam 2B", max_new_tokens=80)[0]["generated_text"])

Important technical topics

• Prompting Sarvam 2B: be explicit about output format. Weak: "Analyze this." Better: "Return JSON with fields id, total, date for Sarvam AI billing data."
• Temperature: use 0–0.3 for extraction and compliance on Sarvam 2B; 0.7–1.0 for brainstorming.
• Tokens: Sarvam 2B bills by tokens (~¾ word each). Undisclosed parameters affect capability; your bill is driven by context length and call volume.
• Context window (128K tokens): everything in one request—system prompt, tools, RAG chunks, and history—must fit. Truncate or summarize when approaching the limit for Sarvam 2B.

Real enterprise patterns

• Deploy Sarvam 2B on edge for intent classification; call frontier model only when needed.
• Quantize (GGUF/AWQ) to hit latency SLOs on consumer GPUs.
• A/B test against larger models on a golden eval set.
• Auto-scale replicas for bursty traffic—small models shine at high QPS.

Production & security

• Secrets: never commit keys for Sarvam 2B; use vault + per-environment rotation.
• PII: mask before inference; log redacted prompts only.
• Observability: trace id per request; log model=sarvam-2b, tokens in/out, latency.
• GPU monitoring: VRAM, batch queue depth, and model revision hash on each deploy.
• Guardrails: schema-validate JSON; block disallowed topics; cross-check numbers against source docs.

Mini projects with this model

• Intent router: Sarvam 2B labels queries → dispatches to specialist models.
• Toxicity/PII screen before main chat.
• Extract-only JSON from short emails at scale.
• On-device chat demo on a laptop GPU.

Suggested stack

• Language: Python 3.11+
• Model: Sarvam 2B via Ollama, vLLM, or Hugging Face
• Hardware: NVIDIA GPU with enough VRAM for quantization level
• API wrapper: FastAPI or LiteLLM proxy
• UI: Streamlit or Next.js for internal tools
• APIs: FastAPI
• Vector DB (RAG): Pinecone / Chroma / pgvector

Learning path

• Python basics
• HTTP/REST and environment variables
• Sarvam AI authentication and Sarvam 2B model id (sarvam-2b)
• First successful call to Sarvam 2B
• Prompt design and JSON / structured outputs
• RAG
• Tool use / function calling
• Evals and regression sets
• Production deploy + monitoring