Skip to main content
Rendobar’s Generation API creates new media from a prompt on hosted diffusion models. It is one of the platform’s products, and it submits, runs, and returns like every other job. You describe what you want, the job runs on a GPU, and the result comes back as a signed file URL.

Modalities

Images are the first modality. You can generate an image from a text prompt, or edit existing images from a written instruction.

Image generate

Turn a text prompt into a webp image. Pick a tier or pin an exact model.

Image edit

Edit one to four reference images from a plain-language instruction.
More modalities will join the same surface over time. Only image generation and editing are available today.

Tiers or exact models

Every generation job takes a model. You can name a tier and let the platform choose, or pin an exact model id.
  • Tiers (economy, standard, premium) express a price and quality posture without naming a model. Omit model and you get economy.
  • Exact ids (for example qwen-image-2512) pin the model and unlock its own controls, such as denoise steps, guidance, and a negative prompt.
Tier aliases can be re-pointed to newer models as the catalog grows. Pin an exact id when you need a result to stay stable across that change.

Discover models

GET /models returns the live catalog: every model with its supported jobs, tier, relative price, capabilities, and step range. Filter to one job type with ?job=. Build a model picker against this endpoint instead of hardcoding the list.
priceTier compares models against each other, from $ to $$$$. It is not a per-image charge, because jobs bill on the compute they actually use, cost-plus. See credits and billing. A model with underReview: true is pulled from tier resolution while we re-evaluate its cost and quality. It stays listed so a caller pinning it can see why the submit was rejected, but no tier resolves to it and pinning it returns VALIDATION_ERROR.

Same job, same shape

A generation job is a job like any other. You submit it to POST /jobs, it runs async, and you poll, wait, or receive a webhook. The image jobs return a single webp file in output.file, with output.data set to null. One thing is specific to generation. While the model denoises, the job emits job.preview events carrying a small frame of the image as it resolves, so a client can show the picture arriving instead of a spinner. Previews are decoration: they are never replayed, and a model can emit none. See watch it render.

See also