One entry point for shipping AI video generation in production
Use this page to understand how mind2video handles generation, credits, callbacks, storage, and the main public endpoints.
Platform snapshot
Generation, credits, billing, callbacks, and storage are already wired together.
Generation
Text, image, and reference video flows share the same generator experience.
Credits
Freeze, settle, and release stay aligned so billing remains consistent.
Callbacks
Provider callbacks complete jobs and move assets into R2 or S3-compatible storage.
Quick start
Start with account access, billing, model selection, and task tracking.
Create an account
Sign in with Google OAuth or magic link, then land in the workspace.
Add credits or activate a plan
Creem is the primary billing path, with Stripe available as a secondary option.
Choose a model and submit
Use Sora 2, Veo 3.1, Seedance 1.5, or Wan 2.6 depending on your workflow.
Track the task to completion
Credits freeze on submit, settle on success, and release on failure.
Generation workflow
This sequence follows the current service flow implemented in the project.
The request enters /api/v1/video/generate, creates the video row, and selects the model.
Credits are frozen before the provider task is submitted.
The provider runs asynchronously and reports status through the callback route.
The result is fetched and uploaded into R2 or another S3-compatible bucket.
Successful tasks settle. Failed tasks release.
Flow snapshot
generate() -> freeze credits -> provider task -> callback -> upload -> settle/release
generate()
-> create video row
-> freeze credits
-> submit provider task
callback(provider)
-> download result
-> upload to object storage
-> settle() or release()Core endpoints
The endpoint list stays focused on the main integration surface.
/api/v1/video/generateCreate a generation task and freeze credits
/api/v1/video/listList a user's generated videos
/api/v1/config/modelsRead available model configuration
/api/v1/video/callback/[provider]Receive provider callbacks
Frequently asked questions
The docs entry now resolves correctly
Navigation and other product surfaces can now point to this page instead of a missing route.