Skip to documentation
Let’s build
PUBLIC TECHNICAL PREVIEW Production access and integration details are agreed during onboarding.
Amora Docs/Image & video generation

DEVELOPER DOCUMENTATION

Image & video generation

Asynchronous character content workflows.

Content generation turns a configured character identity into reviewable assets for the marketplace, conversations and distribution channels.

Image workflow

Start with the character identity or approved references. Submit a scene and composition brief, generate candidate images, review identity consistency, and store approved outputs with their associated character and content metadata.

Generated video workflow

Generated clips are asynchronous jobs. A typical workflow starts with an approved character image, submits an image-to-video request, tracks completion through a job status or webhook, and imports the result into the asset library.

Retain the provider job identifier. A timeout does not prove that a paid job failed, so check its state before submitting it again.

Asset lifecycle

Character + approved scene brief
  → Generation job
  → Status or webhook
  → Review and approval
  → Private asset storage
  → Publish to an entitled user or approved channel

Keep access controls and delivery URLs separate from generation. A temporary provider output URL is not a long-term content library.

Media integrations

Our media provider guide recommends FLUX.2 for character imagery, Kling through fal for generated clips, and Runway as an alternative video integration. These are proposed integrations until connected and tested for the project.

Live video streaming

Live video-avatar streaming is Coming soon. It is a separate capability from generating and delivering a finished clip.

Building something personal?

Talk to our team about your architecture, character and launch.

Discuss your integration ↗