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

# Generate Manifest

> Generate a manifest from natural language description.

    Uses AI to create a valid YAML manifest from a natural language description
    of desired resources. The generated manifest can be reviewed and applied.

    **Example:**
    ```bash
    curl -X POST /v1/manifest/generate \
      -H "Authorization: Bearer $API_KEY" \
      -H "Content-Type: application/json" \
      -d '{
        "description": "I need a bucket of images that feeds into a multimodal extractor and a retriever",
        "manifest_name": "image-search-setup"
      }'
    ```

    **Response:**
    ```json
    {
      "manifest": "version: '1.0'
metadata:
  name: image-search-setup
...",
      "format": "yaml",
      "manifest_name": "image-search-setup",
      "description": "I need a bucket of images..."
    }
    ```

    **Next Steps:**
    1. Review the generated manifest
    2. Apply it using POST /v1/manifest/apply



## OpenAPI

````yaml post /v1/manifest/generate
openapi: 3.1.0
info:
  title: Mixpeek API
  description: >-
    This is the Mixpeek API, providing access to various endpoints for data
    processing and retrieval.
  termsOfService: https://mixpeek.com/terms
  contact:
    name: Mixpeek Support
    url: https://mixpeek.com/contact
    email: info@mixpeek.com
  version: '0.82'
servers:
  - url: https://api.mixpeek.com
    description: Production
security: []
paths:
  /v1/manifest/generate:
    post:
      tags:
        - Manifest
      summary: Generate Manifest
      description: |-
        Generate a manifest from natural language description.

            Uses AI to create a valid YAML manifest from a natural language description
            of desired resources. The generated manifest can be reviewed and applied.

            **Example:**
            ```bash
            curl -X POST /v1/manifest/generate \
              -H "Authorization: Bearer $API_KEY" \
              -H "Content-Type: application/json" \
              -d '{
                "description": "I need a bucket of images that feeds into a multimodal extractor and a retriever",
                "manifest_name": "image-search-setup"
              }'
            ```

            **Response:**
            ```json
            {
              "manifest": "version: '1.0'
        metadata:
          name: image-search-setup
        ...",
              "format": "yaml",
              "manifest_name": "image-search-setup",
              "description": "I need a bucket of images..."
            }
            ```

            **Next Steps:**
            1. Review the generated manifest
            2. Apply it using POST /v1/manifest/apply
      operationId: generate_manifest_v1_manifest_generate_post
      parameters:
        - name: description
          in: query
          required: true
          schema:
            type: string
            title: Description
        - name: manifest_name
          in: query
          required: false
          schema:
            type: string
            default: generated-manifest
            title: Manifest Name
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    ErrorResponse:
      properties:
        success:
          type: boolean
          title: Success
          description: Always false for error responses
          default: false
        status:
          type: integer
          title: Status
          description: HTTP status code for this error
        error:
          $ref: '#/components/schemas/ErrorDetail'
          description: Error details payload
      type: object
      required:
        - status
        - error
      title: ErrorResponse
      description: Error response model.
      examples:
        - error:
            details:
              id: ns_123
              resource: namespace
            message: Namespace not found
            type: NotFoundError
          status: 404
          success: false
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ErrorDetail:
      properties:
        message:
          type: string
          title: Message
          description: Human-readable error message
        type:
          type: string
          title: Type
          description: Stable error type identifier (machine-readable)
        code:
          anyOf:
            - type: string
            - type: 'null'
          title: Code
          description: >-
            Fine-grained error code for programmatic handling (e.g.,
            namespace_name_taken, feature_extractor_not_found). Present only
            when consumers may need to branch on a specific error condition.
        details:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          title: Details
          description: >-
            Optional structured details to help debugging (validation errors,
            IDs, etc.)
      type: object
      required:
        - message
        - type
      title: ErrorDetail
      description: Error detail model.
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError

````