Gemini API Keys Show 'Unavailable' Quota: Fix Guide

Newly created Gemini API keys showing “Unavailable” quota tier instead of “Free tier” is a known issue that has affected many developers recently. This typically occurs because Google has changed their API key allocation policy, where new API keys often require billing to be enabled on the associated Google Cloud project, even for what should be free tier usage. The discrepancy between older working keys and new unavailable keys suggests Google may have implemented stricter validation or different quota allocation policies for recently created API keys.

Contents

• Common Causes of “Unavailable” Quota Tier
• How to Fix the Issue
• Step-by-Step Solutions
• Alternative Approaches
• Preventive Measures
• When to Contact Google Support

Common Causes of “Unavailable” Quota Tier

Billing Requirements for New Keys

The most common reason for new Gemini API keys showing “Unavailable” is that Google has changed their policy regarding free tier access for newly created projects. Many developers report that new API keys no longer automatically receive the free tier allocation and instead require a billing account to be enabled first.

According to Google’s documentation, “if you’re in a region without the free tier, or if you’ve exceeded the free limits, you need to have a billing account enabled on your Google Cloud project” source.

Geographic Restrictions

The Gemini API’s free tier has geographic restrictions that may apply differently to newly created projects. Your older keys might have been created before these restrictions were implemented in your region, while new keys are subject to current limitations.

Project Configuration Differences

The new project might be missing essential configurations that older projects have. This could include API service activation, proper IAM permissions, or specific settings that affect quota allocation.

How to Fix the Issue

Enable Billing on the Project

The primary solution is to enable billing on your Google Cloud project:

1. Go to your Google Cloud Console
2. Navigate to the Billing section
3. Link a valid payment method to the project
4. Return to AI Studio and verify the API key status

When billing is enabled, the API key should transition from “Unavailable” to “Paid” status, allowing you to use the service source.

Check Project Quotas and Limits

Verify that your project has the necessary quotas enabled:

• Navigate to IAM & Admin → Quotas in Google Cloud Console
• Search for “Gemini API” related services
• Ensure the quotas are set appropriately and not exhausted source

Step-by-Step Solutions

Solution 1: Enable Project Billing

# In Google Cloud Console:
1. Go to billing.google.com
2. Create a new billing account or select existing one
3. Link it to your project
4. Return to AI Studio and refresh API key status

Solution 2: Use a Different Project

If billing configuration doesn’t resolve the issue, try using an older project that still works:

1. In AI Studio, switch to a project where your older API keys work
2. Create a new API key in that project
3. Test if the new key inherits the working project’s quota status

Solution 3: Request Quota Increase

For production usage, you may need to increase your quotas:

“To increase your limits, request a quota increase through AI Studio, or switch to another /auth method” source.

Alternative Approaches

Use Gemini CLI with Authentication

Some developers report success using the Gemini CLI with different authentication methods that bypass the API key quota issues:

# Alternative authentication approach
gemini --auth=gcloud  # Uses gcloud CLI auth instead of API keys

Check for Regional Availability

Verify if the free tier is available in your region by:

1. Checking the official Google AI availability page
2. Testing with a VPN to different regions if applicable
3. Using a different Google account from a supported region

Preventive Measures

Create Projects with Billing Enabled

When creating new projects for Gemini API usage:

1. Enable billing during project creation
2. Verify API service activation immediately
3. Test API key creation and quota status before proceeding with development

Monitor Usage Regularly

Set up monitoring for your API usage:

• Use Google Cloud’s operations suite
• Set up alerts for quota usage
• Regularly check API key status in AI Studio

Maintain Multiple Projects

Keep at least one working project with available API keys as a backup for testing and development purposes.

When to Contact Google Support

If you’ve tried all the above solutions and still experience issues, contact Google support when:

• Your project has billing enabled but API keys remain unavailable
• Older working keys suddenly become unavailable
• You receive consistent 429 errors despite having available quota
• The issue persists across multiple projects and API keys

As noted in the community discussions, this appears to be a systemic issue that may require official intervention from Google’s support team source.

Conclusion

The “Unavailable” quota tier issue for new Gemini API keys is primarily caused by Google’s changing policies regarding free tier access, where new keys often require billing to be enabled. Key takeaways include:

1. Enable billing on your Google Cloud project to resolve most “Unavailable” status issues
2. Check regional restrictions as the free tier may not be available in your location
3. Use established projects for development since older keys typically continue working
4. Monitor your API usage regularly and set up alerts for quota limits
5. Contact Google support if the issue persists despite proper configuration

This appears to be a deliberate policy change rather than a bug, so focusing on proper billing configuration is the most reliable solution for accessing the Gemini API with newly created keys.

Sources

1. Stack Overflow - All my new Gemini API keys show “Unavailable” (no free tier)
2. Google AI Studio - Quota tier troubleshooting
3. Gemini API - Billing documentation
4. Gemini API - Rate limits and quotas
5. Arsturn - Gemini API troubleshooting guide
6. Google Cloud Community - Quota exceeded solutions
7. GitHub - Gemini CLI quota issues
8. Google AI Developers Forum - New API key showing quota exhausted