Unified AI generation API
Use one request contract across image, video, audio, and 3D routes.
OfflineCreator compares compatible AI generation routes, selects a reliable option near the lowest available cost, and runs it through one Studio, CLI, MCP server, or API.
Think Kayak for AI generation—built to book the route, not just list it.
Cloud generation. The selected provider is disclosed before submission.
Best balance of cost and health
Inside the 10% cost band
Configured price ceiling
Signed before generation. Failover cannot raise this charge.
qte_••••7f2aOfflineCreator changed how creators generate — images, video, 3D, and whatever comes next. One request. Multiple routes. One locked price. We comb cloud providers for eligible routes, pick a healthy lane near the lowest cost, and lock the credit charge before generation starts.
A generation can pass through a model owner, inference provider, subscription platform, and agent interface before it reaches you. Every layer can package the same work differently, so a credit balance rarely reveals the real cost of one result.
A directory tells you what exists. A router normalizes the choices, commits to one route, and executes the generation.
You choose the model and settings. The router handles route economics and reliability while keeping the model ID stable everywhere you work.
Model, workflow, inputs, duration, resolution, and options define which routes are truly compatible.
Current rate cards and route health are normalized. Reliability decides among routes within 10% of the cheapest eligible cost.
A signed quote records the selected route, options, rate card, credit charge, and expiry before credits move.
The selected provider runs the job. Actual usage is recorded without increasing the customer charge.
Reliability should not create surprise charges or duplicate jobs. The routing contract stays attached to the generation from quote through final usage reconciliation.
See Studio credit pricingChanging a model or material option requires a fresh quote. The reserved charge matches the quote you approved.
A safe alternate route can run only after a definitive failure, and it cannot raise your locked price.
If submission may have succeeded, Studio reconciles that attempt instead of launching a second paid generation.
Studio, REST, CLI, and MCP share the same model catalog, account credits, signed quotes, generation history, and provider disclosures.
$ npx @offlinecreator/mcp quote \
--model seedance-2-5-text \
--options '{"duration":5,"resolution":"720p"}'
✓ quote locked · provider disclosed
✓ token qte_••••7f2a · expires in 5m
$ npx @offlinecreator/mcp generate \
--model seedance-2-5-text --quoteToken qte_••••7f2aAggregators broaden access. OfflineCreator adds price discovery and execution: compatible routes are compared for the same generation request, one route is selected, and the customer charge is locked before work begins.
Start with the unified request contract, then inspect cost normalization, provider failover, and the rate cards behind a locked quote.
Use one request contract across image, video, audio, and 3D routes.
See how eligible routes are normalized before price and reliability are compared.
Keep retries inside the quoted capability, policy, and price envelope.
Translate provider rate cards into comparable generation costs.
Choose disclosed provider routing or fully on-device generation.
Public model names stay the same in Studio, CLI, and MCP. The router selects a healthy eligible route and locks the credit charge before generation starts.
An AI generation router compares compatible provider routes for an image or video request, selects an eligible route using current cost and reliability data, and submits the generation through one interface.
No. The public model ID and requested workflow stay fixed. The router selects among configured provider routes that support that model and its requested options.
No. Studio signs and reserves the customer quote before submission. A safe alternate route can be used only inside the locked cost envelope, so failover does not increase the approved charge.
Yes. Studio, REST API, CLI, and MCP use the same model catalog, account credits, signed quote flow, generation history, and provider disclosures.
No. Routing still uses disclosed cloud providers, and required prompts or source assets are sent to the selected provider. LocalForge is the separate fully offline option.
Choose a model and settings in Studio. OfflineCreator will compare the eligible routes and show the exact credit charge before you generate.