OpenAI-compatible API - Orq.ai Documentation

The AI Gateway exposes endpoints that are fully compatible with the OpenAI API, letting you use every model available in the AI Gateway without changing your application logic. Keep the existing OpenAI client, point it to the Orq.ai proxy baseURL, and continue as usual.

For the OpenAI API specification, see the API Reference

To move an existing application from the OpenAI SDK, the Anthropic SDK, OpenRouter, or LiteLLM, see Migrate to Orq.ai.

Drop-in Integration (No Code Changes)

Keep your existing OpenAI SDK or HTTP integration.
Set the base URL to https://my.orq.ai/v3/router
Use the Orq.ai API Key in the Authorization header.
Call the same endpoints and payloads already used with OpenAI.

Base URL

OpenAI-compatible endpoint:

https://my.orq.ai/v3/router

All routes below are relative to this base URL. The OpenAI-compatible routes mirror OpenAI’s request and response formats.

Authentication

Authenticate with the Orq.ai API key via the Authorization: Bearer $ORQ_API_KEY header.

To learn more about Orq API Key, see API Key.

Minimum headers:

Authorization: Bearer $ORQ_API_KEY
Content-Type: application/json

Supported Endpoints

OpenAI-compatible

These routes match the OpenAI API: same schema, parameters, and response format. See the compatibility notes below for the exceptions.

GET /models: List available models
POST /chat/completions: Chat completions (supports streaming, images, files, and tool calls)
POST /completions: Text completions
POST /embeddings: Vector embeddings (Embeddings)
POST /images/generations: Image generation
POST /images/edits: Image editing
POST /images/variations: Image variations
POST /moderations: Text moderation (Rerank and Moderations)
POST /audio/speech: Text-to-speech
POST /audio/transcriptions: Transcribe audio into the input language
POST /audio/translations: Translate audio into English
POST /responses: Create a model response with built-in tools (Responses API, Web Search)
GET /responses/{response_id}: Retrieve a stored response (Responses API)

Orq.ai routes

These routes are served on the same base URL but use their own request and response contracts, not the OpenAI ones.

POST /rerank: Rerank results (Rerank and Moderations)
POST /decisions: Run typed classification questions against a decision model (Decisions)
POST /classify: Deprecated alias for POST /decisions
POST /ocr: Extract text and structure from a document or image (OCR)

Models

Use the model field exactly as you would with OpenAI, substituting the ID of any model available in the AI Gateway Models.

Error Handling & Compatibility Notes

HTTP status codes and error structures follow OpenAI’s conventions.
Streaming, function/tool calls, and multimodal inputs (images/files) are supported on /chat/completions.
Sending tools to /chat/completions with an OpenAI reasoning model such as openai/gpt-5.6-sol returns 400. Use /responses instead, or set reasoning_effort to none, which drops the reasoning the model would otherwise do. See Migrate to Orq.ai.
The AI Gateway serves the current surface under /v3/router: target this path for new integrations. The earlier paths under /v2/router/ remain published for backward compatibility.