22 of the 45 AI providers we track have a free tier. Only 7 are actually useful.
Every AI provider's landing page says 'free tier'. What they don't say is whether you can do anything real with it. We maintain a structured catalog of 45 providers — prices, rate limits, free-tier terms, the works — and one of the fields we track is whether a free tier is *meaningful*: usable for genuine day-to-day work, not a 100-credit demo tap that dies the moment you point a script at it. As of our 2026-08-16 verification, 22 providers list a free tier. Seven pass the meaningful bar. This article shows the list, the real limits, exactly how we decide 'meaningful', what we exclude and why, and how to actually use these tiers without building a fragile dependency on any single one. If you just want the live filter, the free-tier hub is the maintained view of the same data; this post is the snapshot plus the methodology you can audit.
Methodology: what 'meaningful' means and how we test it
We get asked whether 'meaningful' is a vibe. It is not. It is a structured boolean in the catalog — free_tier_meaningful — with a free_tier_meaningful_rationale string per provider. The rule is: can a single developer do sustained real work for at least a month on the published free limits without hitting a hard paywall, buying a plan, or hitting a one-time credit that expires? That means a recurring allowance (requests per minute, per hour, per day, or per month) that refreshes, not a pile of trial credits that evaporates after a weekend of use. We also require that the free tier be documented on the provider's own pricing or docs page at verification time, not just in a launch tweet. We captured 45 provider pages in August 2026, stored the advertised limit verbatim in rate_limits and free_tier_summary, set free_tier=true only where the provider claims a free lane, and then set free_tier_meaningful=true only where the limit is a recurring allowance large enough for continuous use. A free lane that is free only inside a consumer chat product (e.g., Mistral Le Chat) can still count as meaningful if its allowance is a daily habit, but we note that the API is a separate paid lane.
Limits of this method. We count what providers publish. If a provider advertises no hard numbers (DeepSeek's free lane, GitHub Models' free tier), we leave rate_limits empty and exclude the provider from the rate-limit table rather than inventing a number — our honest-absence rule. If a provider rotates its free-model set (OpenRouter, OpenCode, NVIDIA NIM, Cline), we record the rotation note in rate_limits and link the provider entry so you can check today's list. And 'meaningful' is an editorial classification, not a guarantee of service — a provider can change its limits tomorrow. The free-tier hub carries the current classification for all 22, and the plans table shows what each lane costs once it stops being free.
The 7 that hold up
| Provider | What you actually get | Why it counts as meaningful |
|---|---|---|
| OpenRouter | 50 requests/day across free-tier models with no card; adding $10 in PAYG credits unlocks 1,000/day of free models | Recurring daily allowance, no card for the base tier, and the model pool is genuinely usable for scripting |
| Google AI Studio | Hosted free endpoint with a rotating proprietary model lineup; free daily quota | Daily quota that refreshes — you can do real work every day, not just once |
| NVIDIA NIM | ~40 requests/min, no daily cap, no credit card; featured models rotate | Per-minute rate with no daily ceiling — the only tier on this list with that shape |
| Mistral (Le Chat Free) | Base-tier allowances on messages, web search, libraries, and image generation | Daily-driver chat allowance inside a consumer product; not an API trial |
| OpenCode | 5 free models on OpenCode Zen for a limited time; per-model limits rotate | Structured free access to multiple models in one account, even though the set is promotional |
| Cline | Open-source; the Cline provider offers hosted free models with per-model limits | Free models inside the editor with a refresh — fits the 'continuous work' rule |
| Kilo | Free plan with sign-in; 200 requests/hour, BYOK beyond it | Hourly refresh that survives a full workday of coding assistance |
Why these 7 and not the other 15
The other 15 free tiers are not scams — they are just scoped differently. Four patterns keep appearing. One-time grants: Hyperbolic hands you $1, Alibaba gives 1M free tokens per model for 90 days (plus 70M+ tokens for new accounts), BytePlus ModelArk offers 500K free tokens per LLM and 2M for vision models, and OVHcloud's $200 public-cloud trial credit can be pointed at AI Endpoints. These are excellent for benchmarking a provider you might pay later, but they are not recurring. Rate-limited to evaluation: SiliconFlow gives 100 requests/day plus $1 in credit, Cline-style per-model limits that rotate — useful for testing a specific model, not for a daily driver. Consumer-chat-only: Le Chat counts, but many 'free' lanes elsewhere are consumer apps with no API, so they do not help a script. And metering that is too small: Hugging Face's free inference allowance is ~$0.10/month ($2 on PRO) — the smallest we track, demo-only by design. We track all 22 in the directory regardless, because 'evaluation-only' is still valuable when you are evaluating. Just don't architect a side project to depend on an allowance that expires.
Two edge cases we handle explicitly. First, providers that list a free tier but publish no hard numbers (GitHub Models, DeepSeek) are left out of the ranked table rather than ranked on vibes — you will find them on the free-tier hub with a note that says 'no hard numbers published', not a guessed number. Second, free tiers that require a credit card (Mistral, OpenCode) still count if the recurring allowance is real; we store requires_credit_card as a separate boolean so you can filter by it. The provider directory lets you sort by both fields.
The pattern that actually works: mix them
No single free tier is a strategy — the limits differ per provider precisely so you will eventually pay one of them. The working pattern in 2026 is bring-your-own-key: hold free accounts at several of these, and route tasks to whichever has headroom. In practice that looks like: drafts on OpenRouter's 50 free requests/day, fast interactive pulls on NVIDIA NIM at 40 requests/min, long-context reasoning on Google AI Studio's daily quota, and editor work inside Kilo or Cline. When one lane throttles, you switch in config, not in architecture. That's why our chat page is BYOK and browser-direct: your keys live in your own vault, the page calls providers straight from your browser (we relay nothing — you can watch it in devtools), and a split view lets you run the same prompt through two providers side by side. The pricing page tracks what happens when you outgrow all of them, because free tiers are a runway, not a destination.
A concrete setup that has survived months of real use: put OpenRouter, Google AI Studio, and NVIDIA NIM in your free account trio. OpenRouter covers the scratch work, Google covers the heavy reasoning, NVIDIA covers the bursty interactive loop. Add Kilo's 200 requests/hour lane inside your editor and you have four independent free quotas before you spend a dollar. When you do spend, the plans table shows the cheapest paid step for each provider without the marketing gloss. Free tiers stop being a trap when you can leave any of them in one click — and that portability is more valuable than any single allowance.
Limitations and when to re-check
Provider pages cache, model sets rotate, and rate limits can change without a blog post. A '50 requests/day' tomorrow can be '25' or can gain a new model that makes the old limit irrelevant. We re-verify the catalog monthly and timestamp each entry; the free-tier hub reflects the live value. This article is accurate as of the 2026-08-16 verification, editorially refreshed 2026-08-23. If a number here disagrees with the provider page, the provider page is right — and we want the correction on the provider directory bug report.