Google Flow: Google is offering eligible users an opportunity to access up to 30,000 free credits for experimenting with its cloud and AI-powered services. These credits can be useful for beginners, developers, students, startups, and creators who want to explore Google’s technology without immediately spending their own money.
The credits can potentially be used across eligible Google Cloud services, depending on the specific promotion or offer. Users can experiment with tools for artificial intelligence, machine learning, application development, databases, storage, and other cloud-based projects.
Getting started usually involves creating or using a Google Cloud account and checking whether the 30,000-credit offer is available to the account. Eligibility, expiration dates, supported products, and usage restrictions can vary, so it is important to read the official offer terms before activating the credits.
For beginners, the best approach is to start with small projects and monitor usage regularly. This helps prevent unexpected charges after promotional credits expire or when a service is not covered by the offer.
Overall, Google’s free-credit promotions can provide a valuable way to learn cloud computing and AI technologies through hands-on practice. Before using the offer, always verify the current eligibility requirements and terms directly through Google’s official website.
1. Create a Google Cloud project
Go to:
Then:
Select project → New Project
Give it a name such as:
veo-api-project
Click Create.
You don’t need a new Google account for every project.
2. Create/enable billing
Go to:
Create a billing account and attach your project.
Important: Don’t assume that attaching billing gives you $300 usable for Gemini/Veo. The normal $300 Cloud Welcome credit cannot currently pay for Gemini API/AI Studio usage.
For Gemini API paid usage, Google currently uses its Gemini API billing system, including Prepay for many new accounts.
Google says the minimum prepaid purchase is generally $5 or the regional equivalent, although the exact UI can vary by account/region.
3. Go to Google AI Studio
Open:
Go to API keys.
Google AI Studio can automatically create a project/API key for a new user. You can also create an API key manually and associate it with your project.
You’ll see something similar to:
API Keys → Create API key
Select your Cloud project.
Then Google gives you an API key.
4. Check whether you’re on Free or Paid Tier
In AI Studio, check:
Billing / Projects
Google currently distinguishes between:
- Free Tier
- Paid Tier
The Free Tier has model-specific free usage limits.
Paid Tier requires billing and provides higher limits.
5. The important part: getting credits
There are basically three different things people often call “Google credits.”
A. Google Cloud $300 Welcome Credit
This is the famous one.
Historically:
New Cloud account → $300 → use Cloud services
and the maximum can be much higher depending on the account.
You can also enable auto-reload, but I’d personally leave that OFF initially so you don’t accidentally burn money while testing.
C. Eligible Google Cloud promotional credits
This is the interesting one.
Some Google Cloud promotional programs can provide credits that are eligible for particular Gemini API usage.
Google says eligible Cloud credits can be consumed for Gemini API usage after you have an active Prepay balance, but not every Google Cloud credit is eligible.
So you shouldn’t assume:
“$300 Cloud credit = $300 Veo API credit”
That’s no longer true in general.
6. If your goal is AI VIDEO specifically
This is where things get confusing.
There are two separate experiences:
Google Flow
Flow is Google’s creative filmmaking interface.
Gemini API / Vertex AI
This is the developer/API route.
If you want to build something like:
Your website → user uploads image → API → Veo generates video → return MP4
then you want the API route, not Flow’s consumer interface.
The general architecture is:
Your Website
↓
Your Backend
↓
Gemini / Veo API
↓
Veo model
↓
Generated video
↓
Your backend
↓
User downloads video
7. Get your API key
In AI Studio:
API Keys → Create API key
Copy it.
Do NOT put your API key directly into a public website’s JavaScript.
Bad:
website
↓
API key exposed in browser
↓
Gemini
Someone can steal the key and spend your balance.
Instead:
Browser
↓
Your backend
↓
API key stored as environment variable
↓
Gemini/Veo
Google’s current Gemini API getting-started documentation also uses an API key for authentication.
8. Test Gemini API first
You can install Google’s current Python SDK:
pip install -U google-genai
Then set your API key:
set GEMINI_API_KEY=YOUR_API_KEY
On Linux/macOS:
export GEMINI_API_KEY=”YOUR_API_KEY”
Google’s current documentation uses the google-genai SDK.
9. Then move to video generation
For a video application, you’ll need access to a Veo model available through Google’s API offering for your account/project.
The important point is that having a Gemini API key doesn’t automatically mean every Veo model is available to you.
Model availability, pricing, quotas and access can differ.
So check the current model list/pricing before building your application.
10. Monitor your spending
This is extremely important if you’re experimenting with Veo.
Go to:
AI Studio → Dashboard → Usage
Google says usage can be monitored there.
You can also monitor Cloud Billing.
For example, if you’re testing a video generator, don’t blindly run:
100 generations
Start with:
1 generation
↓
check result
↓
check cost
↓
5 generations
↓
check cost
↓
scale
11. Set spending protection
Google currently provides spending-cap controls for Gemini API projects/accounts, although Google notes that billing data can have some processing delay.
That’s useful if you’re building an automated video system.
For example:
Monthly budget
↓
$10
↓
API usage
↓
Veo generations
This prevents you from accidentally leaving an automated process running and discovering a large bill later.
12. What you CANNOT do
There are a lot of videos claiming things like:
“Create Google Cloud account → get $300 → use it for unlimited Veo”
That’s misleading under the current rules.
You also shouldn’t try to:
- manipulate billing responses
- modify API requests to fake credit balances
- exploit quota bugs
- create accounts solely to repeatedly claim promotions
- circumvent rate limits
- modify client-side values and expect Google’s server to accept them
The actual credit balance and billing authorization are controlled server-side.
The cleanest setup for you
If you’re trying to build an AI video-generation business, I’d structure it like this:
GOOGLE CLOUD
│
├── Cloud Project
│
└── Billing
│
↓
GOOGLE AI STUDIO
│
├── API Key
│
└── Gemini API
│
↓
Veo
│
↓
Video Output
And keep the API key on your backend.