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

# Import an agent from an OCI registry: a source-tarball layer is built and

> Import an agent from an OCI registry: a source-tarball layer is built and
deployed like `/import/upload`; a plain container image is pulled and
deployed directly.



## OpenAPI

````yaml /api-reference/openapi.json post /api/import/registry
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/import/registry:
    post:
      tags:
        - catalog
      summary: >-
        Import an agent from an OCI registry: a source-tarball layer is built
        and
      description: >-
        Import an agent from an OCI registry: a source-tarball layer is built
        and

        deployed like `/import/upload`; a plain container image is pulled and

        deployed directly.
      operationId: import_registry
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/RegistryImportRequest'
        required: true
      responses:
        '201':
          description: Agent registered and deployed
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ImportResult'
        '400':
          description: Invalid reference or oversized blob
        '403':
          description: Registry import disabled or host not allowed
        '422':
          description: Registry host not in the allowed list
        '502':
          description: Registry unreachable or returned an error
        '504':
          description: docker pull timed out
components:
  schemas:
    RegistryImportRequest:
      type: object
      required:
        - reference
      properties:
        reference:
          type: string
          description: |-
            OCI reference: `"registry.host/owner/name[:tag]"`. The host must be
            allowed: a built-in default, the settings-page registry URL, or
            `REGISTRY_IMPORT_ALLOWED_HOSTS`.
    ImportResult:
      type: object
      required:
        - agent_id
        - status
      properties:
        agent_id:
          type: string
          format: uuid
        build_id:
          type:
            - string
            - 'null'
          format: uuid
        container_name:
          type:
            - string
            - 'null'
        status:
          type: string

````