Ling-3.1-flash API

What is Ling-3.1-flash?

Use the public identifier di-inclusionailing-31-flash-3ec2a3359f for Ling-3.1-flash in ServerNet. The gateway uses this identifier to select the configured route; the developer is inclusionAI.

Where to use Ling-3.1-flash

• Add Ling-3.1-flash to a support assistant that receives the relevant conversation as text.
• Test Ling-3.1-flash on summaries and extraction using your own documents, with a small output limit first.
• Compare answer quality, total token usage and cost per completed task before choosing Ling-3.1-flash for production.

Build your integration

Send system and user messages, set max_tokens and store X-Request-Id with your usage record. Stream only when this route supports it. Function calls describe actions for your application to run; the gateway does not execute your tools.

Inputs and service limits

The current chat route accepts text only and one completion per request. Images, audio and hosted paid tools are not enabled by the source model’s capabilities. The configured context and output limits may be below the developer’s maximum. Test language quality on your own dataset.

A request cost example

For 1,000 input tokens and 500 output tokens, without a cache discount. This is a catalogue estimate, not a fixed request fee. Reported consumption and the price frozen for your request determine the usage amount.

Estimated usage, Toman

209

Connect to Ling-3.1-flash API

Enable ai:chat on your key and ai:models:read to check availability. Set SERVERNET_API_KEY in your server environment. Change the idempotency key for each new request; keep it unchanged only for an identical retry.

curl https://servernet.cloud/v1/chat/completions \
  -H "Authorization: Bearer $SERVERNET_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: CHANGE_FOR_EACH_NEW_REQUEST' \
  -d '{
    "model": "di-inclusionailing-31-flash-3ec2a3359f",
    "messages": [
        {
            "role": "user",
            "content": "Hello"
        }
    ],
    "max_tokens": 128
}'

Use the same Idempotency-Key when retrying an identical request. Successful responses are replayed without a second charge for 24 hours. Do not automatically retry when x-should-retry:false is present. The key is shown once. Store it in a server environment variable. Keep it out of browser code, GitHub and logs.

Compare models for the same task