Skip to main content
Nasiko does not host models. It routes to the providers you already have. Built-in providers ship in the catalog. Custom providers are any OpenAI-compatible endpoint you register.

​
Built-in catalog

The LLM router screen lists the same catalog under Available providers, with a model count and a Requires API key chip. Click a provider to create a config with it preselected. Keys are stored as secrets; they are never displayed back. API: GET /api/llm-router/providers.

​
Custom providers

On the LLM router screen, Register any OpenAI-compatible endpoint adds a provider whose models then appear for tier routing. Supported kinds: Superuser only for create, update, delete, test and sync. Any authenticated user can list providers and list a provider’s models. Until a price book row exists for a custom model, TokenOps marks its cost estimated.

​
How agents reach a provider

Deployed agents never hold the real key. At deploy time Nasiko points the agent’s SDK at the cluster (LLM_GATEWAY_BASE_URL) and injects a short-lived identity JWT as OPENAI_API_KEY. Coding harnesses use the same router through model routing. The router endpoints: All except /v1/health require an agent JWT. Missing or unresolvable traceparent is a 403 — see cost attribution.