Skip to main content
Guide

Veo 3.1 429 Resource Exhausted? Get Veo 3.1 for 120 Credits

Veo 3.1 429 RESOURCE_EXHAUSTED on a paid Gemini API project? Generate Veo 3.1 on AIVeed for 120 credits, $0.59 on the $99 pack, with no Google quota to fix.

•Updated •7 min read

If your Gemini API project keeps hitting Veo 3.1 429 RESOURCE_EXHAUSTED errors, you can generate the same ~8-second Veo3.1 video on AIVeed for 120 credits, $0.59 on the $99 / 20,000-credit Business pack, with no Google project, billing tier or Veo quota to provision (AIVeed Veo3.1 model page and pricing, checked October 4, 2026; methodology).

AIVeed runs Veo3.1 in the browser from the Veo3.1 model page and through the AIVeed API as veo3-fast and veo3-quality, on one AIVeed key and one credit balance (AIVeed API model catalog, checked October 4, 2026). Credits are charged up front and refunded automatically if a generation fails (AIVeed API reference, checked October 4, 2026). Developers can create an AIVeed API key in a few minutes and point an existing Veo integration at it.

Why does Veo 3.1 return 429 RESOURCE_EXHAUSTED on a paid Tier 1 project?

Veo 3.1 has been returning 429 RESOURCE_EXHAUSTED to paid Tier 1 Gemini API projects whose Veo quota shows as unused, and as of October 4, 2026 Google has not posted a cause or a fix in the public threads (Google AI Developers Forum, checked October 4, 2026). On September 28, 2026, one developer on a prepaid Tier 1 project wrote that AI Studio showed Veo Fast: 0/2 RPM, 0/10 RPD, yet both veo-3.1-fast-generate-preview and veo-3.1-lite-generate-preview immediately return: 429 RESOURCE_EXHAUSTED You exceeded your current quota, please check your plan and billing details. On October 1, 2026, a second developer replied in the same thread: I have the exact same issue. and But every Veo generation request immediately returns: 429 RESOURCE_EXHAUSTED.

The Veo 3.1 429 error on unused quota is not new. A Tier 1 developer reported on July 20, 2026 that every single API request I send for veo-3.1-lite-generate-preview instantly fails with HTTP 429 RESOURCE_EXHAUSTED while AI Studio showed an available quota of 0/10 daily (Google AI Developers Forum, checked October 4, 2026). Google's forum staff answered the September thread on October 1, 2026 by asking for the project ID and the time of a failed request by direct message, so the check happens project by project, in private. If your project returns permission denied instead of 429, see our guide to Veo 3.1 permission denied.

Is Veo 3.1 429 RESOURCE_EXHAUSTED caused by Google's spend limit?

Google's spend limit is one documented cause of Veo 3.1 429 RESOURCE_EXHAUSTED, but it does not explain the reports above, where usage was zero. The Gemini API rate-limit page sets a spend limit of $10 per 10 minutes on Tier 1, $50 on Tier 2 and $200 on Tier 3, and states that If you hit a spend-based rate limit, the API returns a 429 RESOURCE_EXHAUSTED error (Gemini API rate limits, checked October 4, 2026). The same Google page says Tier 2 requires $100 of payments plus 3 days from the first successful payment. Veo 3.1 has no free tier on the Gemini API at all: Google's pricing page lists every Veo 3.1 model as "Not available" on the free tier (Gemini API pricing, checked October 4, 2026).

How do I generate Veo 3.1 videos when the Gemini API returns 429?

To generate Veo 3.1 videos while the Gemini API returns 429, send the job to AIVeed instead, where Veo3.1 runs on AIVeed credits rather than a Google project's quota (AIVeed API reference, checked October 4, 2026). There are two routes.

In the browser: open the AIVeed Veo3.1 model page and choose Generate with Veo3.1. The AIVeed Veo3.1 page lists two modes, Fast at 120 credits and Quality at 320 credits, each producing about 8 seconds of video, ready in about 2 minutes, with no subscription (AIVeed Veo3.1 model page, checked October 4, 2026).

Through the API: the AIVeed API quickstart describes the flow (checked October 4, 2026):

  1. Create an AIVeed API key. Sign up on the AIVeed developer dashboard, verify your email and create a key. The secret starts with aiv_sk_ and is shown once.
  2. Submit the Veo3.1 job. POST to https://api.aiveed.io/v1/generate/video with the model veo3-fast or veo3-quality, a prompt and an aspect ratio of 16:9 or 9:16. Duration is fixed at about 8 seconds, so leave it out.
  3. Collect the video. Poll GET /v1/jobs/{id} until the status is completed, or register a webhook, then read the permanent MP4 link from GET /v1/videos.
POST https://api.aiveed.io/v1/generate/video
X-API-Key: aiv_sk_...
Idempotency-Key: veo-launch-teaser-01
Content-Type: application/json

{
  "model": "veo3-fast",
  "prompt": "A barista slides a latte across a sunlit counter and says: your order is ready",
  "aspect_ratio": "16:9"
}

The AIVeed Veo3.1 request also accepts a start image (first_frame_url) and an end image (last_frame_url), and a finished Veo3.1 clip can be extended by about 7 seconds for a flat 120 credits through POST /v1/extend/video (AIVeed API reference, checked October 4, 2026). Our AI video generation API guide compares Veo3.1 with the other video models on the same AIVeed key.

How much does Veo 3.1 cost on AIVeed?

Veo 3.1 on AIVeed costs 120 credits for an ~8-second Fast clip and 320 credits for an ~8-second Quality clip, which is $0.59 and $1.58 on the $99 / 20,000-credit Business pack (AIVeed pricing endpoint and AIVeed pricing, checked October 4, 2026). AIVeed credits never expire and can be used across any model (AIVeed pricing, checked October 4, 2026). For Google's own per-second Veo 3.1, Fast and Lite rates side by side with these, see Veo 3 pricing.

Veo3.1 on AIVeed by credit pack (AIVeed pricing, checked October 4, 2026)
AIVeed Veo3.1 settingCredits$99 / 20,000 Business$49 / 9,000 Popular$19 / 3,000 Starter$5 / 600 Pilot
AIVeed Veo3.1 Fast · ~8s120$0.59$0.65$0.76$1.00
AIVeed Veo3.1 Quality · ~8s320$1.58$1.74$2.03$2.67
AIVeed Veo3.1 extension · ~7s120$0.59$0.65$0.76$1.00

What happens if a Veo 3.1 video fails on AIVeed?

A Veo 3.1 video that fails on AIVeed is refunded automatically: the AIVeed API reference says jobs are charged up front and automatically refunded if the provider fails, and AIVeed's pricing page says credits are restored immediately when a generation fails for technical reasons (both checked October 4, 2026). An AIVeed API request the balance can't cover returns INSUFFICIENT_CREDITS, and a retry sent with the same Idempotency-Key replays the original job instead of charging again (AIVeed API reference, checked October 4, 2026). Our post on why failed AI videos still cost money elsewhere covers refunds across platforms.

What are the AIVeed API rate limits for Veo 3.1?

The AIVeed API allows 10 requests a minute and 3 jobs at once on a free key, and 30 requests a minute and 10 jobs at once after the account's first credit purchase, for Veo3.1 and every other model (AIVeed API reference, checked October 4, 2026). Every AIVeed API response carries X-RateLimit-Limit and X-RateLimit-Remaining headers, a request over the per-minute limit returns 429 RATE_LIMIT_EXCEEDED with a Retry-After header, and a request over the concurrency cap is not charged. AIVeed publishes the live values for each key at GET /v1/usage/limits. For more on moving Veo work off Google's own setup, see the best Veo 3 alternative.

Methodology and verification

Verified on October 4, 2026. The forum reports were loaded in full from the Google AI Developers Forum and are quoted exactly; no usernames are reproduced. Google's spend limits, tier rules and Veo 3.1 free-tier status come from Google's own Gemini API rate-limit and pricing pages. AIVeed's Veo3.1 credits come from the public AIVeed pricing endpoint and match the AIVeed Veo3.1 model page; the request fields, refunds, idempotency and rate limits come from the public AIVeed API quickstart and reference. Pack prices are the USD packs listed on AIVeed pricing.

Dollar figures are credits × pack price ÷ pack credits. On the Business pack, $99 ÷ 20,000 = $0.00495 a credit, so 120 credits is $0.594, shown as $0.59, and 320 credits is $1.584, shown as $1.58; on the Pilot pack, $5 ÷ 600 = $0.00833 a credit, so 120 credits is $1.00 and 320 credits is $2.667, shown as $2.67. Every figure was recomputed at full precision and rounded once. The example request uses documented fields only and was not run; no video was generated for this post.

Sources

Make your next Veo3.1 video from the AIVeed Veo3.1 model page, or get a key on the AIVeed developer dashboard and send the job from code. Start at AIVeed.