Qwen3.8 27B API

Pricing

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

Good fit for code generation

• Code completion, generation, and refactoring inside an IDE or CI job
• Test generation and bug localisation against a repository context
• Migration work where the model rewrites whole files
• Code review assistants that must return structured findings

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 code generation 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-27b",
    "messages": [
      {"role": "system", "content": "You are a helpful assistant."},
      {"role": "user", "content": "Refactor this module for readability and explain the change."}
    ]
  }'

Why code generation costs what it does

Code models restate the problem before answering, which inflates output tokens on every call, and output is priced several times higher than input. Set max_tokens to what the diff actually needs, and pass only the files relevant to the task rather than the whole repository.

Model Specifications

Qwen3.8 27B API FAQ

Can Qwen3.8 27B edit files directly?

The API returns text. Your client applies it. Use function calling if you want the model to request file writes through your own tool layer.

What context window should I plan for?

Check the specification table above. For repository-scale work, prefer models with the largest window and keep only the relevant files in context.

How do I keep code output deterministic?

Lower the temperature, pin the model id, and keep the instruction block stable so the prefix stays cacheable.