One API for configured routes
Connect applications once, then route chat requests through the models and providers enabled for your workspace.
Compass gives teams an OpenAI-compatible chat endpoint with workspace access, BYOK credentials, provider routing, usage records, and wallet-backed INR billing.
Set up a workspace, choose model access, keep provider credentials server-side, and give applications one Compass endpoint.
Connect applications once, then route chat requests through the models and providers enabled for your workspace.
Save a team provider key or use an administrator-managed route. Raw provider credentials stay out of client applications.
Browse the model catalog, enable compatible chat models, and optionally restrict which models each Compass key can use.
Check wallet balance before inference, record token usage, and settle each completed request with an idempotent ledger entry.
Compass connects API-key access, model routing, provider attempts, usage, and wallet settlement without exposing provider credentials to the client.
Explore request usageValidate the Compass key and resolve its workspace and model access.
Select the configured provider route, with retry and fallback handling when available.
Record provider attempts, usage, latency, status, and request metadata.
Calculate INR cost, debit the wallet once, and return an OpenAI-compatible chat response.
Review request status, model and provider, token usage, latency, and INR cost from the selected workspace.
Use the Compass Code extension to ask questions, plan changes, inspect files, and make approved edits without leaving VS Code.
Ask Compass to inspect or change this workspace.