ReferenceReference
Protocol compatibility
What passes through unchanged, and what the gateway adds or strips.
By the end: You know how closely the gateway follows each provider's native API.
The gateway is a pass-through. It does not convert between protocols, so the request shape must match the model family you call.
| Route | Protocol | Use a model from |
|---|---|---|
| /v1/chat/completions | OpenAI Chat Completions | Any text model — this shape is the common denominator |
| /v1/responses | OpenAI Responses | GPT models |
| /v1/messages | Anthropic Messages | Claude models |
| /v1beta/models/* | Gemini native | Gemini models |
Chat Completions is the interoperable route
Most models — including Claude, Gemini, and the Chinese families — answer the OpenAI Chat Completions shape through this gateway. When a tool only speaks OpenAI, point it at that route and any catalog model will work.
Headers that pass through
anthropic-version and anthropic-beta are forwarded on the Messages routes. Accept is forwarded so content negotiation still works. Nothing else from your request headers reaches the upstream service.
Base URL: https://www.ary4n73.com