DeepSeek Flash on Lazu: cache and time-based pricing

Model launch · 2026-10-10 DeepSeek Flash on Lazu deepseek-flashStable $0.1875 / $0.75 Lazu

DeepSeek Flash is available through Lazu as deepseek-flash. Evaluate it alongside the models in your existing text workflow. Budgeting requires both cache usage and the time of the request.

Start with a task you can verify #

Keep a fixed task set and record input, output, cache reads and charges. A short visible answer does not necessarily mean little billed output: reported reasoning tokens can contribute to output usage.

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.1875
Output $0.75
Cache read $0.00375

Current Lazu base rates are $0.1875 input, $0.75 output and $0.00375 cached input per million tokens, doubled at 01:00–04:00 and 06:00–10:00 UTC. Lazu currently applies these windows daily; the official schedule excludes weekends and Chinese public holidays. Use Lazu’s catalog and receipt for your charge.

The model card below reads the live catalog:

deepseek-flashDeepSeek · 1M · Stable $0.1875 / $0.75Model 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":"deepseek-flash","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-21Claude Code on GPT and DeepSeek: how Lazu translates APIs 2026-10-28BAAI/bge-m3 embeddings API: 100+ languages, $0.02 per 1M 2026-10-10GPT-6 Sol on Lazu: validate the stable lane first

Try it with a key

Start free