IMAGE API GUIDE

Generate images through the TokenAAS API

Choose an available image model, validate its size constraints, and send an authenticated generation request.

Updated 2026-09-10

In brief

TokenAAS image generation uses POST /v1/images/generations with a public image model ID, a prompt, and a supported size. Billing follows the configured per-request or image-tier price.

Request workflow

Confirm that the image model is visible to the API key, then send the prompt and a supported size to the image generation endpoint.

  • Use the exact public model ID
  • Respect model-specific minimum dimensions
  • Limit batch size to documented values
  • Store the response or download the returned asset promptly

Billing checks

Record the account balance before and after a test request, then compare the TokenAAS usage record with the configured image price.

Production handling

Validate content type and file size before saving generated output. Do not expose the API key in browser-side code.

Frequently asked questions

Why does an image request reject 1024x1024?

Some upstream image models require a larger minimum pixel count. Use a supported size shown in the model documentation or error response.

Is image usage billed by tokens?

Image routes are billed using the configured image request or image tier rather than text token rates.