ONE ACCOUNT. ENDLESS POSSIBILITIES.

More models.
Less friction.
Just build.

Text, images, video and music. One API, transparent credits, and a more reliable way to create.

Pay as you goOptional fallbackOne API key
DEMO
01 / REQUEST
POST /v1/tasks
{ "model": "reel-video-2" }
02 / OUTPUTExample result
16:9 · 720p · 5sConcept preview
03 / CREDITS

Estimated · standard route

25credits
A preview of what’s next. All models and prices on this site are illustrative.
/ THE MODEL COLLECTION

Find your next creative engine.

All models
/ BUILT FOR DEVELOPERS

One integration.
Room to explore.

A familiar interface for language models. A consistent task lifecycle for images, video and music. Less glue code, more time to build.

  1. 01
    Create an API key

    One credential for your whole model stack.

  2. 02
    Choose your model

    Compare capabilities and channel prices.

  3. 03
    Submit. Track. Create.

    Every attempt and every credit, accounted for.

curl https://api.example.com/v1/tasks \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: my-first-generation" \
  -d '{
    "model": "reel-video-2",
    "input": {
      "prompt": "Sunlight over a quiet ocean",
      "duration_seconds": 5
    },
    "output_count": 2,
    "fallback": true
  }'
Contract preview · example domain · call from your server only.
01

Less to manage.

One key and one credit balance across every modality. Switch models without rebuilding your account infrastructure.

02

A plan for failure.

Start with a lower-cost channel. Opt into an eligible official fallback, with the maximum price visible before you run.

03

Know what you paid.

Trace every attempt. Settle each successful item at its final channel price. Release unused reserved credits.

/ NO GUESSWORK

Reserve first.
Settle what succeeds.

Buy credits in USD. Know the range before you run. Failed items release their reserve; successful items carry their actual channel price.

Explore pricing
EXAMPLE · 4 IMAGE RESULTS240 credits reserved
Image 01Standard success20 cr
Image 02Standard success20 cr
Image 03Official fallback success60 cr
Image 04Failed · released0 cr
100 credits settled140 released

A few things worth knowing.

How do credits work?+

Purchase credits in USD, then use the same balance across models. Each successful execution item is settled at its final channel price. Prices displayed here are examples.

What happens when a provider fails?+

When you enable fallback, a confirmed provider failure can switch to an eligible official channel. Official routes may cost more; your maximum reserve is shown before you submit.

Can one request generate multiple results?+

Image and video requests accept output_count from 1 to 4. Each item runs and settles independently. Music models can return two tracks, each with its own audio, cover and metadata.

Do I pay for failed attempts?+

No separate inference charge is made for failed attempts. A fully failed item releases its reserved credits. Successful items in a partially successful request are billed normally.

Can I try this before connecting a real API?+

Yes. Use a model playground or explore the console in demo mode. No upstream model is called and no real payment is collected in this preview.

YOUR NEXT IDEA STARTS HERE

Make the first call.

Create your accountExplore the demo console