5.6 Sol technical docs
Endpoint, auth header, parameters, prices, and tested request examples for GPT-5.6 Sol.
Endpoint and pricing
Thinking uses reasoning.effort. Pro adds reasoning.mode: "pro". Every tier keeps the same model id and the same fixed price: Luna 5 cauris, Terra 10 cauris, or Sol 20 cauris per request. Base and Thinking are available in API and Agent; Pro is API only. Imole does not impose a token ceiling.
A request without reasoning is Base/none. Low effort uses the same fixed price.
Omit reasoning, or use reasoning.effort: "none" | "low"Thinking selects standard reasoning with reasoning.effort at the same fixed model price.
reasoning.effort: "medium" | "high"Thinking Max selects the highest standard reasoning efforts at the same fixed model price.
reasoning.effort: "xhigh" | "max"Pro adds reasoning.mode set to "pro" without changing the fixed model price.
reasoning.mode: "pro" · effort: "medium" | "high"Pro Max combines Pro mode with the highest reasoning efforts at the same fixed model price.
reasoning.mode: "pro" · effort: "xhigh" | "max"Request headers
Bearer Imole API key.
Use application/json for JSON requests.
Request parameters
Use the page model id for Base, Thinking, and Pro. The model id never changes between tiers.
gpt-5.6-solString input or Responses input array.
Legacy chat-style array. The router converts it to Responses input.
System or developer instruction inserted ahead of the user task.
Optional native Responses output control. It is not required, and Imole does not impose a token or output ceiling.
Omit reasoning for Base/none. Thinking uses reasoning.effort. Pro adds reasoning.mode set to "pro" while keeping the same model id.
effort: none, low, medium, high, xhigh, max · mode: proSampling randomness when the model supports it.
Nucleus sampling control.
Return server-sent events when supported.
true, falseTool definitions for tool-enabled Responses calls.
Tool selection policy.
auto, none, requiredAllow multiple tool calls in one turn.
true, falseStructured text format controls for Responses.
Compatibility field for JSON-style output requests.
Optional request metadata.
Tested request examples
Base, Thinking, and Pro use the same model id. Only the reasoning object changes.
curl -X POST "https://api.imole.app/v1/responses" \
-H "Authorization: Bearer $IMOLE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-5.6-sol",
"input": "Write a concise product update announcing a faster API workflow.",
"instructions": "Answer in three short bullet points."
}'curl -X POST "https://api.imole.app/v1/responses" \
-H "Authorization: Bearer $IMOLE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-5.6-sol",
"input": "Compare exponential backoff and fixed-delay retries for an API client, then recommend one.",
"reasoning": {
"effort": "medium"
}
}'curl -X POST "https://api.imole.app/v1/responses" \
-H "Authorization: Bearer $IMOLE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-5.6-sol",
"input": "Review a migration from a monolith to event-driven services and identify the most important operational trade-offs.",
"reasoning": {
"mode": "pro",
"effort": "medium"
}
}'