Skip to main content
Planck normalizes reasoning controls across supported provider endpoints. Use the request shape that matches your SDK; Planck translates it to the selected provider’s format. Reasoning support and accepted effort values are model- and provider-specific. Check the model’s Request Lab at inquantum.ai/models, or inspect its endpoint capabilities with GET /v1/models/{model_id}.

OpenAI-compatible requests

Replace <provider>/<model> with a model ID from the Models page. The available effort values depend on the selected endpoint.

cURL

OpenAI Python SDK

include_reasoning is a Planck-compatible extension, so the OpenAI Python SDK example sends it through extra_body.

Anthropic-compatible requests

Use adaptive thinking and optionally set an effort. Planck translates these fields for the selected model and provider.

Python SDK

The Anthropic SDK calls its credential option api_key, but the value above is your Planck API key. The SDK sends it as x-api-key, which Planck accepts for authentication.

cURL

Anthropic thinking mappings

The compatibility route does not accept manual thinking budgets such as thinking: {"type": "enabled", "budget_tokens": 2048}. For effort-based models, use adaptive thinking with output_config.effort; an unsupported value or mode returns 400.

max_tokens behavior

Anthropic Messages requires max_tokens. The Anthropic SDK also requires it, and Planck does not add a default for an Anthropic-compatible request.
For POST /v1/chat/completions, max_tokens is optional. If you omit both max_tokens and max_completion_tokens, Planck leaves the output limit unspecified and the selected provider applies its own default. A model’s advertised maximum output is a ceiling, not an automatic default.

Bring your own Anthropic key

For normal credit usage or a provider key already stored in Planck, the single PLANCK_API_KEY setup above is sufficient. To send an Anthropic provider key explicitly with the SDK, keep the Planck key in api_key and add the provider key separately:
See Provider routing and BYOK for billing-mode selection and stored provider keys.