Current price
$0.011 / output second
Product use cases · In-product generation · Images and video
The same persona every day, in every platform's frame.
Give a fictional adult host a recognizable look, then prepare a short 9:16 greeting and a 1:1 channel cover. Use a single main portrait as the starting point for both.
- Best for
- Social teams, talent studios and creator tools operating a recurring virtual persona across several platforms.
- What you get
- An unattended daily pipeline where identity comes from one committed plate and every published post can be matched back to a task record.
Concept illustration
A creative brief to try
Plan one host for two formats
- 01
Choose a clear main portrait and note the hair, outfit, and signature accessory you want to retain.
- 02
Select 9:16 before making the greeting frame. Leave space for captions and keep the wave small when you animate it.
- 03
Return to the main portrait for the 1:1 cover. Compose the face for the square frame and add any title in your editor.
Before you keep the result
Compare the host across both formats. Check the face, accessory, crop, and moving fingers before publishing.
Start with your own reference images, follow the scene plan and review each result.
Open this scene in the Playground →Recommended models
24 matching models
Matches use the tasks and required capabilities published in the catalogue. Availability and current prices come from each model page.
- Image editing
- 4
- from $0.013 / image
Current price
$0.013 / image
Current price
$0.013 / image
Current price
$0.015 / image
Current price
$0.018 / output second
Current price
$0.022 / output second
Current price
$0.023 / output second
Current price
$0.037 / output second
What one run costs
Worked out from the live catalogue, at the settings named under each figure.
Catalog estimates refresh hourly. Check the estimate for your settings before running; final charges follow the model’s usage and billing policy.
How to build it
This is the only chain here that runs with nobody watching, so it ends where the others begin: with a reconciliation sweep. Callbacks drive publishing minute to minute, and the daily list request is what tells you whether the day matched the plan.
- 01
Ask for an upload ticket
POST
/api/v1/common/upload-urlThe ticket is valid only for the byte count you declared: JPEG, PNG, WebP and GIF up to 10 MiB each. Media that already has a public HTTPS URL skips this step entirely.
- 02
Commit the uploaded file
POST
/api/v1/files/{fileId}/commitThe commit checks the bytes and hands back a spicy:// reference, which is what a model's media fields accept. Committing the same file again changes nothing.
- 03
Create the task
POST
/api/v1/jobs/createTask202 means accepted, not finished. Send an Idempotency-Key, and if the price must not move, send the jobs/quote result together with the amount you agreed to.
- 04
Or let the result come to you
POST
{callBackUrl}Leave a callBackUrl and the finished record is delivered there. Verify the signature before you trust the body, and assume the same delivery will arrive twice.
- 05
Move the file into your own storage
POST
/api/v1/common/download-urlMint a short-lived download URL for the output and copy it into your own bucket within the same job. Results stay on our CDN for 14 days.
- 06
Sweep the whole batch
GET
/api/v1/jobsOne request returns the tasks this key created, newest first, up to 100 per page over a window of at most 92 days. It carries status only — no prompt, no output — so a finished item is still read back by its task ID.
Copy a request
This example starts with the scene described on this page. Fields come from the selected endpoint’s schema. Replace any example.com reference URL with your own image or committed file URI before sending.
Seedance 2.0 Mini · Reference to Video →
Where this usually snags
Platform behaviour that is cheaper to design around than to discover in production.
Reference fields need a model that takes references
Input is validated against that endpoint's own schema and extra properties are refused, so a reference sent to a model without the capability is a 400, not a field quietly ignored.
Aspect ratio is a list, not a number
Resolution, aspect ratio and length come from each endpoint's own input schema as a closed set, and extra properties are refused. Check that the frame you ship in is on that list before you pin an endpoint to a format.
Verify the callback before you read it
Check the HMAC over task ID, timestamp and body hash in constant time, and reject stale timestamps. Deliveries repeat, so the receiver has to be idempotent.
Launch checklist
- 01Keep the versioned character originals in your own storage and reuse accessible HTTPS references. Temporary uploads last 1 day, so refresh them when needed. Record reference order and settings for comparison, then check the face, hair and identifying details in each result; repeated inputs can still produce variation.
- 02Verify the callback signature before the payload reaches the publishing queue, and expect the same delivery to arrive twice.
- 03Produce each platform's frame from the same plate instead of cropping one master — aspect ratio is a closed enum on every endpoint.
- 04Close the day with one task list request and reconcile it against what you published; results stay available for 14 days, so your archive should not depend on them.
Models that match this workflow
Explore model families for this workflow. Open a model page to review its inputs, pricing and current availability.
Frequently asked questions
24 published models match the listed tasks and required capabilities. Compare their inputs, examples, availability and current prices before choosing one.
Keep the versioned character originals in your own storage and reuse accessible HTTPS references. Temporary uploads last 1 day, so refresh them when needed. Record reference order and settings for comparison, then check the face, hair and identifying details in each result; repeated inputs can still produce variation.
Generate each platform's frame from the same plate rather than cropping one master. Aspect ratio is a closed enum on every endpoint, so confirm that the frames you publish in are offered before you pin one for the channel.
Leave a callback URL and verify the signature before the payload reaches your publishing queue; assume the same delivery arrives twice and make the receiver idempotent. Close each day with one task list request and reconcile it against what you actually published.
About this workflow
A persona channel is an unattended pipeline with a publishing deadline. One committed identity plate carries the look, verified callbacks carry the posts, and a daily list request tells you whether the day matched the plan. Results are available for 14 days and are never published to a public feed by us, so the archive stays yours to keep.
