Why the order matters more than the platform list

Many people assume a free tier is credited the moment you sign up. It usually is not. In 2026, most official free tiers are bound to a project or an API key: without a key, the quota panel stays grey; with a key, the quota becomes callable.

So the right approach is not "list a bunch of platforms" but: identify the console entry type → create the key/project → then read the quota panel.

Four console entry types

  1. Key-bound quota: create an API key and the quota attaches to it immediately.
  2. Project-bound quota: you must create a project first; keys are just credentials inside it.
  3. Org-bound quota: quota is counted per organization; a personal account must create an org first.
  4. Cloud-account-bound quota: quota comes from a cloud account (e.g. Bedrock, Vertex AI, Azure AI); you must enable the service first.

Decide which one you are facing before you start clicking.

Steps

Step 1: Build an entry-type table

Open the consoles of the 3–5 providers you plan to use and record only three things:

  • whether quota is bound to key, project, or organization;
  • whether a payment method is required (most free tiers do not charge, but may require card verification);
  • whether quota is one-time or refreshes periodically.

Step 2: Activate easiest-first

Recommended order:

  1. Key-bound quota first (fastest; you can verify callability within minutes);
  2. then project-bound quota (needs naming and region selection);
  3. then org-bound quota (needs invitation or review);
  4. finally cloud-account-bound quota (service enablement and quota requests; usually slowest).

Step 3: After each key, run one minimal call

Do not batch your tests. Right after creating a key, send a minimal chat/completions request and confirm a 200 response plus a deduction in the quota panel. This surfaces three common problems early: quota not activated, wrong region, model not enabled.

Step 4: Name keys traceably

Use something like platform-purpose-date. Free-tier quota is usually counted per key or project, and messy naming makes it painful to tell which key still has quota.

Step 5: Record the refresh cycle

One-time quota is gone once used. Periodically refreshing quota (often daily or monthly) needs a reminder of the reset time so you do not burn it the day before reset.

Notes

  • Quota numbers change: free-tier amounts are adjusted frequently; this article deliberately omits figures. Always check the console quota panel.
  • Free tiers usually have rate limits: even with quota left, you can be rejected for exceeding RPM/TPM. That is not quota exhaustion.
  • Some platforms require payment verification: verification is not a charge, but virtual cards often fail.
  • Region and model availability: the same platform exposes different models in different regions; choosing the wrong region at project creation leads to "quota exists but model unreachable".
  • Do not mass-register with one card: most platforms link accounts via risk control, which can get quota revoked.

When to use this

  • Individual developers who want to quickly verify several official free tiers within days;
  • Small teams that need to allocate free quota from different vendors across projects;
  • Model comparison work that requires holding usable keys from multiple platforms at once.

Checklist

  • [ ] Confirmed whether quota is bound to key / project / org / cloud account
  • [ ] Created a key and completed one minimal call
  • [ ] Key name includes platform, purpose, date
  • [ ] Recorded whether quota is one-time or periodic
  • [ ] Recorded the rate-limit tier
  • [ ] Confirmed the selected region supports the target model