Sign in
openRouterGateway

Create an OpenRouter chat completion

Relay an OpenRouter chat-completions payload through Respan with nothing filtered out, so OpenRouter-owned fields such as provider and reasoning survive the call. This endpoint is BYOK: Authorization carries your Respan API key and x-openrouter-api-key carries your OpenRouter API key. There is no fallback to Respan gateway credits. OpenRouter's response, status code, and event stream are relayed back unchanged.

post/api/openrouter/v1/chat/completions

Headers

Authorizationstring required

Use your Respan API key for Respan API authentication. Enter only the Respan API key value; clients send Authorization: Bearer <RESPAN_API_KEY>. For /api/responses, provider credentials such as Perplexity, OpenAI, or Azure OpenAI go in Settings -> Providers or respan_params.credential_override in the request body, not in this authentication field.

x-openrouter-api-keystring required

Your OpenRouter API key. Authorization carries the Respan API key on this operation.

Request body

modelstring required

OpenRouter model slug, for example anthropic/claude-sonnet-4-5. An openrouter/ prefix is also accepted and is stripped before the call goes upstream.

messagesobject[] required
streamboolean
providerobject

OpenRouter provider routing block, forwarded unchanged.

reasoningobject

OpenRouter reasoning block, forwarded unchanged.

respan_paramsobject

Respan gateway metadata. Stripped before the payload reaches OpenRouter.

Response

OpenRouter response or event stream.

object required

Changes