chat.completions.
Point base_url at https://gateway.vlm.run/v1/openai, and every model on the catalog speaks
the same request shape your existing SDK calls already use.
Why the Gateway
General-purpose model routers are built for text LLMs, so they usually cover only a small slice of visual workloads. The VLM Run Gateway is built around OCR and VQA instead:- One API, multiple supported models. Use
qwen/qwen3.5-0.8bfor visual question answering, including video and per-page PDF chat,paddleocr/pp-ocrv6for OCR and text detection, andzai-org/glm-ocr/rednote-hilab/dots.mocrfor document OCR and layout parsing, all through the samechat.completionsshape. - Embeddings and transcription too.
qwen/qwen3-vl-embedding-2bembeds text and images into the same vector space for visual search, andnvidia/parakeet-tdt-0.6b-v3handles audio transcription, including subtitle output (srt/vtt). Both are available through their own OpenAI-compatible endpoints under the samebase_urland API key. - Document routing built in. Multi-page PDFs are decoded, rasterized, and fanned out per page automatically at the ingress layer, so you do not have to split or stitch documents yourself.
- Method and DPI routing.
methodselects the operation a model runs (ocr,detect,markdown, …);document_dpitunes how much detail reaches the OCR model per page. - Operational signals included. Use the live catalog at
GET /v1/openai/models, per-requestusage.costfor metering, andx-request-idfor tracing on every response.
Next steps
Quickstart
Prerequisites, plus first VQA and document OCR requests.
Flexible Document OCR
Request knobs, page blocks, and streaming for PDFs.
Models
Catalog, capabilities, and model selection.
Methods
Method and
method_params reference.