Qwen3.8 Flash API

Pricing

₹20/1M input · ₹60/1M output. Pay-as-you-go micro-metered billing. UPI and cards accepted with zero minimum commitment.

Why chat volume is predictable to budget

Chat workloads have short, stable output. That makes per-call cost easy to forecast: input tokens times the document size, output tokens times the reply length. The main leak is retries and regenerate buttons, which bill as fresh requests.

Model Specifications

OpenAI-Compatible Integration

Drop into existing OpenAI SDK code by changing the base URL to https://api.luminoai.co.in/v1. The request shape below is the chat and general purpose pattern.

curl https://api.luminoai.co.in/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $LUMINO_API_KEY" \
  -d '{
    "model": "qwen3-8-flash",
    "messages": [
      {"role": "system", "content": "You are a helpful assistant."},
      {"role": "user", "content": "Summarise this document in five bullet points."}
    ]
  }'

Good fit for chat and general purpose

• Chat assistants and customer-facing support drafting
• Summarisation, extraction, and classification at volume
• Style and tone rewriting for content pipelines
• Any high-volume task where cost per call is the binding constraint

Qwen3.8 Flash API FAQ

How much does Qwen3.8 Flash cost per call?

Multiply your input tokens by the input rate and your reply length by the output rate. Both rates are in the pricing table above.

Is Qwen3.8 Flash good enough for production support?

For drafting, summarising, and structured extraction, yes. Keep a human in the loop for anything that commits money or changes account state.

How do I control spend on a chat product?

Cap max_tokens, rate-limit the regenerate button, and cache a stable system prompt.