Grok Responses

Use the Grok / xAI API family for xAI-compatible Responses requests. The Grok / xAI route restricts dispatch to Grok-family models and upstreams; the HTTP request and SSE response bodies use xAI’s OpenAI-compatible Responses shape.

This protocol describes the routing boundary, not a different customer payload format. An OpenAI SDK can use this API when its base_url is set to https://api.kineticrouter.com/grok/v1.

Base URL and endpoint

Protocol root:

Planned example

The dedicated Grok route is planned and its configuration is shown only as a reference. This example is intentionally not copyable in its current display state.

Responses endpoint:

Planned example

The dedicated Grok route is planned and its configuration is shown only as a reference. This example is intentionally not copyable in its current display state.

Authentication

Pass your kineticRouter API key as a Bearer token:

Planned example

The dedicated Grok route is planned and its configuration is shown only as a reference. This page preserves the dedicated Grok request shape as an integration reference. This example is intentionally not copyable in its current display state.

Request examples

Terminal
Planned example

The dedicated Grok route is planned and its configuration is shown only as a reference. This example is intentionally not copyable in its current display state.

Streaming

Set stream: true to receive xAI-compatible SSE events:

grok_responses_stream.py
Planned example

The dedicated Grok route is planned and its configuration is shown only as a reference. This example is intentionally not copyable in its current display state.

Continuations and WebSocket clients

Use previous_response_id only with a response previously created by the same kineticRouter principal. The router keeps the continuation bound to its original Grok upstream account; unavailable or foreign response IDs are rejected instead of being sent to another account.

A compatible Responses WebSocket ingress is available at:

Planned example

The dedicated Grok route is planned and its configuration is shown only as a reference. This example is intentionally not copyable in its current display state.

It is a kineticRouter bridge to xAI HTTP/SSE for each turn. It does not indicate that xAI provides a native WebSocket transport.

Current text models

Model IDNotes
grok/grok-4.5Default frontier model with a 500,000-token context window.
grok/grok-composer-2.5-fastText-only coding model with a 200,000-token context window; image input is not supported.

For Chat Completions instead of the Responses shape, see Grok Chat Completions.