⏩ Video Continuation — the “Continue” button for your app
Native endpoint + ready-to-use widget: after every video generated with the Neuralai API, your app shows a “Continue” button that extends the scene natively, with perfect visual and audio continuity.
How it works
Generate the video with the API endpoint (neuralaiPublicApi with video intent, or any video generation): the response includes result.video_id.
Under every video, show the “Continue” button: with the included widget (neuralai-continue.js) it is automatic; with your own code use the video_continue endpoint.
When the button is pressed, the scene continues from the last frame of the previous video: same characters, voice, lighting and style, no jumps.
The new video arrives with a video_id: the “Continue” button appears under it too, so the chain continues up to the 40-second ceiling.
Endpoint
Request parameters
api_keystringrequiredAPI key with the “video” scope (or in the x-api-key header).
video_idstringrequiredID of the source video: result.video_id (or operation_name) returned by the video generation.
promptstringrequiredHow the scene should continue. Continuity (characters, voice, lighting) is applied automatically.
duration_secondsnumberoptionalDuration of the new clip: 4, 6, 8 or 10 seconds (default: inherited from the source video).
resolutionstringoptional“720p” (default) or “1080p”. If omitted, inherited from the source video.
aspect_ratiostringoptional“16:9”, “9:16” or “1:1”. If omitted, inherited from the source video.
operation_namestringoptionalRESUME only: repeats the polling of an in-progress continuation, at no cost.
Response
video_urlPublic URL of the continued video (MP4, ready for <video>).
google_video_uriNative source URI of the video: for the next continuation it is used automatically by the API.
video_idID of the new clip: pass it as video_id to the next call to continue the chain.
chain_secondsTotal seconds of the chain so far (40 ceiling).
Limits and billing
- •Continuation chain: maximum 40 total seconds (Gemini Omni). Over the ceiling the API replies chain_limit_reached.
- •Cost: 200 tokens per continuation, charged ONLY on video delivery (automatically refunded if generation fails).
- •The source video must be YOUR video job completed successfully (result.video_id from the orchestrator or the video API's operation_name).
- •The key requires the “video” scope; the token balance is checked before every request.
Native widget — ready-made “Continue” button
Include the official script and tag every video: the “Continue” button (label automatically in the visitor's language, 13 languages) handles pending, polling and insertion of the new video with its own button by itself, up to the chain ceiling. Style customizable via CSS variables, automatic dark/light.
Auto-embed with data attributes
Programmatic mount
Integration examples
curl
JavaScript
Error codes
401 invalid_api_keyKey missing, invalid or revoked.
403 missing_scopeThe key does not have the “video” scope.
402 insufficient_tokensToken balance below 200.
404 video_not_foundvideo_id is not your video job (or the operation_name no longer exists).
400 chain_limit_reachedThe chain would exceed the 40 total seconds.
500 generation_failedGeneration failed on the worker: no tokens charged.
Related references
- • Endpoint video —
/api-docs/generators - • Response Schema —
/api-docs/schema - • API Key Security —
/api-docs/security - • Instructions for AI Assistants