Guide
Pricing & credits
Image packs, the free grant, and how failed jobs are refunded.
Billing is quoted in images, not credits. One image is the unit of work and the unit of billing: one render of one photo costs one image.
Free images
Creating your first API key adds 50 free images to the account. That is enough to build and test an integration end to end. The grant applies once, to your first key — creating a second key does not add more.
Until the account buys a pack, every render carries a Roomagen watermark: the free images are for building and testing, not for publishing. Once a pack is paid for, every new render is watermark-free — the free images you have left included. Renders made before that keep their watermark, and a pack that is fully refunded no longer counts.
Packs
Images are bought up front, in packs (Pilot, Growth and Scale in the portal):
| Images | Price | Per image |
|---|---|---|
| 500 | $125 | $0.25 |
| 2,500 | $550 | $0.22 |
| 10,000 | $2,000 | $0.20 |
| 50,000+ | Contact us | — |
Packs do not expire and they stack — buying a second pack adds to the balance you already
have. GET /v1/account reports what is left in image_credits.
What a job costs
Each documented tool costs one image per render at the default 2K resolution. Rendering at
resolution: "4K" doubles that to two images.
POST /v1/jobs charges as soon as the job is accepted and reports the charge as
images_charged.
Refunds
A job that fails during generation is refunded automatically — you are not billed for a render you did not get.
images_charged on the job is not rewritten when that happens, so read it as what was charged
at creation rather than the net effect on your balance. GET /v1/account is the authority on
what you have left.
Where to buy
Packs are bought in the portal at /portal/credits — pick a pack, pay by card through our payment partner, and the images land on your balance within a minute. Receipts are emailed automatically. Volume above 50,000 images is priced case by case — email [email protected] with your monthly figure and what you are rendering.
Next step
Changelog — what shipped, and how breaking changes are announced.