UserBus
VIDEO
Video generation
Text to video on marketplace capacity. Minimax H3 is the first model on UserBus, and UserBus Video anchors the delivery path for every video job.
Submitted from the console.
GENERATION CAPABILITIES
Every modality. One compute market.
UserBus runs generation work of every modality on capacity that independent providers supply. Buyers choose the model and the parameters. The marketplace finds the capacity, moves the job, verifies the output and settles it.
01 / MODALITIES
Video, image, audio and speech.
One request path serves all of them.
IMAGE
Image generation
Image requests travel the same route: one model, its parameters, one job, one verified result.
Submitted from the console.
AUDIO AND SPEECH
Audio and speech
Speech and audio generation run on the same capacity market, with their own models and parameters.
Submitted from the console.
02 / MODELS
The models behind the marketplace.
A model joins UserBus as an exact identity: a model id and a version.
Minimax H3
The video model at the centre of UserBus. Requests for Minimax H3 are submitted from the console like any other model, matched to a provider whose declared runtime fits, executed under a lease, and verified before the result is delivered.
Video generation on UserBus runs on Minimax H3.
UserBus Video
The reference for video delivery on UserBus. It exercises the whole route from request to verification and returns the same clip for the same request, which makes it the anchor of a working video pipeline.
Available from the console.
03 / THE COMPUTE MARKET
Capacity behind every modality.
The same market serves video, image, audio and speech.
- 01
Providers supply
Independent providers run the UserBus worker and declare the exact runtime their hardware supports.
- 02
UserBus matches
Each job is offered to a provider whose declared model, version and runtime fit the request.
- 03
Verification decides
The uploaded result is checked for size, media type and digest before it counts as delivered.
- 04
Settlement follows
One settlement record is written per completed job, and providers are paid for verified work.
OPEN THE CONSOLE
Request generation work.
Choose a model in the console and submit the job. Providers see the other side of the same market.