API overview
Gateway base addresses, the list of endpoints and which request format fits a model.
Base URL
OpenAI-compatible tools and SDKs (base URL already includes /v1):
https://ai-seller.vibe-codes.ru/v1Anthropic SDK and Claude Code (the SDK appends /v1/messages itself):
https://ai-seller.vibe-codes.ruEndpoints
| Endpoint | Description |
|---|---|
POST /v1/chat/completions | Chat Completions — base OpenAI format, streaming supported |
POST /v1/responses | Responses — Codex format, streaming supported |
POST /v1/messages | Messages — Anthropic and Claude Code format, streaming supported |
POST /v1/images/generations | Image generation, billed per image |
POST /v1/videos | Create a video job: 202 + id for polling; billed per second on completion |
GET /v1/videos/{id} | Video job status |
GET /v1/videos/{id}/content | Download the finished video — after GET /v1/videos/{id} reports status completed |
GET /v1/models | Model catalog (key optional; with a key it also lists models opened to your account) |
GET /v1/balance | Current balance (by API key) |
There are no other endpoints: for example, /v1/embeddings and
/v1/messages/count_tokens return 404 not_found.
Every request is authorized with a key — see Keys and authentication.
Every response carries an x-request-id header — the same id as request_id
in an error body; include it when contacting support.
Request format and model
The gateway does not translate between request formats: a request to
/v1/chat/completions, /v1/messages or /v1/responses reaches the model's
provider in the same format. So a model answers on an endpoint only if its
provider supports that format. If a model returns an error on one text
endpoint, try another — /v1/chat/completions is the most widely supported.
The model type must match the endpoint: an image model on the chat endpoint (and
vice versa) gets 404 model_not_found, just like a model that does not exist.
What the gateway changes in a request
Only supported parameters reach the model, and client identifiers are replaced
with the gateway's — see Request parameters. Your request
headers (for example, OpenAI-Beta or anthropic-beta) are not passed to the
provider. Send the full conversation history with every request: the gateway
keeps no provider-side state.
Updated September 29, 2026