Credits Add credits

₹—

Email me when balance falls below ₹ save

Your new API key — copy it now, it won't be shown again: Copy key

Ready-to-run curl (your key is already in it) qwen2.5-7b-instruct Copy curl ▶ Test it now

Full docs: quickstart · Python/Node samples included.

API keys Create key All workspaces

Where did you first hear about BharatRouter? skip

Activity requests · tokens · spend

Last 7 days Last 30 days Last 90 days Custom… – Apply All models All keys

Requests newest first — follows the filters above

Load more

Fallback chains — org-wide routing: requests for a model walk YOUR chain in order, across providers and even across models

Same JSON for agents: PUT /me/routing/<model> or the set_fallback_chain MCP tool. Per-request fallbacks overrides a saved chain. Test chains live in the failover playground.

Your custom endpoints (BYOE) — register your OWN OpenAI-compatible deployments as fallback steps for a model (priced ₹0 — your infra). Admitted to routing only after a compliance test. Multiple per model allowed.

Agents: POST /me/endpoints or the register_endpoint MCP tool. Keys are encrypted at rest and never shown again. Once registered & compliant, pick it as a step's provider below.

New chain

Requests for are served by, in order:

+ Add step Save chain Publish as Collection…

Workspaces — operational environments inside your org (e.g. Production, Staging, per-team). Each scopes its own API keys and usage; your org keeps the single wallet, members and billing.

+ New workspace

How it splits: a workspace owns the operational side — its API keys and (soon) BYOK keys, ₹/mo budget caps and guardrails. Your org owns everything legal & financial — one wallet, members & roles, GST/billing. New keys land in whichever workspace you pick; keys with no workspace sit in the org default. Same JSON for agents: GET/POST /me/workspaces.