> ## 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.

# Fetch a single agent by UUID or name, rendered as an A2A AgentCard-shaped envelope.



## OpenAPI

````yaml /api-reference/openapi.json get /api/agents/{id}
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/agents/{id}:
    get:
      tags:
        - catalog
      summary: >-
        Fetch a single agent by UUID or name, rendered as an A2A
        AgentCard-shaped envelope.
      operationId: get_one
      parameters:
        - name: id
          in: path
          description: Agent UUID or name
          required: true
          schema:
            type: string
      responses:
        '200':
          description: Agent card
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SingleResponse'
        '403':
          description: Caller cannot access this agent
        '404':
          description: No agent with this id/name
components:
  schemas:
    SingleResponse:
      type: object
      required:
        - data
        - status_code
        - message
      properties:
        data:
          $ref: '#/components/schemas/AgentDetailResponse'
        message:
          type: string
        status_code:
          type: integer
          format: int32
          minimum: 0
    AgentDetailResponse:
      type: object
      required:
        - id
        - name
        - owner_id
        - can_manage
        - is_coding_agent
        - compress_enabled
        - minimal_code_enabled
        - has_coding_skills
        - metadata
        - status
        - version
        - description
        - url
        - preferredTransport
        - protocolVersion
        - capabilities
        - securitySchemes
        - security
        - defaultInputModes
        - defaultOutputModes
        - skills
        - tags
        - supportsAuthenticatedExtendedCard
        - signatures
        - created_at
        - updated_at
      properties:
        additionalInterfaces: {}
        can_manage:
          type: boolean
          description: |-
            True when the caller may manage this agent (owner or superuser) —
            computed with the same predicate the mutating routes enforce
            (`crate::acl::can_manage_agent`), so the UI can gate its management
            tabs without guessing.
        capabilities: {}
        coding_agent_integration_id:
          type:
            - string
            - 'null'
        compress_enabled:
          type: boolean
          description: >-
            Per-agent payload-compression opt-in. The Settings toggle renders
            from this, so a

            projection that omits it shows the switch off however the column
            reads.
        created_at:
          type: string
          format: date-time
        defaultInputModes:
          type: array
          items:
            type: string
        defaultOutputModes:
          type: array
          items:
            type: string
        description:
          type: string
        display_name:
          type:
            - string
            - 'null'
        documentationUrl:
          type:
            - string
            - 'null'
        has_coding_skills:
          type: boolean
          description: >-
            Whether this agent's card reads as code work, and so should be
            offered minimal-code

            mode at all. Served rather than re-derived in the browser: the
            settings page used to

            run its own `/code/i` over the skills, mirroring a Postgres `ILIKE
            '%code%'` in the

            dispatch path, and the two could disagree — which is exactly what
            happened, since both

            missed `coding` (no "code" in it) while matching `encode`.
        iconUrl:
          type:
            - string
            - 'null'
        id:
          type: string
          format: uuid
        is_coding_agent:
          type: boolean
        metadata:
          description: >-
            Owner-writable bag, and the home of `features.*` — the flags

            `AppState::agent_env` turns into `NASIKO_<KEY>` on the container.


            Third occurrence of the same trap the two fields above warn about,
            and the worst of

            them: the Settings feature switches render from `metadata.features`,
            and the UI builds

            its `PUT` body by spreading the value it read back. Omitted here it
            was always

            `undefined`, so every switch showed off however the column read
            *and* each save

            replaced the whole column with just the one feature it was toggling.
        minimal_code_enabled:
          type: boolean
          description: >-
            Drives the control plane's minimal-code ladder injection at A2A
            dispatch

            time (a2a_dispatch.rs). Same reasoning as compress_enabled above —
            omit

            it here and the Settings toggle shows off regardless of the real
            value.
        name:
          type: string
        owner_id:
          type: string
          format: uuid
          description: Owner's user UUID — lets the UI label the owner row in grant lists.
        preferredTransport:
          type: string
        protocolVersion:
          type: string
        provider: {}
        security:
          type: array
          items: {}
        securitySchemes: {}
        signatures:
          type: array
          items: {}
        skills:
          type: array
          items: {}
        status:
          type: string
        supportsAuthenticatedExtendedCard:
          type: boolean
        tags:
          type: array
          items:
            type: string
        updated_at:
          type: string
          format: date-time
        url:
          type: string
        version:
          type: string

````