Before you begin
Create a Planck API key from API Keys, then load it as a server-side environment variable:1. List the models available to you
GET /v1/models is authenticated and returns models accessible with your credentials, Planck credit availability, and organization policy.
endpoints. Capabilities can differ between endpoints offering the same model, so check one endpoint satisfies all of your requirements together.
2. Filter by your use case
Models with chat and image input
Models with tools and streaming on one endpoint
Reasoning models available with Planck credits
Models available through a specific provider
parameterContract.
3. Call the selected model
The request format does not determine the provider. You can use an OpenAI-compatible client to call supported Claude, Gemini, Qwen, and other models through Planck.- cURL
- Python
- TypeScript
- Anthropic SDK
groq/qwen/qwen3.8-27b. Leave the prefix off to let Planck select an accessible endpoint.
4. Read the response
An OpenAI-compatible non-streaming response has this shape:
Extract only the assistant text with
jq:
choices[0] contains text for every operation. Tool-calling responses can contain tool_calls, Anthropic-compatible responses contain typed content blocks, and streaming responses arrive as a sequence of deltas.
5. Choose the next pattern
Common mistakes
- Sending a Planck key to a provider URL instead of
https://api.inquantum.ai. - Putting the API key in client-side code.
- Assuming a model-level capability means every provider endpoint supports it.
- Treating the model’s maximum output as a default. OpenAI-compatible output limits are optional; Anthropic Messages requires
max_tokens. - Parsing every response as plain text without checking
finish_reason, tool calls, reasoning fields, or stream events.