Google · Model and API
Veo turns a scene description into video. Start with one action and a clear camera movement: a focused shot is easier to review and refine than several unrelated scenes in one prompt.
Google DeepMind describes Veo 3 as supporting native audio, including ambience, effects and dialogue. The official page also showcases Veo 3.1; those capabilities should not automatically be assumed available in every runblob mode.
The runblob catalog offers Fast and Quality with text input. Choose landscape 16:9 or portrait 9:16 and an available quality option. Rates depend on mode and quality; reference input is not advertised for this integration.
Define the location, subject, action, lighting and camera path. For example: a paper boat crosses a puddle after rain; the camera follows slowly at water level, with evening city lights reflected on the surface.
To integrate the Veo 3 API, select the exact version and settings in the playground. The generated cURL includes the endpoint, request fields and required Bearer authorization type. Move the request into your server code; keep secret keys out of the browser. References use service-accessible URLs rather than local file paths.
When looking for an affordable Veo 3 API, compare Fast and Quality with matching settings. Consider the selected rate, quality and number of attempts. Start with one complete shot; adding several events to a prompt makes evaluation harder without guaranteeing a usable clip.
Veo Fast and Veo Quality are integration variants in the runblob catalog. Keep the description and aspect ratio identical, then compare motion, lighting and usefulness. Features advertised for Google’s Veo 3.1 do not mean that the selected integration automatically uses that version.
Atmospheric shots for videos and intros.
Testing directing ideas before a shoot.
Vertical video concepts for social media.
A glass bottle stands on dark stone. The camera slowly pushes in as a narrow strip of light travels across the glass. One continuous shot, no change of subject and no lettering.
A useful test of reflections and smooth camera movement.
A paper boat floats across a puddle. The camera follows at water level with city lights reflected on the surface. Center the subject, use gentle movement and an overcast evening setting.
Select 9:16 in the form; mentioning a portrait shot in the prompt is not a substitute.
Early morning in an empty greenhouse. Water drops on leaves, light mist, and a camera gliding along a row of plants. No people and no abrupt transitions.
A single location makes continuity easier to assess.
Runblob prices in USD. The final cost depends on the selected version and request parameters. Public rates refresh every six hours; personal rates are available in your dashboard.
Configure the parameters and build an API request. Sign in to runblob to start a generation.
Yes. The form offers 9:16 and 16:9. Choose the aspect ratio before submitting your prompt.
The current runblob Veo integration accepts text. For image-to-video, choose a supported model in the catalog, such as Kling Video or Seedance.
Veo Fast and Veo Quality are integration variants in the runblob catalog. Keep the description and aspect ratio identical, then compare motion, lighting and usefulness. Features advertised for Google’s Veo 3.1 do not mean that the selected integration automatically uses that version.
To integrate the Veo 3 API, select the exact version and settings in the playground. The generated cURL includes the endpoint, request fields and required Bearer authorization type. Move the request into your server code; keep secret keys out of the browser. References use service-accessible URLs rather than local file paths.
When looking for an affordable Veo 3 API, compare Fast and Quality with matching settings. Consider the selected rate, quality and number of attempts. Start with one complete shot; adding several events to a prompt makes evaluation harder without guaranteeing a usable clip.