> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nasiko.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Clear the default flag on one of the caller's configs, leaving them with no

> Agents that were falling back to this default resolve to `source: "none"`
afterwards and use the platform key path (see `resolve_agent_config`).



## OpenAPI

````yaml /api-reference/openapi.json delete /api/llm-configs/{id}/default
openapi: 3.1.0
info:
  title: Nasiko API
  description: >-
    HTTP API for the Nasiko OpenRuntime: agents, coding harnesses, TokenOps,
    routing, MCP, and secrets. Spec is generated from annotated routes; some
    surfaces are documented on the hand-written pages alongside this file.
  license:
    name: ''
  version: 0.1.0
servers: []
security: []
tags:
  - name: secrets
    description: Encrypted per-user agent secrets
  - name: catalog
    description: >-
      Agent catalog: registration, discovery, versions, per-agent secrets, and
      source import
  - name: agents
    description: >-
      Agent lifecycle: deployments, LLM routing config, update/rollback,
      upload-and-deploy
  - name: orchestrator
    description: >-
      A2A dispatch: routing-engine/ReAct orchestrator and direct agent chat,
      plus routing stats
  - name: users
    description: >-
      User management: CRUD, roles, credentials, accessible agents
      (superuser-only)
  - name: usage
    description: Per-user token usage and cost reporting
  - name: observability
    description: Sessions, traces, spans, agent logs, and FinOps reporting
  - name: llm-router
    description: LLM routing presets, provider/model catalog, and tier→model registry
  - name: mcp
    description: >-
      MCP gateway: agent-facing JSON-RPC tool calls, connector
      registration/upload/sharing, credentials & OAuth, and per-agent tool
      permissions
paths:
  /api/llm-configs/{id}/default:
    delete:
      tags:
        - llm-router
      summary: >-
        Clear the default flag on one of the caller's configs, leaving them with
        no
      description: >-
        Agents that were falling back to this default resolve to `source:
        "none"`

        afterwards and use the platform key path (see `resolve_agent_config`).
      operationId: clear_default
      parameters:
        - name: id
          in: path
          description: LLM config id
          required: true
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: '`data` is the config object, now with `is_default: false`'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/McpEnvelope'
        '401':
          description: Missing or invalid session
        '404':
          description: Unknown id, or not owned by the caller
components:
  schemas:
    McpEnvelope:
      type: object
      description: |-
        Doc-only schema for the standard MCP `ApiResponse` envelope
        (`{"data": …, "status_code": N, "message": "…"}`). Most `/api/mcp/*`
        payloads are service-layer `serde_json::Value` views, so `data` is
        documented as a free-form object; each route's response description says
        what it carries.
      required:
        - data
        - status_code
        - message
      properties:
        data:
          type:
            - object
            - 'null'
        message:
          type: string
        status_code:
          type: integer
          format: int32
          example: 200
          minimum: 0

````