Build image and video generation into your app

AI Image and Video API

Integrate SeedreamBest AI image generation, image editing, video generation, image-to-video, uploads, and usage-based billing into your product.

Open API platform View API pricing

/tasks

Core endpoint

Usage-based

Billing

Sub keys

Auth

POST /api/v1/tasks

{
  "type": "video",
  "mode": "first_frame",
  "prompt": "cinematic product shot, slow camera push",
  "asset_ids": ["asset_123"],
  "options": {
    "duration": 6,
    "resolution": "720p"
  }
}

Capabilities

Built for repeatable creative production

One API for creative generation

Create text-to-image, image editing, text-to-video, first-frame video, and first-and-last-frame jobs through structured requests.

Asset upload workflow

Upload images first, receive asset IDs, then reuse those assets for image editing or image-to-video generation.

Usage and balance tracking

Monitor API balance, monthly spend, requests, active keys, and billing activity from the API Platform.

Workflow

From idea to usable output

Create a sub key

Generate a server-side API key from the API Platform and store it in your backend environment variables.

Upload assets if needed

For reference image and keyframe workflows, upload source files before creating a generation task.

Create and poll tasks

Submit a task, store the returned task ID, then poll status until generated results are ready.

Use cases

Where teams use this

AI creative tools and SaaS products

Programmatic ad creative generation

Automated product image and video pipelines

Internal marketing asset systems

Creator platforms that need image and video generation

FAQ

Common questions

What can I build with the SeedreamBest API?

You can build workflows for AI images, image editing, text-to-video, image-to-video, creative copywriting, asset upload, and usage tracking.

How is API usage billed?

API requests use the same API balance pricing model shown on the pricing page, with usage tracked by task and key.

Should API keys be used in the browser?

No. API sub keys should be stored and called from your server so credentials are not exposed to end users.