GPT-6 Sol on Lazu: validate the stable lane first

Model launch · 2026-10-10 GPT-6 Sol on Lazu gpt-6-solStable $2.00 / $10.00 · Discount $0.36 / $1.80 Lazu

GPT-6 Sol is available through Lazu’s OpenAI-compatible API as gpt-6-sol. Stable-lane base pricing is $2 per million input tokens and $10 per million output tokens. Start by verifying one small task in an existing SDK integration.

Start with a task you can verify #

Keep the original input and acceptance checks, then inspect the response, finish reason and usage. Changing a model name does not make every parameter compatible. Read the key-scoped catalog before choosing an endpoint or optional parameter.

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 $2
Output $10
Cache read $0.2
Cache write, 5 minutes $2.5
Cache write, 1 hour $2.5

The verified example uses the stable lane. Select that lane when creating a key to use the prices and request path in this guide. Discount lanes have their own prices and status; check them separately before switching.

The model card below reads the live catalog:

gpt-6-solOpenAI · 1.05M · Stable $2.00 / $10.00 · Discount $0.36 / $1.80Model 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-sol","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.

Related
2026-10-21GPT-6.1 Sol vs GPT-6 Sol: same price, cache reads at half 2026-09-30LLM API pricing comparison: Claude, GPT, Gemini, DeepSeek 2026-10-28BAAI/bge-m3 embeddings API: 100+ languages, $0.02 per 1M

Try it with a key

Start free