Skip to main content
The VLM Run Gateway serves open-weight vision and document models through a single OpenAI-compatible API. Each model declares the input types it accepts (text, image_url, document_url) and the operations it supports via the method field.

Visual Question Answering (VQA)

VQA models accept text plus up to 64 images, one video, or a PDF in the same message. PDFs fan out per-page chat instead of OCR. See method parameters for more details.

Document and Image OCR

These models accept a PDF via document_url or an image via image_url. The VLM Run Gateway rasterizes each page and runs per-page inference, returning <document>-wrapped page blocks, concatenated (non-streaming) or streamed in document order (streaming). Use method: "ocr" for full OCR, or method: "detect" when you only need text detection and bounding polygons. zai-org/glm-ocr and rednote-hilab/dots.mocr support both OCR and reading-order markdown output; dots.mocr also exposes layout parsing methods. For images, the Gateway runs inference on the entire image. For consistency purposes, we do not stream on a token-by-token basis. See method parameters for more details.

Embeddings and Transcription

These models appear on GET /v1/openai/models with a task field other than chat. They use separate OpenAI-compatible endpoints, not chat completions. See Embeddings and Audio Transcriptions for full request schemas.
Python

Model Aliases

Many models accept multiple request IDs:
  1. Preferred: lowercase <org>/<slug> (listed on /models)
  2. Short: slug only (e.g. pp-ocrv6)
  3. Hugging Face: upstream repo id (e.g. PaddlePaddle/PP-OCRv6_medium_det)

Next steps

Flexible Document OCR

End-to-end recipe from model selection to response parsing.

Methods

Per-model method and method_params reference.

Chat Completions API

Full request parameters, streaming, and error handling.

Error Codes

HTTP status mapping, correlation ids, and support details.