Skip to content

$ uprouter — best lists

Free AI Router

shareXLinkedInReddit
// tldrthe short version
  • A free ai router is an AI API router whose only access mode is free — no card, no subscription, no upgrade path. UPROUTER tracks 39 of them; the sample is the top 10 by verified free-credit value.
  • Free access comes in three honest shapes: one-time signup grants (e.g. a granted balance that depletes), recurring daily/monthly quotas, and shared no-auth endpoints.
  • Risk is the defining trade-off: several entries are community relays that pool upstream keys, and upstream providers' terms (OpenAI's included) prohibit that pattern — the risk badge and rationale on each entry say which concern applies.
  • Ordering is a disclosed data sort — free-credit value descending, unquantified values last, ties alphabetical. Community votes and affiliate relationships never change it.
  • If you need production reliability rather than zero cost, look at /best/free-credits (282 freemium routers) instead.

What is a free ai router?

A free ai router is an AI API router with no paid tier at all: the only way to use it is the free access it offers, and there is nothing to buy once that access runs out. In the UPROUTER dataset this is the routerType "free-only" — 39 published entries as of the last check, out of 388 tracked routers. The other three router types exist for contrast: freemium (38 free tiers plus paid options across the directory), paid-only, and enterprise-first offerings.

A router is a service that exposes AI model APIs — usually an OpenAI-compatible /chat/completions endpoint — so one key reaches models that otherwise sit behind several vendor consoles. Free-only routers are interesting precisely because they remove the billing surface entirely: no card on file, no spend limit to configure, no invoice. What you give up is the exit ramp. A freemium router lets you start free and pay as you grow; a free ai router caps out where its free access ends.

The 39 entries fall into recognizable shapes. Some are platforms that are free as a business model (a shared endpoint anyone can call, or a free credit grant for trying the product). Others are community projects that relay upstream inference. The access column in the sample below tells you which: "API key" means you register and get a key that encodes your free allowance; "No auth" means the endpoint is callable without any credential at all — convenient, and also why operators can revoke it unilaterally at any moment.

What "no paid tier" actually changes about the decision

The absence of a paid tier is not just a price point; it changes the risk profile. With a freemium provider you are a customer: terms of service apply to a defined account, support channels exist, and the provider has a financial reason to keep the free tier roughly as documented (it is their acquisition funnel). With a free-only router you are a guest. The access can be rationed, tightened or switched off by an operator decision, and your code will only find out by failing.

That makes free-only routers a genuinely good fit for specific jobs and a bad one for others. Good fit: prototypes where you are learning the model's behavior, local development, low-volume automation (a nightly job, a small personal tool), and education, where the point is wiring up the call. Bad fit: anything user-facing or time-bound, anything where a silent rate-limit change at 9am costs you money, and anything that needs an SLA — no free-only service in this slice offers one, because there is no paid side to attach one to.

There is also a data-handling angle: a no-auth relay cannot hold you to a data policy, and your prompts may sit in shared infrastructure you cannot audit. For sensitive inputs, prefer "API key" entries with a named operator, and read the risk rationale first.

How the free access on these routers is built

Three mechanisms cover nearly everything in this slice, and they fail differently, so it is worth knowing which one a given entry uses — the entry page records it in the free-credit note with the source URL.

One-time grants. The operator credits your account with a fixed allowance at signup, and the balance depletes. DeepSeek is the cleanest example: its pricing page states that fees are deducted from a topped-up balance "with a preference for using the granted balance first when both balances are available" — the granted balance is the free part, and once it is gone, the account is a paying account or nothing. On a free-only router the second option is the only one, so the grant is the whole relationship.

Recurring quotas. Some platforms reset free usage on a schedule rather than a balance. Cloudflare's Workers AI free tier, for example, publishes explicit daily limits that "reset daily at 00:00 UTC"; the dataset's free-credit value for such entries is a normalization of the quota at the provider's own pay-as-you-go rate, which is why the figure is an estimate and flagged where the assumption was ours.

Shared endpoints. The router serves inference from pooled capacity and meters nobody individually. Hugging Face's Inference Providers route a single token to eighteen partner providers and state "no extra markup on provider rates" — that is the aggregator model applied to free access; Pollinations runs the same shape (one OpenAI-compatible API for text, image, audio, video) with "free Pollen for prototypes & testing". Shared capacity is the most convenient and the most revocable: no contract protects you when the operator changes their mind.

Risk: who runs a free router, and why it matters here more than elsewhere

Every entry in this directory carries a community-evidence risk rating (low / medium / high / unrated) with the reasoning on the entry page, but the rating matters most on this slice. The reason: the free-only business model attracts relays that pool API keys obtained through other people's accounts or through upstream free tiers, and that pattern sits in direct tension with upstream providers' terms. OpenAI's usage policies prohibit sharing accounts or reselling access to the API; a relay that fronts shared keys is structurally exposed to being cut off, and your application inherits that exposure.

The dataset does not try to hide this distinction. Entries whose operator identity, terms or funding are unclear tend to carry "medium" or "high" with a rationale naming the specific concern (young service, vague terms, unclear data handling, ToS friction — the rubric is on each entry and summarized on /about). "Unrated" means the evidence is not there yet, not that the entry is clean. Treat a high-risk free relay as a convenience endpoint you can lose at any time, and design around that rather than discovering it.

What we verify, and what we do not

To keep this page honest about its own limits: UPROUTER runs best-effort status probes against each endpoint (the "status" column and the probe history on each entry), normalizes published free-credit figures into comparable USD estimates and flags every estimate , and records the date each figure was last checked. We do not benchmark latency or throughput, do not guarantee uptime, and do not re-verify each provider's terms — the ToS claims link to the providers' own policy pages, which change. Free tiers are the most volatile part of any AI pricing table; when in doubt, the provider's pricing page is the source of truth, and the entry page links it.

// sample — top 10 of 39 — by free-credit valueverify with the provider before buying
ProviderFree creditsAccessRiskStatus
AgentRouter
agentrouter.org
$200.00API keyMedium risk up
AnyRouter
anyrouter.top
$50.00estAPI keyMedium risk up
APIMonkey
monkeyapi.apimonkey.online
$14.88estAPI keyHigh risk up
FreeTheAI
freetheai.xyz
$7.50estAPI keyHigh risk up
Pollinations
pollinations.ai
$5.00estAPI keyLow risk up
ChatAnywhere
chatanywhere.tech
$2.00estAPI keyMedium risk up
RouterPark
routerpark.com
$2.00estSystemHigh risk up
Hvoy.ai
hvoy.ai
$1.49estSystemLow risk up
DeepSeek
platform.deepseek.com
$0.70estAPI keyMedium risk unknown
Hugging Face
huggingface.co
$0.10API keyMedium risk up

free-credit values are normalized USD estimates from public sources — see methodology · ordering is a disclosed data sort, never sponsorship

Choosing among free ai routers: the criteria that actually separate them

Credit value is the sample's sort key because it is the one number comparable across the three free-access shapes — but it is not the only criterion, and a big one-time grant is not the same asset as a daily quota. Walk the columns in this order: access first (API-key entries are revocable per account and come with terms; no-auth entries are revocable in principle and come with none), then risk (the rationale on the entry names the specific concern — an established platform's medium rating and a nameless relay's medium rating are different animals), then model count (one small model is a different tool than the open frontier), and only then status — an official platform that is down comes back; a relay that is down is probably gone.

Two honest shortcuts. If your job is "any recent open model, cheaply, right now", start from the top of the sample and read down until the access shape and risk tier fit your threat model. If your job is "free today, paid path tomorrow", you are in the wrong slice by definition — /best/free-credits lists the 282 freemium routers where the free tier is the on-ramp rather than the whole road, and /routers/paid-api is the other end of the spectrum.

How to evaluate a free ai router before you build on it

  1. 1.Open the entry and read the free-credit note in full: it states the shape of the free access (grant, quota, shared), the source URL it was normalized from, and whether the figure is an
  2. 2.Check the risk badge and read the rationale. A "high" with a named ToS concern means the endpoint can disappear by policy, not just by failure — decide whether that is acceptable for your use.
  3. 3.Look at the live status and the probe history on the entry. "Unknown" means we have not had a recent clean probe, not that it is down; "down" on a relay is often terminal.
  4. 4.Run your own smoke test: one request to the OpenAI-compatible endpoint with a prompt representative of your workload. Note the error shape when you hit a limit — it tells you what the failure looks like when your real traffic meets it.
  5. 5.Read the provider's terms on key sharing, reselling and data retention. For no-auth relays, note what the terms say about who may send prompts through the endpoint.
  6. 6.Check the quota reset rule in the provider docs (daily, monthly, one-time) — a monthly reset and an emptying grant are different commitments.
  7. 7.Configure a fallback before you need one: a second router from /best/free-credits in your client config means a revoked endpoint is a config change, not an outage.
// faq10 questions
What exactly is a free ai router?

A router (an API service exposing AI models through one endpoint) whose only access mode is free — in the dataset, routerType "free-only". You cannot buy more of it. The 39 entries here range from official free platforms to community relays; the access and risk columns tell you which you are looking at.

Do free ai routers need an API key?

Some do and some don't. The "Access" column on each row shows it: "API key" entries give you a personal key that encodes your free allowance (usually with signup), while "No auth" endpoints are callable without any credential. Keyed access is revocable per account; no-auth access is revocable in principle.

Do I need a credit card for any of these?

Most entries in this slice do not — that is part of the appeal. A few platforms attach a card for abuse prevention even though the tier is free; the entry page records the access requirement, so check the specific row rather than assuming.

Is it safe to build on a free ai router?

For prototypes, learning and low-volume automation — yes, with eyes open: the endpoint can be rationed or revoked by an operator decision, and no-auth relays have no data policy to hold. For user-facing production, no free-only service offers the guarantees you need; pair it with a freemium fallback from /best/free-credits.

Why does this list only cover {count} routers?

Because that is the honest size of the free-only slice of the directory: entries where the only access mode is free. The remaining routers have a paid, freemium or enterprise path, and they live on /best/free-credits (282 free tiers of every shape) and the category pages. Shrinking or padding the slice to hit a number would make the page worse, so it keeps the predicate as-is.

How is the free-credit value calculated?

Each provider's published free allowance — signup bonus, daily or monthly quota, included usage — is normalized into USD at that provider's own pay-as-you-go rates where one exists. Where a figure required an assumption, it is flagged on the entry; where it could not be quantified honestly, the row shows "not quantified" and sorts to the bottom instead of carrying a made-up number.

How is the list ordered?

Free-credit value descending; entries without a quantified value sort after quantified ones, and ties break alphabetically by name. It is a data sort, never sponsored — no affiliate, referral or commercial relationship changes the order, and community votes are displayed but excluded from it.

Do community votes or reviews change the ranking?

No. Votes and reviews are shown on each entry as a signal about real-world experience (the review tags include "verified free tier" and "hit rate limits"), but the sort rule above is the only thing that orders this page. That separation is deliberate: the list should survive being disliked by a loud minority, and disliked entries should survive being a data favorite.

What happens when a free ai router stops working?

Practically: your fallback kicks in if you configured one — the evaluation steps urge it, because free-only endpoints are the most revocable class in the directory. For the record: the status column reflects best-effort probes, and the entry keeps its probe history.

Where does this data come from?

From UPROUTER's public dataset (documented at /developers, CC BY 4.0): 388 published entries with pricing, free-credit values, risk ratings, probes and verification dates. This page recomputes counts and sample per request, so 39 moves as entries change.

Sources & References

  1. UPROUTER.ONLINE — Public dataset (CSV, CC BY 4.0) — The {count} free-only entries, free-credit values, risk ratings, access types and status shown in the sample table
  2. DeepSeek — Models & Pricing — api-docs.deepseek.com — One-time-grant shape: fees deduct from "granted balance first" before topped-up balance; per-1M-token published rates used for normalization
  3. Hugging Face — Inference Providers documentation — Shared-capacity aggregator model: one token across 18 partner providers, "no extra markup on provider rates", pay-as-you-go with monthly included credits
  4. Pollinations — pollinations.ai — platform overview — Free Pollen for prototypes and testing on one OpenAI-compatible API (text, image, audio, video)
  5. Cloudflare — Workers AI pricing & free-tier limits — Recurring-quota shape: published daily limits that "reset daily at 00:00 UTC" on the free tier
  6. OpenAI — Usage policies — Upstream terms prohibit sharing accounts and reselling API access — the basis for the relay ToS-risk section
  7. UPROUTER.ONLINE — About & methodology (risk rubric, 45-day staleness, probes) — How risk ratings, confidence and best-effort status probes are produced; correction pathway
// how this list is builtlast verified 2026-10-12

predicate: Inclusion is the dataset predicate routerType = "free-only" (only free usage available) over published, non-internal entries. 39 entries matched at last check. Entries that add a paid or freemium path are excluded by definition — they live on /best/free-credits.

sort: Free-credit value (creditValueUsd) descending. Entries without a quantified value sort after quantified ones (nulls last); ties break alphabetically by name. Community votes, reviews and commercial relationships never enter the sort.

freshness: Free-credit values carry a per-entry last-verified date; entries unverified for 45+ days are flagged stale per the methodology on /about. The "status" column is a best-effort probe result from our network — a measurement, not a guarantee. Counts and the sample recompute from the live dataset on each request.

limitations: We do not benchmark latency or throughput, do not guarantee uptime, do not re-verify each provider's terms text, and cannot confirm how long any free access will persist — free tiers are the most volatile part of AI pricing. Figures marked _est._ are normalized estimates from public sources, not provider-published totals.

Full methodology, probe cadence and the correction pathway: about & methodology · raw data: public dataset (CC BY 4.0) · pricing and status on every row are measurements with dates, not guarantees.

Written by Mike Fleming — Founder & Editor. He runs the directory, writes the entry research and reviews every page here; corrections go to the contact page.