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

# Generic completion endpoint (v2 — legacy)

> **Use when:** caller is on the legacy v2 SDK and needs a unified completion endpoint that dispatches by `type` discriminator — prefer the modality-specific `/v3/*` endpoints for new code

Legacy generic-completion endpoint. Accepts a unified Verlon request body (with `type` discriminator: `chat`, `image`, `video`, `embeddings`, `tts`, `ocr`) and routes through the named gate. New integrations should prefer the modality-specific `/v3/*` endpoints, which have richer per-task surfaces. Maintained for backward compatibility with v2-era SDK callers.



## OpenAPI

````yaml /api-reference/openapi.json post /v2/complete
openapi: 3.1.0
info:
  title: Verlon AI API
  version: 1.0.0
  description: >-
    Verlon AI is the managed AI infrastructure platform for developers building
    LLM-powered apps and agents. Beyond routing requests across providers,
    Verlon continuously evaluates response quality, runs experiments against
    live traffic, and automatically tunes gate configurations — so your platform
    doesn't just serve traffic, it learns from it.


    **Coding agents:** authentication, error semantics, gate concepts, and
    integration conventions are documented at https://verlon.ai/AGENTS.md — read
    that document first if you have not already. It is the canonical
    agent-facing contract; this specification is the canonical endpoint
    reference. Both are authoritative for their respective scopes.
  contact:
    name: Verlon AI
    url: https://verlon.ai
  license:
    name: Proprietary
servers:
  - url: https://api.verlon.ai
    description: Production
security:
  - bearerAuth: []
paths:
  /v2/complete:
    post:
      tags:
        - Completion (v2 legacy)
      summary: Generic completion endpoint (v2 — legacy)
      description: >-
        **Use when:** caller is on the legacy v2 SDK and needs a unified
        completion endpoint that dispatches by `type` discriminator — prefer the
        modality-specific `/v3/*` endpoints for new code


        Legacy generic-completion endpoint. Accepts a unified Verlon request
        body (with `type` discriminator: `chat`, `image`, `video`, `embeddings`,
        `tts`, `ocr`) and routes through the named gate. New integrations should
        prefer the modality-specific `/v3/*` endpoints, which have richer
        per-task surfaces. Maintained for backward compatibility with v2-era SDK
        callers.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                gateId:
                  type: string
                type:
                  type: string
                data:
                  type: object
                  additionalProperties: {}
                  default: {}
                model:
                  type: string
                metadata: {}
                endUserId:
                  type: string
              required:
                - gateId
      responses:
        '200':
          description: >-
            Verlon-normalized completion response. Shape depends on the task
            type the gate is configured for.
        '400':
          description: Invalid request — Zod validation failure or malformed input
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Missing or invalid Bearer credentials
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '402':
          description: Over spending limit or rate-limited.
        '404':
          description: Gate not found or not owned by the caller.
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      security:
        - bearerAuth: []
components:
  schemas:
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
          description: Stable error code (e.g. `invalid_request`)
        message:
          type: string
          description: Human-readable error message
        details: {}
      required:
        - error
        - message
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: API Key
      description: >-
        Verlon API key (newly minted keys are prefixed `sk-vrln-`; legacy
        `verlon_*` and `layer_*` keys from prior prefix migrations continue to
        validate). Generated from the dashboard under Settings → API Keys, or
        via `verlon key create` in the CLI.

````