Skip to main content
Use the request format your application already understands. The format does not determine the underlying provider: an OpenAI-compatible request can still target a supported Claude, Gemini, Qwen, or other model.

OpenAI-Compatible Chat

Set stream: true to receive the response incrementally with server-sent events. The streaming guide includes complete TypeScript, Python, cURL, and raw SSE examples. See Chat Completions for the complete request schema.

Responses API

See Responses API for supported request behavior.

Reasoning and thinking

OpenAI-compatible requests use reasoning_effort and include_reasoning. Anthropic-compatible requests use thinking and output_config.effort. Planck normalizes both formats before routing the request. See Reasoning and thinking for cURL, OpenAI SDK, and Anthropic SDK examples.

Anthropic-Compatible Messages

The mapped Messages route accepts Anthropic-style inputs and returns an Anthropic-style response while retaining gateway routing, billing, and observability.
max_tokens is required for Anthropic-compatible Messages requests. To use the Anthropic SDK, set its base URL to https://api.inquantum.ai/anthropic and pass your Planck API key to the SDK’s api_key option. The SDK appends /v1/messages. See Anthropic-compatible routes for a complete SDK example and the distinction between mapped Messages and other native endpoints.

Observability

Successful and failed generations appear in Requests with their model, provider, tokens, duration, cost, user, custom properties, and response status. Add your own user, session, or property headers when you need application-level attribution.

Configure routing and BYOK

Choose providers, supply provider keys, and configure fallbacks.