Skip to main content
LLM.kiwi is currently free and does not require a credit card. Free access is still subject to capacity, rate limits, and fair use. See Limits and pricing.
No. Your application sends HTTPS requests to the hosted LLM.kiwi API. You do not need a GPU, Docker, or a model server.
Sign in at llm.kiwi/login, open the dashboard, and create a key. Copy it when shown and store it safely.
Use https://api.llm.kiwi/v1. In an SDK, set this as the base URL. In direct HTTP, append an endpoint such as /chat/completions.
Start with auto for general use. Test hrllm when Croatian-language quality is your main requirement. Query GET /v1/models for current availability.
LLM.kiwi supports the OpenAI-compatible chat completions patterns documented here. Set the custom base URL in a compatible client. Features not listed in the LLM.kiwi API reference should not be assumed to work.
Your frontend can use an AI feature, but it should call your backend. The backend holds the API key and calls LLM.kiwi. Never embed a private key in code sent to the browser.
Use your own backend for the same reason as a browser app: secrets packaged with a mobile application can be extracted.
No. Include the relevant system, user, and assistant messages with each request. Your application decides what history to store and resend.
Language-model output can vary because of sampling and model routing. If consistency matters, make instructions precise, test model parameters supported by the endpoint, and validate the output.
You can request JSON, but your code must still parse and validate it. Define a schema, reject invalid fields, and provide a fallback when parsing fails.
Revoke it immediately in the dashboard, create a replacement, update the application’s secret, and remove the exposed value from code and logs. Deleting only the latest Git commit may not remove it from history.
The key is missing, malformed, invalid, or revoked. Verify Authorization: Bearer sk_kiwi_... and confirm that the environment variable is available to the running process.
A request or capacity limit was reached. Wait, reduce request frequency or concurrency, and retry a limited number of times with exponential backoff.
Evaluate it against your reliability, privacy, capacity, and support requirements. At minimum, keep keys server-side, set timeouts, handle failures, validate model output, and provide a fallback. See Best practices.
Follow Troubleshooting first. If the problem remains, email support@llm.kiwi with the status code, approximate time, SDK version, and a minimal redacted request. Never send a full API key.
Last modified on July 28, 2026