Skip to main content

Personal pricing

Personal accounts pay for what each generation actually uses. 1 credit = $0.01. Charges are recorded as the generation runs, so you can watch your balance in Billing. New accounts start with $20 of credit; add more on the Billing page.

Starting a generation

A generation needs at least 100 credits ($1) available to start. A request with variations needs $1 plus $1 per requested variation; for example, an original with 4 variations needs $5 available. Without enough credits, the request returns 402 insufficient_credits. If your balance runs out while a generation is running, it stops and does not finish. Make sure you have enough credit for everything you submit, especially before a large batch.

Personal limits

A 21st POST /v1/assets while 20 are in progress returns 429 concurrency_limit_exceeded with Retry-After: 60; send it again once one of your jobs finishes. Polling and downloads are not affected. To queue more than 20, submit a batch instead. Gizmo starts batch items as your slots free up, so a batch never hits this 429. Each batch item is priced exactly like a single generation. At busy times an accepted job can wait in the queue for a short time before it starts.

Request rate limits

The API also limits how many HTTP requests a key can send. Rate-limited responses carry X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. On 429 rate_limit_exceeded, wait for Retry-After. This limit is separate from the number of generations in progress. GET /v1/usage shows each Personal key’s request counts and last use. It is not a bill; your balance and charges are on the Billing page.

Teams

Teams use the Team’s configured pricing and a Team processing limit shared by all of the Team’s batches and single generations. Submit as much as you need: items beyond the limit wait in the queue and start automatically. Do not resubmit queued items to make them start sooner.
  • Team variations accept variant_count from 1 to 9. If variations are not enabled for the Team, the request returns 422 appearance_variants_unavailable or asset_variants_unavailable; contact Antim to enable them.
  • Team batch and item responses report settled_spend_cents (charges recorded so far) and billing_status. Only complete means the charge is final. Older jobs can report reserved_spend_cents for credits held at the start.
  • Team batches accept an optional max_cost_cents that caps the batch’s total spend.
  • effective_max_concurrency on a batch reports the Team’s processing limit, not the number of free slots.
See Errors & troubleshooting for retry advice and Batches for submission examples.