Why Order by Console Entry

The real difference between official free tiers is not the credit number but the activation path: some issue a key at signup, some require a workspace first, some gate the free tier behind phone or business-email verification, and others park free credits in a Playground where you must manually generate an API key. Sorting by entry difficulty gets you a usable key fastest and prevents one vendor's verification step from blocking the whole process.

Steps

Step 1: Vendors that issue keys at signup (about 5 minutes)

  • Groq Console: after signup you can create a key directly on the API Keys page; the free tier is bounded by rate limits (RPM/TPM), good for validating your call path first.
  • Mistral La Plateforme: create a key under API Keys after signup; the free experiment tier usually has rate and monthly caps, with exact figures shown in the console.
  • These two work well as your "first batch" of keys to confirm your SDK and proxy settings.

Step 2: Vendors that need a workspace or project first (about 10 minutes)

  • Cohere Dashboard: create an organization/project, then generate a Trial key under it; trial credits and rate limits are visible on the project page and require upgrade after expiry or exhaustion.
  • AI21 Studio: sign in, create an API key in Studio; free trial credits are usually granted per account, so check whether they expire.
  • The key here is "project first, key second", otherwise you cannot tell where the credits belong.

Step 3: Vendors with extra verification (about 10–20 minutes)

  • Some vendors unlock the free tier only after phone or business-email verification; personal email may only grant restricted Playground access.
  • If verification fails, do not retry the same number repeatedly; switch method or wait a day to avoid risk controls.

Step 4: Wire keys into your local workflow

  • Store them in .env and point one OpenAI-compatible client at different base_urls to compare rate-limit behavior.
  • Log the x-ratelimit-* response headers on each call to decide which vendor becomes your primary later.

Caveats

  • Free-tier credits, rates and expiry change with vendor policy; this article deliberately avoids hard numbers and defers to the live console.
  • Most free tiers prohibit resale or public-facing services; they suit development, testing and personal projects.
  • Some vendors tie free credits and paid usage to the same key, so rate limits shift after upgrade; keep environments separate.
  • Do not bulk-register accounts with the same card or device; it triggers bans and you lose credits you already had.

When to Use

  • Developers who need to compare several models within a day or two.
  • Teams that want free tiers as fallback routes behind a paid primary API.
  • Teaching or demo scenarios that need cheap, swappable inference endpoints.