Your first request.

From a workspace to a working request, using the tools you already know.

Create your workspace

Create an account and verify your email address. Add credits, then create an API key with a spending limit in your dashboard.

Install the SDK

Make it yours

Set RYNLER_API_KEY in your server environment and confirm the example model is available in the current catalogue. Generate a new idempotency identifier for each request.

import os
import uuid
from openai import OpenAI

client = OpenAI(
    base_url="https://api.rynler.com/v1",
    api_key=os.environ["RYNLER_API_KEY"]
)

response = client.chat.completions.create(
    model="xiaomi/mimo-v2.6-flash",
    messages=[{"role": "user", "content": "Hello, world."}],
    max_tokens=1024,
    extra_headers={"Idempotency-Key": str(uuid.uuid4())}
)
print(response.choices[0].message.content)

Authentication

Send your key using Authorization: Bearer RYNLER_API_KEY. Keys are shown once, stored as hashes and can be revoked immediately. Keep them on your server, never in a browser bundle or a public repository.

List currently available models with GET /v1/models. Your key must include the inference scope.

Making requests

POST /v1/chat/completions currently accepts a conservative text request limit of 8,192 tokens (input bound plus maximum output), even when a reference model has a larger native context. It supports text messages with system, user and assistant roles, temperature and a bounded max_tokens value. Supply an Idempotency-Key header containing 16–128 URL-safe characters.

When streaming is requested, the response uses SSE after the complete output and token usage have been validated. Native token-by-token streaming, tool calls and the Responses API are not supported. Image input requires an enabled vision model and supported user-message image parts. Check GET /v1/vision-capabilities before use.

Errors & retries

Security & data

Enable two-factor authentication in account settings. It is required for administrators. Browser sessions use HttpOnly cookies; account changes are protected against cross-site requests.

Rynler stores request metadata for usage and accounting, not the contents of your conversations. Inference services process prompts and outputs under their own data terms. Do not submit confidential or regulated data until those terms meet your requirements.