manyframeBuild the creative step into your own workflow.
Programmatic generation for available, approved image and video routes. Check the model, the required inputs and the commercial permissions before you build around it.
Start with the contract
One integration. Explicit capabilities.
Manyframe's relay API includes model discovery, image generation and asynchronous video routes. Models can differ in accepted references, durations, aspect ratios and response behavior. Select an enabled route that supports the exact job you need.
Developer access is a beta offering. A model's presence in a research catalog or a successful studio generation does not establish raw API availability or resale rights. Confirm account entitlement and commercial permissions for your integration and intended territories.
Keep API credentials on your server, scope access to the application that needs it and check current usage accounting. Use the documentation for the selected route rather than treating every model as interchangeable.
Documented relay routes
A practical starting point.
These paths exist in Manyframe's relay specification. Your account's enabled models and route-specific contract determine what you can use.
| Method | Route | Job |
|---|---|---|
| GET | /v1/models | Discover available models |
| POST | /v1/images/generations | Submit image generation |
| POST | /v1/images/edits | Edit supported image inputs |
| POST | /v1/videos | Create a supported video task |
| GET | /v1/videos/{task_id} | Retrieve video task status |
| GET | /v1/videos/{task_id}/content | Retrieve completed video content |
Route presence is not a guarantee that every model supports the same payload or is enabled for your account.
Treat generation as a job, not a page load.
Confirm the route
Choose an available model and verify its inputs, pricing, commercial permissions and account limits.
Submit and record
Validate the brief and media. Persist the returned task identifier and submission outcome in your application.
Reconcile and retrieve
Follow the documented task-status behavior. Retrieve content after completion and handle failure or uncertainty without blindly duplicating a paid request.
Start in the studio when the creative brief is still changing.
Before automating a production task, test whether the selected route consistently produces a result your team accepts. Check product fidelity, format and total cost across attempts. Canvas can also connect generation steps and approved destinations without your team building its own orchestration first.
Explore Canvas workflowsGood questions. Clear answers.
Still curious? Browse all FAQs
Can I use every model in Manyframe through the API?
No. Availability depends on enabled routes, your account and commercial permissions. Raw API access requires its own permission check; studio access alone does not establish it.
Is every route OpenAI compatible?
The relay specification includes several API formats. The /v1/videos route follows an OpenAI-compatible video contract, but other provider-specific routes and model inputs can differ. Use the current documentation for your selected route.
Does the API include social publishing?
Social publishing uses the connected-account and approved-workflow boundary. Do not assume a generation key authorizes social delivery. Explore Canvas and the publishing flow for configured destinations.
Where do I see the current generation cost?
Review the pricing available to your account and selected route. Public provider rates and research catalog prices are not Manyframe selling prices.
Build around a workflow you have tested.
Explore developer access, then confirm the route and commercial scope for your application.