EVREN

EVREN is the LLM inference service opened by the SAYZEK programme of Turkey's Presidency of Defence Industries, hosted in Turkey. The EVREN rows on LLMTR run on your own EVREN API key: the request is made with your credential, LLMTR only routes it, and LLMTR charges nothing for these requests.

Model	Context	Price ($/1M)
evren/gemma-4-31b	256,000	0
evren/deepseek-v4-flash-tr	1,000,000	0
evren/qwen3.8-flash-next	256,000	0
evren/glm-5.3-fp8	512,000	0
evren/qwen3-vl-30b	256,000	0

Register your key first

Unlike every other model on LLMTR, these rows do not answer until you have stored an EVREN key.

1. Create an API key in the EVREN console and accept EVREN's terms of use.
2. Paste it into Settings → Your own provider keys on LLMTR.
3. Call the model as usual. You do not send the EVREN key in your request; only your LLMTR key travels.

Once saved, a key is never shown again — only its last four characters. If you lose it, create a new one in the EVREN console and replace it in Settings.

curl "$LLMTR_BASE_URL/v1/chat/completions" \
  -H "Authorization: Bearer llmtr-your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "evren/glm-5.3-fp8",
    "messages": [
      { "role": "user", "content": "Summarise the termination clauses in this contract." }
    ],
    "max_tokens": 4096
  }'

Keeping your key safe

A stored key is held under strong encryption and is used for one thing only: sending your own request. It is never shown again, not even to you — only its last four characters. The moment you remove it, it can no longer be used.

Error responses

On EVREN rows the provider's answer is relayed to you directly. The key and the account are yours, so you are the only person who can act on either.

Situation	HTTP	error.type
No key stored	403	provider_credential_required
EVREN rejected your key	403	provider_credential_rejected
Your EVREN account did not serve the request	403	provider_account_limited
EVREN rate limited the request	429	provider_rate_limited
EVREN refused the request for another reason (4xx)	the provider's code	provider_upstream_error
EVREN failed on its side (5xx)	502	provider_upstream_error

error.details.upstreamStatus always carries the original status EVREN returned, even where the HTTP status is 502. The distinction matters because clients decide retries from the HTTP status: 4xx codes are preserved as they are, 5xx responses are collapsed into 502. The provider's error text is not relayed; only the status and which provider answered.

Things worth knowing

• Streaming on these rows is not real streaming: the answer is delivered in chunks after it completes.
• Tool calling, JSON mode and reasoning controls are not offered on these rows.
• Context windows and parameter counts are taken from EVREN's published model table.
• No separate output ceiling is published. The limit shown on the model card is the context window; if EVREN's own output limit is lower, it refuses the request and its answer is relayed to you. If you expect long outputs, raise max_tokens gradually.
• The service being free is EVREN's decision. It is free until 1 November 2026; LLMTR adds no charge of its own. The platform margin on credit top-ups is unaffected.