Skip to main content
The Gateway uses OpenAI request and response shapes at /v1/openai. There is no mapping layer and no request rewriting. The same chat.completions.create call reaches a vision model.

Pointing the SDK at the Gateway

Authentication is optional at the moment. Omit the Authorization header for anonymous access. Tiers and quotas are in Authentication.

Check the connection

Compatibility matrix

Put request extensions at the top level of the body, or in extra_body on the OpenAI SDKs. The full list and defaults are in Chat Completions.

Supported parameters

Each model lists the OpenAI parameters it honours in supported_parameters on GET /v1/openai/models. A model with a non-empty list returns 400 capability_violation for any other parameter. A model with an empty list accepts the standard fields and ignores them. ● The model honours the parameter. Blank means the model does not, and a non-empty list rejects it with 400.
  • Chat VLMs: qwen/qwen3.5-0.8b, qwen/qwen3.8-27b, and google/gemma-4-26b-a4b-it.
  • Provider models: google/gemini-*, meta/muse-*, moonshotai/kimi-k3, and minimax/minimax-m3.
  • OCR models: every model with an empty supported_parameters list. They accept sampling fields and ignore them.
Embeddings take dimensions and encoding_format. Transcription takes language, response_format, and timestamp_granularities.

Defaults and limits

Quickstart

First VQA and document OCR requests.

Chat Completions

Request reference, including every Gateway extension.

Methods

Select the operation with method and method_params.

Response Formats

JSON mode for code, text mode for agents.

TypeSafe SDK Compatibility

Get typed, calibrated decisions from the same Gateway.