GPT-6 Luna on Lazu: text generation or Decisions?
GPT-6 Luna’s text API is available through Lazu. Current stable-lane base pricing is $0.10 per million input tokens and $0.50 per million output tokens. Use the text endpoint for prose, summaries or rewrites; evaluate Decisions separately for typed judgments.
Start with a task you can verify #
Summarizing a passage is a text-generation task; checking a predefined condition can be a typed decision. The two endpoints have different response formats, limits and prices despite sharing the Luna name.
Pricing and boundaries #
This is a snapshot of Lazu’s stable-lane base rates on October 10, 2026, before any account-specific discount. Consult the catalog for subsequent changes.
| Dimension | USD / million tokens |
|---|---|
| Input | $0.1 |
| Output | $0.5 |
| Cache read | $0.01 |
| Cache write, 5 minutes | $0.125 |
| Cache write, 1 hour | $0.125 |
Lazu’s current text price has no configured context tier, while OpenAI’s price list includes long-context rates. This short-text example does not validate long-context economics. Use bounded retries and a fallback path for critical tasks.
The model card below reads the live catalog:
gpt-6-lunaOpenAI · 1.05M · Stable $0.10 / $0.50Model page →A minimal request #
Create a key with a model restriction and spending cap, then set LAZU_API_KEY in your local environment. Keep the key out of source code. Query /api/models/catalog with that key to check permissions and supported endpoints before integration.
curl --fail-with-body https://api.lazu.ai/v1/chat/completions \
-H "Authorization: Bearer $LAZU_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"gpt-6-luna","max_tokens":128,"messages":[{"role":"user","content":"Reply with only OK."}]}'
Verify the result before increasing traffic #
On October 10, 2026, a restricted key completed this short-text request through the public API with HTTP 200 and a valid response. This verifies one basic request path, not sustained concurrency, long-context behavior or task quality.
Save X-Lazu-Request-Id from the response headers. Inspect the input, output, cache usage and charge in Usage & Logs, or query GET /api/usage/requests/{request_id} with the same key. Distinguish quota and budget errors from upstream rate limits; retry only when appropriate and with a limit.
See the Lazu catalog, pricing and lanes, and model reference.