Credit Costs

Every generation deducts credits from your team's balance at submission time. If a job fails, the credits are automatically refunded.

You can check your current balance via the Account endpoint or in the Apiframe console.

Image generation

Models tagged × n multiply by the number of images requested in the call (n, number_of_images, or num_images depending on the model).

AI Photos (LoRA training)

POST /v2/loras — train a Flux LoRA from 15-30 subject photos.

Video generation

Per-clip pricing

Per-second pricing

credits = rate × duration. The route probes the requested duration (or input video length, for wan-2.7-r2v) and bills accordingly.

Image editing

POST /v2/images/upscale, POST /v2/images/background-remove, POST /v2/images/edit — Upscale, background removal, inpainting and outpainting.

The Topaz output-megapixel tier is computed automatically from the input image's dimensions × upscale_factor² and rounded up to the next configured row.

Video editing

POST /v2/videos/upscale — Topaz video upscale and frame interpolation.

Pricing is per second of input video, tiered by output resolution × output fps. The route probes the input duration via ffprobe at submit time and charges cost-per-second × ceil(duration).

Music generation

How credits work

• Deducted at submission — credits are reserved the moment you send a generation request.
• Refunded on failure — if a job fails (provider error, content policy violation, etc.), the full credit cost is returned to your balance.
• Snapshotted per job — the creditCost field on a job reflects the cost at the time of submission, even if pricing changes later.
• Team-scoped — credits belong to your team, not individual users. All team members share the same balance.

Checking your balance

curl https://api.apiframe.ai/v2/me \
  -H "X-API-Key: afk_your_api_key_here"

The response includes your current credit balance:

{
  "id": "...",
  "email": "...",
  "team": {
    "id": "...",
    "credits": 850
  }
}