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

# Get a card

> Read one capability card as markdown (the LLM view): operations, examples and "Not for" redirects.


## OpenAPI

```yaml openapi.json get /v1/discovery/cards/{type}/{id}
openapi: 3.1.0
info:
  title: Ocean One API
  version: 2.1.0
servers:
  - url: https://api.plungeai.com
paths:
  /v1/discovery/cards/{type}/{id}:
    get:
      summary: Fetch a capability card (markdown LLM view)
      security:
        - ozkBearer: []
      parameters:
        - name: type
          in: path
          required: true
          schema:
            type: string
            enum:
              - agent
              - skill
              - digital_twin
              - expert
              - background
              - workflow
              - model
              - provider
              - connector
              - plugin
              - mcp_server
          description: Singular card type; plural search kinds (agents, mcp-servers, …) are accepted aliases
        - name: id
          in: path
          required: true
          schema:
            type: string
      responses:
        "200":
          description: Card markdown
          content:
            text/markdown:
              schema:
                type: string
        "400":
          description: invalid_request — a bad type/id is normalised to the One-API error envelope
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "404":
          description: not_found — no such card
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
components:
  schemas:
    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_…)"
```