Can’t access API because of exceeded current quota yet i have a paid subscription

Google AI Studio
1

image
image3024×4032 3.22 MB

2

Hi @Stifler_Hakeem ,

Welcome to the community! The error in your screenshot indicates that your project is connected to a free tier API and has hit the rate limit. API keys attached to projects are separate from your plan allowance. Your plan provides allowance to build with the chat, but doesn’t provide usage for powering AI in the apps you build. If you’d like to setup billing for a specific project that allow higher rate limits, you can follow the steps below:

  • Go to https://aistudio.google.com/api-keys and click on Create API key in the top right corner of the screen.
  • Locate the project you’re using for your app, it should say “Free Tier”
  • Click the Set up billing button right next to it (in the Billing Tier column)
  • Follow the instructions to attach a credit card or link an existing Google Cloud billing account
  • Once you switch it to the ‘Paid Tier’, your existing API key will get the higher quota right away.

I hope that helps!

3

@TechRay

@Stifler_Hakeem

Hi everyone,

I invite developers, researchers, and users working with Google AI Studio to conduct an independent verification of the platform’s data deletion lifecycle and backend persistence.

Steps to Reproduce the Deletion Verification:

  1. Create a session: Open Google AI Studio and start a new prompt / multi-turn chat session.
  2. Delete the prompt: Trigger the deletion command on the prompt within the AI Studio user interface.
  3. Empty the Trash: Navigate to Google Drive, locate the associated .json file in the Trash folder, and select ‘Empty Trash’ (permanent deletion).
  4. Run recovery: After a period of time (e.g., several days), execute the official Google Drive File Recovery tool on the account.
  5. Check AI Studio: Re-open Google AI Studio and click on the restored .json file. Observe whether the complete conversational memory, prompt context, and token history are reloaded from the backend servers.

Technical Background:

The purpose of this test is to verify whether triggering deletion in Google AI Studio executes a cascading backend purge (DELETE/DROP) on persistent storage, or merely performs a client-side disconnection by moving the frontend metadata pointer (.json) to the Trash while retaining the underlying interaction data on persistent servers.

Verifying whether data remains recoverable following explicit permanent deletion commands is an essential aspect of evaluating data lifecycle transparency and statutory compliance under GDPR Article 17 (Right to Erasure).

Documentation & Forensic Reports: