Skip to main content

​
Two packages, two models

The model follows the package: a GPT key can only call gpt-5.6-sol, an Astra key can only call gpt-astra. Calling across packages returns “No available channel for model …”. To use both, buy two codes and configure one key per app.
Model names must match exactly, case-sensitive. gpt-5.6-Sol, gpt5.6-sol, GPT-astra are all wrong. Copy from the table.

​
Shared capabilities

  • Chat Completions and Responses API, with streaming, tool calling and JSON mode.
  • Vision: send screenshots of errors, charts, images with text. See cURL / Python.
  • Reasoning: both are reasoning models. You may set reasoning_effort (low, medium, high) in the request; if you do not, the gateway uses a high level for consistent quality. Reasoning tokens are reported in usage.completion_tokens_details.reasoning_tokens and count against quota like output tokens.

​
How to choose

gpt-5.6-sol handles most coding work. For very hard tasks, deep reasoning or very long context, gpt-astra.

​
List the models your key can call

The result lists exactly the models this key is allowed to use. Anything not listed cannot be called with it.

​
Quota and rate

  • Quota is charged by tokens actually used (input + output + reasoning), exactly the usage returned.
  • Each key has a per-minute request limit set by its package; exceeding it returns 429, wait for the next minute. Add a delay between calls in batch scripts.
  • Remaining quota, expiry date and allowed models: gpt.teamsoclo.site/check.