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

# Search project context documents

> Find evidence across selected project context documents. Batch independent queries; use passages directly when sufficient. Results merge overlapping text and include source ranges and zero-based queryIndexes into queries. matched reports a hit; truncated means evidence may be omitted, clipped means partial lines, and unavailableResourceIds were not searched. Resolve missing evidence before concluding a fact is absent.



## OpenAPI

````yaml /api-reference/openapi.json post /websiteKnowledge/search
openapi: 3.1.0
info:
  title: Cactal API
  version: 1.0.0
  description: >-
    The Cactal public API. Create, edit, publish, and operate websites
    programmatically. Authenticate every request with an API key sent as
    `Authorization: Bearer <key>`.
servers:
  - url: https://api.cactal.ai/v1
security:
  - apiKey: []
tags:
  - name: Documentation
    description: >-
      Search and read the Cactal product documentation for concepts, guides,
      agent workflows, platform behavior, and API operations.
  - name: Feedback
    description: >-
      Submit free-form product feedback from users and agents to the Cactal
      feedback inbox.
  - name: Websites
    description: >-
      Create and manage websites — the top-level resource that owns source code,
      content, assets, domains, and analytics.
  - name: Website editors
    description: >-
      Grant, list, and revoke website-scoped editor access, and invite
      collaborators to a single website by email.
  - name: API keys
    description: >-
      Create, scope, rotate, and revoke the API keys that authenticate
      programmatic and agent access.
  - name: Source code
    description: >-
      Read and edit the framework source files of a website draft. Mutations
      require an edit lease.
  - name: Publishing
    description: Validate, build, publish, and roll back website versions.
  - name: CMS collections
    description: >-
      Define the content model: collections of structured content owned by a
      website.
  - name: CMS fields
    description: Manage the typed fields that make up a collection schema.
  - name: CMS items
    description: >-
      Create, query, publish, and organize the content entries inside a
      collection.
  - name: Domains
    description: >-
      Manage platform subdomains and custom domains, including DNS verification
      and the primary domain.
  - name: Assets
    description: Upload and manage website files and images served from the Cactal CDN.
  - name: Media generation
    description: >-
      Generate reference-guided website images that are stored as ordinary
      Cactal CDN assets.
  - name: Project Context
    description: >-
      Upload private durable reference material that the website agent can
      search, read, and inspect.
  - name: Analytics
    description: >-
      Read first-party traffic analytics for a website and export datasets as
      CSV.
  - name: Organizations
    description: Manage organizations, members, and organization-wide invitations.
  - name: Audit log
    description: >-
      Read the immutable record of actions performed in an organization by users
      and API keys.
  - name: Billing
    description: >-
      Read billing state and manage plans, site capacity, and prepaid usage
      balance. Every billing operation requires the organization owner role,
      which API keys cannot hold — today these operations are performed from the
      dashboard, return 403 for API-key callers, and are hidden from MCP tool
      lists.
paths:
  /websiteKnowledge/search:
    post:
      tags:
        - Project Context
      summary: Search project context documents
      description: >-
        Find evidence across selected project context documents. Batch
        independent queries; use passages directly when sufficient. Results
        merge overlapping text and include source ranges and zero-based
        queryIndexes into queries. matched reports a hit; truncated means
        evidence may be omitted, clipped means partial lines, and
        unavailableResourceIds were not searched. Resolve missing evidence
        before concluding a fact is absent.
      operationId: websiteKnowledge.search
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                websiteId:
                  type: string
                  minLength: 1
                resourceIds:
                  minItems: 1
                  maxItems: 25
                  type: array
                  items:
                    type: string
                    minLength: 1
                  description: >-
                    Selected text resource ids from the project context index,
                    in relevance order.
                queries:
                  minItems: 1
                  maxItems: 8
                  type: array
                  items:
                    type: string
                    minLength: 1
                    maxLength: 500
                    pattern: ^[^\r\n]+$
                  description: >-
                    Independent case-insensitive literal terms matched within a
                    line, not questions or regular expressions.
                contextLines:
                  default: 2
                  type: integer
                  minimum: 0
                  maximum: 5
                maxCharacters:
                  default: 8000
                  description: >-
                    Shared passage character budget across all documents and
                    queries.
                  type: integer
                  minimum: 4000
                  maximum: 16000
              required:
                - websiteId
                - resourceIds
                - queries
      responses:
        '200':
          description: Deduplicated passages, query coverage, and unavailable resource ids.
          content:
            application/json:
              schema:
                type: object
                properties:
                  queries:
                    type: array
                    items:
                      type: object
                      properties:
                        query:
                          type: string
                        matched:
                          type: boolean
                        truncated:
                          type: boolean
                      required:
                        - query
                        - matched
                        - truncated
                      additionalProperties: false
                  passages:
                    type: array
                    items:
                      type: object
                      properties:
                        resourceId:
                          type: string
                        filename:
                          type: string
                        startLine:
                          type: integer
                        endLine:
                          type: integer
                        content:
                          type: string
                        clipped:
                          type: boolean
                        queryIndexes:
                          type: array
                          items:
                            type: integer
                      required:
                        - resourceId
                        - filename
                        - startLine
                        - endLine
                        - content
                        - clipped
                        - queryIndexes
                      additionalProperties: false
                  unavailableResourceIds:
                    type: array
                    items:
                      type: string
                required:
                  - queries
                  - passages
                  - unavailableResourceIds
                additionalProperties: false
        '400':
          description: >-
            Validation failed. The response `message` names the first invalid
            field.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceError'
        '401':
          description: Missing, invalid, expired, or revoked API key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceError'
        '403':
          description: The authenticated principal lacks the required capability.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceError'
        '404':
          description: >-
            The resource does not exist or is outside the principal’s access
            scope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceError'
        '429':
          description: >-
            Rate limit exceeded. Retry after the number of seconds in the
            `Retry-After` header.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceError'
components:
  schemas:
    ServiceError:
      type: object
      required:
        - kind
        - message
      description: >-
        Canonical error body returned by every non-2xx response. Extra fields
        carry error-specific details.
      properties:
        kind:
          type: string
          enum:
            - validation
            - unauthorized
            - forbidden
            - not_found
            - conflict
            - rate_limited
            - internal
          description: Stable, machine-readable error category.
        message:
          type: string
          description: Human-readable explanation of the failure.
        suggestion:
          type: string
          description: >-
            What to do next when the failure has a known fix; may name the exact
            operation to call.
        validValues:
          type: array
          items:
            type: string
          description: The acceptable values for the failing field, when the set is closed.
      additionalProperties: true
  securitySchemes:
    apiKey:
      type: http
      scheme: bearer
      description: >-
        Cactal API key. Create one in the dashboard or via `POST /apiKeys`. The
        plaintext key is shown once at creation.

````