Free Qwen API: Qwen3.8 27B on LLMTR until 2 November 2026

Short answer: yes, until 2 November 2026, 00:00 (TRT)

LLMTR (llmtr.com) is a gateway that gives access to language models hosted in Türkiye and at global providers through one OpenAI-compatible API. If you are looking for a free Qwen API, you can call Qwen3.8 27B there for free with the model id heabsy/qwen3.8-27b-heabsy-free at https://llmtr.com/v1. Until 2 November 2026, 00:00 (TRT), the price is $0.00 per 1M input tokens and $0.00 per 1M output tokens, and no credit is deducted for this model.

The catalog shows Heabsy as the provider. Free Qwen 3.8 use is open until that date with a daily limit per account. The one extra step before the first request is the Heabsy data-transfer consent in Settings. After the end date you can keep using the same model under the metered id heabsy/qwen3.8-27b-heabsy.

How do you use a free Qwen API?

Create an LLMTR API key, grant the Heabsy consent and send your request to https://llmtr.com/v1/chat/completions with heabsy/qwen3.8-27b-heabsy-free as the model. You do not need a separate Qwen API key: your LLMTR key goes in the Authorization: Bearer header. The curl request below asks the model to explain, in three short points, what an HTTP 429 response with a Retry-After header means for an API client.

In an existing OpenAI client, three things change: base_url becomes https://llmtr.com/v1, api_key takes your LLMTR key, and the model string becomes heabsy/qwen3.8-27b-heabsy-free. This model is called only through the OpenAI-compatible /v1/chat/completions endpoint; /v1/responses is not available for it. The example sets max_tokens to 2048; reasoning tokens come out of the same budget, so do not pick a very small value.

curl request to the free Qwen3.8 27B with max_tokens set to 2048, asking what an HTTP 429 response means.

curl https://llmtr.com/v1/chat/completions \
  -H "Authorization: Bearer $LLMTR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "heabsy/qwen3.8-27b-heabsy-free",
    "max_tokens": 2048,
    "messages": [
      {"role": "user", "content": "In three short points, explain what an HTTP 429 response with a Retry-After header means for an API client."}
    ]
  }'

Before the first request: the Heabsy data-transfer consent

Heabsy models cannot be called until your account grants the Heabsy data-transfer consent. Without it, every request returns HTTP 403 with the error type provider_consent_required, and retrying does not help until the consent is given. You grant it on llmtr.com in the Data-transfer consents card under Dashboard > Settings, and you can withdraw it from the same place.

Consent is per provider: a consent given for another provider does not cover the Heabsy models. It is account-level, so it applies to every API key on the account. The content of your request is transferred to Heabsy to produce the response; account details such as your name and e-mail are not transferred. LLMTR's usage records do not contain request content.

According to Heabsy, Qwen3.8 27B runs in EU/EEA data centres; prompts and completions are not stored (zero data retention) and are never used for training. For these points Heabsy refers to its privacy policy and data processing agreement (DPA); the binding terms are the text of those documents.

• Heabsy, privacy policy (link provided by Heabsy) · 2026-10-13
• Heabsy, data processing agreement (DPA) (link provided by Heabsy) · 2026-10-13

What the model accepts: limits and reasoning

heabsy/qwen3.8-27b-heabsy-free has a context window of 262,144 tokens. max_tokens can go up to 32,768 for the response; a larger value is refused with HTTP 400 and the error type invalid_request. The model card lists image input and tool/function calling.

The model reasons by default. Reasoning tokens count toward max_tokens and are output tokens. If a response ends with finish_reason "length", raise max_tokens and send the request again. reasoning_effort is not supported on this model: a request that sends it is refused with HTTP 400 invalid_request, so if your code sends that field, remove it for this model.

stream: true is accepted, but for now the answer is delivered in chunks after it completes, so the first chunk arrives when the response is finished. For long answers, size your client timeout for the whole response, not for a quick first chunk.

Daily limit, error codes and the 2 November 2026 end date

Free use is limited per account per day. When a limit is reached, the API returns HTTP 429 with a Retry-After header; your client should wait for the time in that header and then send the request again. Do not treat 429 as final, and do not retry in a tight loop. Waiting does not fix 403 provider_consent_required or 400 invalid_request: fix the consent or the request body first. On an account that has not topped up yet, a request can return HTTP 402 after some use, with details.reason set to account_verification_required. Automated-use protection is asking for a one-time account verification: top up once from Dashboard > Billing and retry after a minute; the model is not charged to your balance.

The free period ends on 2 November 2026, 00:00 (TRT), which is Europe/Istanbul time, UTC+3. From that moment, requests to heabsy/qwen3.8-27b-heabsy-free return HTTP 410 with the error type model_retired, and the error names the metered id heabsy/qwen3.8-27b-heabsy. The model page stays online. A 410 is final, and retrying does not help.

To keep using the same model, change the model id in your code to heabsy/qwen3.8-27b-heabsy. That id is billed from prepaid credit per 1M tokens: $0.40 input, $0.05 cached input and $3.00 output.

Getting started with the Python OpenAI SDK: account, key, consent and first request

Step 1: create an account at llmtr.com. Step 2: create an API key under Dashboard > API Keys. The raw key is shown once, so store it right away in the LLMTR_API_KEY environment variable. Step 3: grant the Heabsy consent in the Data-transfer consents card under Dashboard > Settings.

Step 4: send the first request to https://llmtr.com/v1 with any OpenAI-compatible SDK. The Python example below sends a request with the OpenAI SDK, prints the Retry-After header on a 429 and reports when a response ends with finish_reason "length". The llmtr-your_key value is only a placeholder; in real code, read the key from the LLMTR_API_KEY environment variable.

The same key works for every model in the catalog, and switching models means changing the model string. Other models are billed from prepaid credit at their catalog prices; this one deducts nothing during the free period.

Python example with the OpenAI SDK that calls the free Qwen3.8 27B and handles the Retry-After header of a 429 and finish_reason length.

from openai import OpenAI, RateLimitError

client = OpenAI(base_url="https://llmtr.com/v1", api_key="llmtr-your_key")

try:
    response = client.chat.completions.create(
        model="heabsy/qwen3.8-27b-heabsy-free",
        max_tokens=2048,
        messages=[
            {"role": "system", "content": "You are a concise technical assistant."},
            {"role": "user", "content": "Write a short checklist for reviewing a pull request."},
        ],
    )
except RateLimitError as err:
    # HTTP 429: wait for the time in the Retry-After header, then send the request again
    print("Limit reached, Retry-After:", err.response.headers.get("retry-after"))
    raise

choice = response.choices[0]
if choice.finish_reason == "length":
    # Reasoning tokens count toward max_tokens: raise it and send the request again
    print("The answer stopped at max_tokens")
print(choice.message.content)

Call Qwen3.8 27B for free through LLMTR

Create an account, create an API key, grant the Heabsy consent and send the first request to heabsy/qwen3.8-27b-heabsy-free before 2 November 2026, 00:00 (TRT).

1. Account and API key. Create an account at llmtr.com and create a key under Dashboard > API Keys. The raw key is shown once; store it as the LLMTR_API_KEY environment variable.
2. Heabsy consent. Grant the Heabsy consent in the Data-transfer consents card under Dashboard > Settings. Without it, every request returns HTTP 403 provider_consent_required.
3. First request. Send the first request to https://llmtr.com/v1 with any OpenAI-compatible SDK, changing base_url and api_key and using the model heabsy/qwen3.8-27b-heabsy-free.

Frequently asked questions

Is the Qwen API really free on LLMTR?

Yes. heabsy/qwen3.8-27b-heabsy-free costs $0.00 per 1M input and output tokens until 2 November 2026, 00:00 (TRT), and no credit is deducted. Use is limited per account per day, and the Heabsy data-transfer consent is needed before the first request.

What happens to the free Qwen API after 2 November 2026?

Requests to heabsy/qwen3.8-27b-heabsy-free return HTTP 410 with the error type model_retired, and the error names the metered id heabsy/qwen3.8-27b-heabsy. To keep using the same model, change the model id to that metered id.

Why does the free Qwen API return 403 provider_consent_required?

Your account has not granted the Heabsy data-transfer consent yet. Grant it in the Data-transfer consents card under Dashboard > Settings; you can withdraw it from the same place at any time.

Related posts

• Free Qwen in Europe: where requests go and what is stored
• Free Qwen for AI agents: tool calling with Qwen3.8 27B
• qwen3.6-27b-free retired: managing the daily quota on qwen3.8-27b-free

• Qwen3.8 27B (Free) model
• Heabsy documentation
• Chat Completions guide
• Errors documentation