Claude Opus 5.5 on Lazu: reconcile a complete task
Claude Opus 5.5 is available through Lazu at $4 per million input tokens and $20 per million output tokens on the stable lane. Add claude-opus-5-5 to an existing Anthropic SDK integration or a client with a configurable API endpoint.
Start with a task you can verify #
For a complex code change or a longer task, compare completion quality, the number of turns and the cost of all requests. Include repeated input and cache usage rather than comparing a single answer in isolation.
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 | $4 |
| Output | $20 |
| Cache read | $0.2 |
| Cache write, 5 minutes | $5 |
| Cache write, 1 hour | $8 |
Stable-lane cache reads currently cost $0.20 per million tokens; five-minute writes cost $5 and one-hour writes $8. Keep real keys out of examples. Validate tool calls and continuations before migrating a coding-agent workflow.
The model card below reads the live catalog:
claude-opus-5-5Anthropic · 1M · Stable $4.00 / $20.00 · Discount $1.72 / $8.60Model 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/messages \
-H "Authorization: Bearer $LAZU_API_KEY" \
-H "Content-Type: application/json" \
-H "anthropic-version: 2023-06-01" \
-d '{"model":"claude-opus-5-5","max_tokens":64,"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.