Skip to main content
Every leading image, video, and audio model behind one endpoint, one key, and one bill. Browse the model catalog, pick a model, and ship — the same key and the same job lifecycle work for all of them.

​
Step 1: Create an API key

Generate a key in the developer console. Every request authenticates with it:

​
Step 2: Fund the API wallet

The API bills a prepaid wallet held in US dollars. It is separate from your Hedra Studio balance, and a workspace starts with $0.00 in it — nothing you buy or hold in Studio moves money into it. Until it is funded, every generation is refused with 402 INSUFFICIENT_BALANCE. Add funds in the developer console, and read the wallet any time with GET /balance.
Uploading inputs with POST /files is free and works on an empty wallet, so you can stage a request end-to-end and only meet the billing gate at submit.

​
Step 3: Pick a model

GET /models lists every model with its id and human name, so a model you know by name (“GPT Image 2”) maps straight to the id you submit to (gpt-image-2). Each model publishes its typed input schema at GET /models/{id}/openapi.json.
To know the price before you run, ask for an estimate:

​
Step 4: Submit, poll, download

Every generation follows the same lifecycle: submit a job, poll it, then read the output URL.
Generated media is retained for 48 hours after a job completes — download outputs to your own storage, or chain them into the next job by asset_id.

​
Next steps

Model catalog

Every model behind the endpoint, with ids, names, and what each one is for.

Chain generations

Reuse a completed job’s output as an asset in the next submit.

Quality levels

How the quality tiers map to cost and latency across models.

​
Enterprise

For volume pricing and custom limits, talk to us.