Introduction

Veo 3.1, Google's flagship video model, runs from a single curl through useapi.net. You drive your own Google Flow account — no Google Cloud project, no enterprise approval, and up to several times lower cost per generation than the official metered API.

The official Gemini API and Vertex meter Veo per second of output. This third-party Google Flow API runs on a flat subscription instead — you spend your normal Flow credits plus one monthly fee for API access, far cheaper per clip. Below: the models you get, the price gap versus the official API, then the two-call workflow and a runnable batch script.

Supported models

Pick a model per request with the model field (default veo-3.1-fast). Credit costs come from Google's official Flow credits table:

Notes from the overview: 4s/6s are Ultra-only on Veo, veo-3.1-quality is 8s only, veo-3.1-lite-low-priority costs 0 credits but is available only to Google AI Ultra $199 subscribers, and 10s clips are omni-flash only. Google Flow can also generate stills with Imagen 4 and the Nano Banana models via the separate POST /images endpoint.

Pricing

You spend your Google AI plan's Flow credits as usual, plus a flat $15/month to useapi.net for API access to every supported service — no per-call surcharge.

Third-party Google Flow API by useapi.net vs. the official Gemini API — drive your own Google Flow subscription instead of metered, per-call API billing:

Expected daily output — Ultra ($199/mo) plan. Daily averages observed on top real accounts. These are expected, not guaranteed: Google governs the underlying Flow allowances and they vary with demand.

*Averages from the busiest real accounts — not guarantees. They are set by Google's own allowances and fluctuate with demand. Applies only to the free lower-priority video queue and image generation. Credit-metered models (Veo 3.1 Fast / Quality and Gemini Omni Flash) are not shown here — their volume is bounded by your plan's monthly Flow credits (see the credit table), not a free allowance.

Veo is billed per second on the Gemini API (an 8-second 720p clip shown) and images are priced per image. Through useapi.net you spend your own Flow plan credits and pay a flat $15/month — image generation is included on any Google AI plan, and there is no Google Cloud project, API key, or per-call metering.

Full per-tier credit allowances and the per-model cost breakdown live on the Google Flow overview. See the setup guide to connect your account.

Generate a video in two API calls

You need a useapi.net API token and a connected Google Flow account. Generation is asynchronous: pass async: true and the create call returns a jobid immediately, then you poll until the video is ready.

1. Submit the job — POST https://api.useapi.net/v1/google-flow/videos:

curl -X POST "https://api.useapi.net/v1/google-flow/videos" \
  -H "Authorization: Bearer $USEAPI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "A serene mountain landscape at sunset, camera slowly panning right",
    "model": "veo-3.1-fast",
    "aspectRatio": "landscape",
    "duration": 8,
    "async": true
  }'

In async mode the response returns immediately with 201 Created, a lowercase jobid, and status: "created":

{
  "jobid": "j1731859234567v-u12345-email:jo***@gmail.com-bot:google-flow",
  "type": "video",
  "status": "created",
  "created": "2026-06-15T12:34:56.789Z",
  "request": {
    "async": true,
    "prompt": "A serene mountain landscape at sunset, camera slowly panning right",
    "model": "veo-3.1-fast",
    "aspectRatio": "landscape",
    "duration": 8
  }
}

1. Poll for the result — GET https://api.useapi.net/v1/google-flow/jobs/{jobId}:

curl "https://api.useapi.net/v1/google-flow/jobs/{jobId}" \
  -H "Authorization: Bearer $USEAPI_TOKEN"

status moves through created → started → completed. When it reaches completed, the finished MP4 is in response.media[].videoUrl (a single prompt with count > 1 returns one entry per clip):

{
  "jobid": "j1731859234567v-...",
  "type": "video",
  "status": "completed",
  "response": {
    "media": [
      {
        "mediaGenerationId": "user:12345-email:6a6f...-video:a1d95d21-...",
        "videoUrl": "https://flow-content.google/video/a1d95d21-...?Expires=...",
        "thumbnailUrl": "https://flow-content.google/image/a1d95d21-...?Expires=..."
      }
    ],
    "remainingCredits": 18760
  }
}

Veo 3.1 typically finishes in 60–180 seconds depending on model and mode. The signed videoUrl is valid for about 24 hours, so download promptly. Prefer not to poll? Pass a replyUrl in the create body to receive a webhook callback when the job completes.

Image-to-video and reference-to-video

Veo takes image inputs two different ways. Upload each image first with POST /assets/email (raw bytes, an image Content-Type, PNG/JPEG/WebP up to 20 MB). The upload response nests the id at mediaGenerationId.mediaGenerationId — that nested string is what you pass back. When you supply any image input you can omit email: the request routes to the account where the image was uploaded.

First / last frame (I2V)

Your image becomes a literal frame of the clip. Pass it as startImage to start from that frame:

curl -X POST "https://api.useapi.net/v1/google-flow/videos" \
  -H "Authorization: Bearer $USEAPI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "Brave Captain Cat chasing away the pirates!",
    "model": "veo-3.1-fast",
    "aspectRatio": "portrait",
    "startImage": "user:12345-email:6a6f...-image:ff9aa5cc-...",
    "async": true
  }'

Add endImage (a second uploaded reference id) to pin the last frame so Veo generates the transition between the two. endImage requires startImage — end-frame-only is not supported. On omni-flash, only startImage is accepted.

Reference images (R2V)

Your images guide the whole clip — subject, character, or style — rather than a specific frame. Pass referenceImage_1 through referenceImage_3 (Veo accepts up to 3, on 8-second clips only, and not on veo-3.1-quality). R2V cannot be combined with startImage/endImage:

curl -X POST "https://api.useapi.net/v1/google-flow/videos" \
  -H "Authorization: Bearer $USEAPI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "A lady says to the dog, \"Say meow meow meow.\" The dog looks at the lady with a surprised, frustrated look and woofs in a human voice, \"What the heck lady?!\"",
    "model": "veo-3.1-fast",
    "aspectRatio": "portrait",
    "referenceImage_1": "user:12345-email:6a6f...-image:abcde-...",
    "async": true
  }'

Mention each reference inline with an @referenceImage_N marker in the prompt, add a referenceAudio_1 (a system voice name like Zephyr) for narration, or pass a reusable character as character_1 (it drives the same R2V mode and counts toward the 3-reference budget). Omni Flash takes references further — up to 7, plus video-to-video editing and synced voices — see the Omni Flash tutorial.

Batch-generate with a script

Finding the right shot takes many attempts, and running them by hand is tedious. The Node.js script reads a list of prompts from prompts.json, uploads any start/end frame images, submits each job in async mode, then polls and downloads every finished MP4 — so you can queue a batch and come back to the winners.

You need Node.js v21 or newer. Put prompts.json and google-flow.mjs in the same folder and run node ./google-flow.mjs API_TOKEN EMAIL, where API_TOKEN is your useapi.net API token and EMAIL is your connected Google Flow account email. The script looks the account up by email automatically and checks its health field before submitting.

Prefer to clone and run it locally? The complete google-flow.mjs and prompts.json are on GitHub in useapi/google-flow-api.

Examples

Real Veo 3.1 clips generated through this Google Flow API, taken straight from our release notes.

veo-3.1-fast » Brave Captain Cat chasing away the pirates (image-to-video)

From Google Flow API v1: Initial Release. Animated from a Nano Banana still passed as startImage.

veo-3.1-fast » Lady and her dog, with AI voice narration

From Veo 3.1 Lite and Voice Narration. A reference-to-video generation with the referenceAudio_1: "Zephyr" preset adding spoken dialogue.

veo-3.1-fast » Dancing cha-cha (portrait reference-to-video)

From Veo 3.1 Portrait R2V. Portrait R2V from a single reference image.

Frequently asked questions

• Is there a Veo 3.1 API? Yes — two ways. Google offers Veo 3.1 directly through the official Gemini API (and Vertex AI), billed per second on a Google Cloud project. Or use useapi.net's Google Flow API, which gives you programmatic access to Veo 3.1 (Quality, Fast, Lite) by driving your own Google Flow account through a standard REST endpoint — no Cloud project, and you pay your flat Flow subscription instead of metered per-second rates (often cheaper per clip — see Pricing).
• What's the difference between Veo 3.1 Quality, Fast, and Lite? They trade quality for speed and cost: veo-3.1-quality is the highest-fidelity model, veo-3.1-fast is the default balance, and veo-3.1-lite is the cheapest, with veo-3.1-lite-low-priority available to Ultra subscribers at lower scheduling priority. See Supported models above for per-model credits and durations.
• Can I do image-to-video with Veo? Yes. Upload your start frame with POST /assets/email, then pass the returned reference id (nested at mediaGenerationId.mediaGenerationId) as startImage — and optionally endImage for a first→last transition (Veo only, requires startImage). See Image-to-video above.
• Do I need to solve a captcha? Google Flow video generation requires reCAPTCHA, but you do not solve it yourself. The useapi.net worker solves the captcha automatically — your first Google Flow account comes with 100 free captcha credits as a one-time grant (powered by CapSolver), and after that you configure your own provider keys via POST /accounts/captcha-providers. The script in this guide sends no captchaToken and relies on this automatic solving.
• How much does it cost? You keep your paid Google AI subscription (needed for video) and add a flat useapi.net subscription for API access to all services. Each generation then spends your normal Flow credits from your Google plan — far cheaper than the official metered API; see Pricing above.
• How is this different from the official Google / Gemini API? Google's official Veo 3.1 access runs through the Gemini API / Vertex AI on a Google Cloud project, billed per second. Google Flow — the consumer app — has no public API of its own. useapi.net bridges that gap by driving your own consumer Flow account at its flat subscription price — no Cloud project or per-second metering (see the side-by-side Pricing comparison above), and the same subscription covers other AI services too.

Conclusion

Visit our Discord Server or Telegram Channel for any support questions and concerns.

We regularly post guides and tutorials on the YouTube Channel.

Check our GitHub repo with code examples.

Cross posted