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

# List models

> The priced model catalog routing candidates are drawn from. `pricing.in` and `pricing.out` are the provider cost basis in USD per 1M tokens, before your org markup.


## OpenAPI

```yaml openapi.json get /v1/models
openapi: 3.1.0
info:
  title: Ocean One API
  version: 2.5.0
servers:
  - url: https://api.plungeai.com
paths:
  /v1/models:
    get:
      operationId: get-v1-models
      tags:
        - Compat
      summary: Model catalog (proxied to inference-gateway) — the priced list routing candidates are drawn from.
      security:
        - ozkBearer: []
        - skOcean: []
      responses:
        "200":
          description: Priced model catalog
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/ModelCatalog"
        "401":
          description: Missing or invalid API key
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "405":
          description: "method_not_allowed — the path serves one method: the Allow header names it, plus OPTIONS"
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
          headers:
            Allow:
              description: The method this path serves, plus OPTIONS
              schema:
                type: string
        "503":
          description: money_plane_unavailable — INFERENCE_GATEWAY_SERVICE not bound on this tier
          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
            connect:
              type: object
              description: "On a 424 connection_required / credential_required: where the missing connection is made."
              properties:
                provider:
                  type: string
                method:
                  type: string
                  enum:
                    - oauth
                    - api_key
                    - wallet
                link:
                  type: string
                  example: POST /v1/connections/stripe/link
          required:
            - code
            - message
          additionalProperties: true
      required:
        - error
    ModelCatalog:
      type: object
      properties:
        object:
          type: string
        data:
          type: array
          items:
            type: object
            description: Priced model catalog entry (id, pricing, provider)
      required:
        - object
        - data
  securitySchemes:
    ozkBearer:
      type: http
      scheme: bearer
      description: "ozk_ platform API key (Authorization: Bearer ozk_…)"
    skOcean:
      type: http
      scheme: bearer
      description: "Legacy sk-ocean- inference key: still accepted on the money plane until the sk-ocean- sunset; new integrations use the ozk_ key"
```