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

# Search the registry

> Hybrid semantic and keyword search over capability cards. Pages with `limit` and `offset`; a page shorter than `limit` is the last one.


## OpenAPI

```yaml openapi.json get /v1/discovery/search
openapi: 3.1.0
info:
  title: Ocean One API
  version: 2.1.0
servers:
  - url: https://api.plungeai.com
paths:
  /v1/discovery/search:
    get:
      summary: Search the capability registry (hybrid semantic + keyword)
      security:
        - ozkBearer: []
      parameters:
        - name: q
          in: query
          schema:
            type: string
          description: Natural-language capability query
        - name: kind
          in: query
          schema:
            type: string
            enum:
              - agents
              - skills
              - digital-twins
              - personas
              - experts
              - backgrounds
              - workflows
              - models
              - providers
              - connectors
              - plugins
              - mcp-servers
          description: Plural capability group, e.g. agents, mcp-servers
        - name: type
          in: query
          schema:
            type: string
        - name: category
          in: query
          schema:
            type: string
        - name: status
          in: query
          schema:
            type: string
            default: active
        - name: tier
          in: query
          schema:
            type: string
        - name: limit
          in: query
          schema:
            type: integer
        - name: offset
          in: query
          schema:
            type: integer
        - name: mode
          in: query
          schema:
            type: string
            enum:
              - hybrid
              - keyword
              - vector
        - name: fields
          in: query
          schema:
            type: string
            enum:
              - list
              - summary
              - full
      responses:
        "200":
          description: Registry search envelope
          content:
            application/json:
              schema:
                type: object
                properties:
                  cards:
                    type: array
                    items:
                      $ref: "#/components/schemas/Card"
                  count:
                    type: integer
                  searchMethod:
                    type: string
        "401":
          description: Missing/invalid ozk_ key
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
components:
  schemas:
    Card:
      type: object
      description: Registry capability card (summary fields).
      properties:
        id:
          type: string
        name:
          type: string
        type:
          type: string
        category:
          type: string
        status:
          type: string
        description:
          type: string
        tags:
          type: array
          items:
            type: string
        quality:
          description: Present only when the search was called with include=quality; null when unmeasured (no eval-service binding on this tier, no runs yet, or an upstream miss).
          type:
            - object
            - "null"
          properties:
            score:
              type:
                - number
                - "null"
            success_rate:
              type:
                - number
                - "null"
            runs:
              type: integer
      required:
        - id
        - name
        - type
        - category
        - status
      additionalProperties: true
    Error:
      type: object
      description: Standard error envelope. Every error response also carries an `X-Error-Code` response header equal to error.code, so a client branches on the header regardless of the negotiated body format (json | yaml | markdown | text). When the request created an execution, the `X-Execution-Id` response header is also set. Errors follow the negotiated format like success bodies.
      properties:
        error:
          type: object
          properties:
            code:
              type: string
            message:
              type: string
          required:
            - code
            - message
          additionalProperties: true
      required:
        - error
  securitySchemes:
    ozkBearer:
      type: http
      scheme: bearer
      description: "ozk_ platform API key (Authorization: Bearer ozk_…)"
```