Skip to main content
GET
List the caller's LLM configs, ordered by name.

Authorizations

Authorization
string
header
required

Session JWT. After nasiko auth login, print it with jq -r '.clusters[.active].token' ~/.nasiko/config.json. API keys aren't supported.

Response

data is an array of config objects, each with: id, name, provider, model, fallback_models, temperature, max_tokens, api_key_secret_name, pinned, pinned_model, tier1_model, tier2_model, tier3_model, embedding_provider, embedding_model, embedding_api_key_secret_name, embedding_model_override, is_default, created_at, updated_at

Standard MCP response envelope: {"data": …, "status_code": N, "message": "…"}. data is a free-form object; each route's response description says what it contains.

data
object | null
required
message
string
required
status_code
integer<int32>
required
Required range: x >= 0
Example:

200