Agnes Video V2.0 is a production-oriented video generation model that supports text-to-video, image-to-video, and keyframe animation. Video generation uses an asynchronous task API: create a task first, then retrieve the result through
video_id or task_id.Model
agnes-video-v2.0Create Task
POST /v1/videosGet Result
GET /agnesapi?video_id=<VIDEO_ID>Current Price
Video duration is currently
$0 / second.Overview
Developers can generate high-quality videos from text prompts or image URLs. The model is suitable for storytelling, marketing videos, product demos, social media content, app motion assets, and AI creative workflows.Core Capabilities
Text-to-video
Generate videos directly from text prompts.
Image-to-video
Turn static images into dynamic videos.
Keyframe Animation
Generate smooth transitions between multiple keyframes.
Motion Control
Control subject actions, camera movement, and scene dynamics through prompts.
Visual Consistency
Maintain subject, style, and scene consistency across frames.
Cinematic Output
Generate high-quality cinematic video content.
Asynchronous API
Create a task first, then poll or query the generated result.
Use Cases
Storytelling
Short films, character scenes, and narrative clips.
Marketing Videos
Product ads, promotional videos, and campaign content.
Social Media Content
Reels, Shorts, and TikTok-style videos.
Image Animation
Add motion to portraits, products, characters, or scenes.
Product Demos
Generate product showcase videos from text or images.
Keyframe Transitions
Generate smooth transitions between different visual states.
Prerequisites
Before integration, make sure you have a valid Agnes AI API key, network access to the Agnes AI API gateway, and a text prompt for video generation. Image-to-video and keyframe animation workflows also require publicly accessible image URLs.
API Reference
Create Video Task
Get Video Result: Recommended Method
Get Video Result: Legacy-compatible Method
Headers
Create Task Parameters
Parameter Normalization
Agnes Video V2.0 normalizes some video generation parameters to ensure stable output quality. When the submitted
width, height, or aspect ratio does not exactly match supported model specifications, the system maps the request to the closest standard output configuration.480p, 720p, and 1080p.
The original
width, height, and num_frames values in the request may not exactly match the normalized generation settings. When displaying task information, calculating video duration, or debugging generation results, use the size, seconds, and metadata.size_mapping fields returned by the API response as the source of truth.Create Task Examples
- Text-to-video
- Image-to-video
- Keyframe Animation
Create Task Response
When the video task is created successfully, the API returns task information. The response includes bothtask_id and video_id. video_id is the recommended ID for retrieving video results.
Response Fields
Get Video Result
- By video_id
- By video_id + model_name
- Legacy: By task_id
Final Result Response
When the task is completed, the API returns the final video result. The generated video URL is available inmetadata.url.
Result Fields
Task Status
Video Duration Control
Agnes Video V2.0 supports controlling video duration withnum_frames and frame_rate.
num_framesis the total number of generated frames.frame_rateis the playback frame rate in frames per second.num_framesmust be less than or equal to441.num_framesmust follow the8n + 1rule.frame_ratesupports values from1to60.
Common Duration Settings
Recommended Parameters
Prompt Best Practices
Text-to-video Prompts
Text-to-video Prompts
Describe the subject, action, scene, camera movement, lighting, and visual style.
Image-to-video Prompts
Image-to-video Prompts
Describe what should move and which key subject elements should remain stable.
Keyframe Animation Prompts
Keyframe Animation Prompts
Clearly describe the transition relationship between keyframes.
Error Codes
Pricing
Integration Checklist
Use
agnes-video-v2.0 as the model name.Video generation is asynchronous. Create a task first, then retrieve the result.
New integrations should use
video_id to retrieve video results.Use publicly accessible image URLs for image-to-video and keyframe workflows.
Use the response fields
seconds and size as the source of truth after parameter normalization.