default group, and you call them through Chat Completions or Responses by setting model to the model ID.
- Published: September 24, 2026
- Last verified: September 24, 2026
- Status: Active. All three models are available in the
defaulttoken group.
Key facts
Pricing
These rates come from LaoZhang API’s public pricing as of September 24, 2026, in US dollars per 1M tokens. They match the Standard rates on OpenAI’s pricing page. Standard requests (up to 272K input tokens per request):
Long-context requests (more than 272K input tokens per request):
Once a request has more than 272K input tokens, the whole request is billed at the long-context rates. For current rates, see the model and pricing catalog and the console pricing page.
Choose a model
OpenAI suggests weighing the reasoning your task needs against latency and cost:gpt-6-astra: OpenAI’s most capable model, aimed at the hardest end-to-end work such as complex reasoning, coding, research, and document creation. It has the highest rates of the three.gpt-6-sol: built for complex coding and agentic workflows, and suited to demanding tasks that need strong reasoning.gpt-6-luna: the model OpenAI describes as its most efficient, for focused, repeatable tasks at high volume. It has the lowest rates of the three.
Who is affected
- Affected: projects that call text models through LaoZhang API’s OpenAI-compatible endpoint. An API key in the
defaultgroup with the Usage first or Usage-based billing mode can call GPT-6, so you can start testing by changingmodelto a GPT-6 ID. - Not affected: existing models. GPT-5.6, GPT-5.4, and other models remain available, and current integrations need no changes.
Call GPT-6
Create an API key in Token management in thedefault group, with its billing mode set to Usage first (按量优先, recommended) or Usage-based (按量计费). Then export the key in your terminal:
gpt-6-sol with Chat Completions. For Python, run python -m pip install openai first.
- cURL
- Python
choices[0].message.content, which the Python example prints. To use gpt-6-astra or gpt-6-luna, change only model. The Python example turns off automatic retries so that your application decides when to send a request again. Call logs show the tokens and the charge for each request.
To use the Responses API, send input to POST /v1/responses:
- cURL
- Python
response.output_text joins the reply text. In the raw JSON, the text is in content[].text of the output item whose type is message.
Check your request parameters before you switch
All three GPT-6 models are reasoning models. OpenAI’s Using GPT-6 guide lists the parameters to check when you move to GPT-6. These rules apply to Chat Completions requests:- Reasoning effort (
reasoning_effort):gpt-6-solandgpt-6-lunaacceptnone,low,medium(the default),high,xhigh, andmax.gpt-6-astradoes not acceptnone; uselowinstead.- If your requests use
minimal, switch tolowfor any of the three models and compare the results.
- Sampling parameters: unless reasoning effort is
none, removetemperature,top_p,logprobs, andtop_logprobsfrom the request. Becausegpt-6-astrahas nononesetting, never send these parameters to it. - Tool calling:
- Tool calling with
gpt-6-astrarequires the Responses API. gpt-6-solandgpt-6-lunasupport function calling in Chat Completions only whenreasoning_effortisnone.- To use tools with
gpt-6-astra, or reasoning together with function calling on Sol or Luna, send the request to LaoZhang API’s Responses endpoint (POST /v1/responses).
- Tool calling with
Frequently asked questions
Can I call GPT-6 through the Responses API?
Yes. LaoZhang API supports OpenAI’s Responses API: set the base URL tohttps://api.laozhang.ai/v1 and call client.responses.create as in OpenAI’s GPT-6 guide; see the examples above. Tool calling with gpt-6-astra requires the Responses API, while plain conversations work with either endpoint.
How are requests with more than 272K input tokens billed?
The whole request is billed at the long-context rates, not just the tokens above 272K. Input, output, cache reads, and cache writes all use the long-context table above. Compared with the standard rates, input and cache rates are doubled and output costs 1.5 times as much, the same rule OpenAI applies. To estimate cost, use a request’s full input token count to decide which tier applies.I already use GPT-5.6. Do I need to switch?
No.gpt-5.6-luna, gpt-5.6-terra, and gpt-5.6-sol remain in the pricing configuration, and existing integrations keep working.
If you plan to switch, compare both generations on representative requests for quality, latency, and cost, then check reasoning effort, sampling parameters, and tool calling as described above. The model and pricing catalog lists current rates for both generations.
What if the model doesn’t exist or isn’t allowed?
Check the model ID, token group, and endpoint, in this order:- The model ID is copied exactly (
gpt-6-astra,gpt-6-sol, orgpt-6-luna). - Your API key is in the
defaultgroup with the Usage first or Usage-based billing mode, because a Per-call key can call only per-call models. - The request goes to
POST /v1/chat/completionsorPOST /v1/responses.
How do I check what my GPT-6 requests cost?
Multiply a request’s token counts by the current rates and compare the result with the actual charge:- Confirm the current rates on the console pricing page.
- Pick a recent request in call logs and work out its expected charge from its token counts. Use the long-context rates if the request had more than 272K input tokens.
- Compare the result with the actual charge.
Sources and related links
OpenAI
- OpenAI API changelog: the September 3, 2026 entry for GPT-6 Astra and the September 22, 2026 entry for GPT-6 Sol and Luna
- OpenAI API pricing: standard and long-context rates for all three models
- Model pages for GPT-6 Astra, GPT-6 Sol, and GPT-6 Luna: context window, maximum output, reasoning effort, and pricing rules
- Using GPT-6: how the three models differ, and the parameter and tool-calling rules for switching
LaoZhang API
LaoZhang API rates, token groups, and endpoints come from the public pricing configuration as of September 24, 2026:- Model and pricing catalog: current rates, including long-context tiers
- Console pricing page: the rates that apply to your account
- Token management: create an API key and set its group and billing mode
- Call logs: token counts and the actual charge for each request