Seed 2.1 Turbo on Lazu: one key, a new model option
Seed 2.1 Turbo is available on Lazu’s stable lane as seed-2.1-turbo. It adds a Seed option to an existing application while keeping API keys and request receipts in one place.
Start with a task you can verify #
Try it on a small set of rewrites, summaries or questions with known expected results. Compare quality and total cost before increasing traffic. “Turbo” is a model name, not a latency or capacity promise.
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.5 |
| Output | $2.5 |
| Cache read | $0.1 |
The catalog lists a 256,000-token context window with no additional context tier in the current Lazu sell price. Cached-input pricing applies only to reported cache hits. This launch covers the text API; it does not announce Seedance or Seedream availability.
The model card below reads the live catalog:
seed-2.1-turboByteDance · Seed · 256k · Stable $0.50 / $2.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":"seed-2.1-turbo","max_tokens":128,"messages":[{"role":"user","content":"Reply with only OK."}],"thinking":{"type":"disabled"}}'
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.