Kilo AI Gateway
22 model routes currently listed at zero price.
https://api.kilo.ai/api/gatewayModels mentioned
kilo-auto/freepoolside/laguna-s-2.1:freenvidia/nemotron-3-ultra-550b-a55b:freedots-studio/dots-3-note-preview:freenex-agi/nex-n2.5-pro:freeinclusionai/ling-3.0-flash-vl:freenex-agi/nex-n2.5-mini:freeinclusionai/ling-3.0-flash-sante:freeinclusionai/ling-3.0-flash-fin:freeliquid/lfm-2.5-2.6b:freenvidia/nemotron-3.5-lightning:freethinkingmachines/inkling-small:freepoolside/laguna-xs-2.1:freecohere/north-mini-code:freenvidia/nemotron-3.5-content-safety:freenvidia/nemotron-3-nano-omni-30b-a3b-reasoning:freenvidia/nemotron-3-super-120b-a12b:freeqwen/qwen3.8-27b:freedeepseek/deepseek-v4-flash-0731:freez-ai/glm-5.2:freestepfun/step-3.7-flash:freeopenrouter/freeEquivalent paid value
How this was valued: The published allowance or a defensible paid comparison is not precise enough to calculate.
The request-rate ceiling has no bounded request size and the rotating aliases have no stable paid counterpart.
Limits and terms
- Requests Per Hour Per Ip
- 200
- Price USD
- 0
What happens to your prompts?
The terms grant broad perpetual improvement rights and some routed models can require training permission.
- Plan Scope
- Kilo Gateway and Kilo coding products; free and paid plans and the selected OpenRouter or downstream model route differ.
- Prompt Retention
- Kilo's terms grant a perpetual, irrevocable, sublicensable license to use Customer Data for service delivery and improvement. Paid plans advertise no-retention support, but that is not a default commitment for the free plan.
- Response Retention
- Outputs are Customer Data under the same broad terms; paid plans can support no-retention routing.
- Ordinary Logging
- Kilo collects account and technical data and states analytics telemetry excludes prompt or conversation content. Audit and usage logs may be available for governed plans.
- Model Training
- A user can decline to license data to an AI model for training, but then some models may be unavailable. Downstream model rules remain route-specific.
- Product Improvement
- The Customer Data license expressly permits Kilo to improve its service and other products, including development, diagnostics, and corrective work.
- Human Or Operator Access
- The terms authorize Kilo processing for development and diagnostics. OpenRouter and the selected downstream provider process prompt and conversation content for inference.
- Subprocessors And Routing
- Prompts are routed through OpenRouter to the selected provider, including Anthropic, OpenAI, Google, xAI, Mistral, Meta, and others. Their terms and route controls also apply.
- Deletion Controls
- Users may delete the account from their profile or request deletion. Paid-plan no-retention support and provider-routing controls require configuration and do not erase previously retained data automatically.
- Caveat
- The free plan does not receive the paid no-retention statement, and Kilo's terms contain a broad perpetual data license. Model access may depend on accepting downstream training rights.
Governing documents
- Terms Of Service
- https://kilo.ai/terms
- Privacy Policy
- https://kilo.ai/privacy
Eligibility
- Account Required
- No
- Payment Method Required
- No
Primary sources
Before you build with Kilo AI Gateway
Read the classification narrowly
This record has current first-party evidence for some zero-cost hosted inference. The label describes the bounded offer supported by evidence on 2026-09-19; it does not guarantee permanence, production suitability, uptime, latency, model quality, or access from every region.
Resolve the live model route
This snapshot records 22 model IDs. Match the exact ID against the provider's live catalog before using it in code; zero-price routes and aliases can rotate while an older documentation page remains online. The recorded base endpoint is https://api.kilo.ai/api/gateway, but the provider's current API reference remains authoritative for paths, authentication, and request shape.
Confirm account and billing boundaries
The recorded offer does not require an account, but published limits and abuse controls can still change without notice. The reviewed evidence explicitly says no payment card is required. Re-check the signup flow because eligibility and billing controls can change after the snapshot. The equivalent paid value shown here prices a documented allowance where possible; it is not cash, guaranteed savings, or protection from overage.
Re-read the prompt policy for your plan
This record classifies the reviewed handling as “Not private”: The terms grant broad perpetual improvement rights and some routed models can require training permission. Provider policies can distinguish free, paid, enterprise, opted-in, and feature-specific traffic, so verify the governing terms for the exact account and route that will receive your data.
Follow the evidence, then re-check it
The record links 9 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest governing document or live catalog when sources disagree, and submit a correction when a provider changes a material term.
Match the quota to the workload shape
Translate the published allowance into the traffic pattern you actually expect instead of comparing headline totals alone. A daily token pool can look generous while a low requests-per-minute or concurrency ceiling blocks interactive bursts; a high request limit can still fail a long-context job when input, output, or per-request tokens are capped. Separate prompt tokens from generated tokens, include retries and tool calls, and test the largest realistic payload. If the provider documents more than one limit window, the tightest window at your peak load is the practical ceiling. Research, experimental, and community access can also carry eligibility or fair-use constraints that cannot be modeled as a simple number.
Plan fallback without changing the rules
A fallback should preserve more than API syntax. Confirm that the substitute route supports the required modality, context length, streaming behavior, structured output, tools, and safety controls, then compare its prompt-retention and training terms. An OpenAI-compatible request shape does not make providers operationally or contractually equivalent. Decide which errors may trigger a retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. If deterministic output matters, record the model revision and sampling settings; rotating aliases and free-model pools can change behavior even when the endpoint remains available.
Monitor the offer as a dependency
Capture the model ID, response model field, rate-limit headers, usage fields, latency, HTTP status, and any provider request identifier for each test. Watch for authorization failures, quota exhaustion, catalog removal, policy revisions, and dashboard balance changes as separate failure modes. Re-check the provider’s live catalog and governing pages on a schedule proportionate to the workload’s importance, and keep the dated sources that supported your decision. Free capacity is especially suitable for prototypes, evaluations, fallbacks, and bounded workloads when the application can tolerate change; a production dependency still needs observability, an exit path, and an owner responsible for re-verification.
Test one complete request before scaling
Start with the smallest permitted request using the exact credential, model ID, endpoint, and account type you intend to deploy. Record the HTTP status, response headers, usage fields, latency, and any dashboard balance change. Then exercise the failure path: an invalid model, an exhausted quota, or a rate-limit response should fail clearly without silently switching to a paid route. If the provider supports streaming or tool calls, validate those features separately because a free model can expose a narrower capability set than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and avoid sending sensitive data until the observed route matches the reviewed data agreement.