FrameworksFrameworks
Frameworks
Use NemoRouter with LangChain, LlamaIndex, Vercel AI, Google ADK, CrewAI, and AutoGen
Last updated
NemoRouter speaks the OpenAI REST shape, so every framework with an OpenAI integration works without a custom plugin. Point the framework's OpenAI client at https://api.nemorouter.ai/v1, pass your sk-nemo-... key, and everything else — guardrails, prompt templates, caching, rate-limits, and cost tracking — runs server-side.
Supported Frameworks
| Framework | Best for | Guide |
|---|---|---|
| LangChain | Chains, agents, RAG | Setup → |
| LlamaIndex | Document indexing, RAG | Setup → |
| Vercel AI | Next.js / React UIs | Setup → |
| Google ADK | Agent Development Kit | Setup → |
| CrewAI | Multi-agent orchestration | Setup → |
| AutoGen | Microsoft agent framework | Setup → |
What you get for free
Without changing a line of framework code:
- Guardrails — PII redaction, prompt injection blocking, keyword filters
- Caching — repeat prompts return instantly from cache
- Prompt templates — versioned, A/B-tested, injected server-side
- Rate limits — per-key / per-org RPM/TPM enforcement
- Cost tracking — every response carries
x-nemo-request-cost - Model fallbacks — switch providers by changing the model name string
What you don't have to build
- PII detection (Presidio, Microsoft Presidio Analyzer)
- Prompt injection detection
- Per-tenant rate limiting
- Cross-provider cost normalization
- Prompt versioning + rollout
- Per-request guardrail allow-listing
All of these are server-side. The framework only sees the LLM response.
Was this page helpful?