What is it
Per-image pricing is a billing unit where each AI-generated image is metered, common in image generation APIs and multimodal AI platforms.
The headline “one image, one charge” is only a starting rate. What a vendor actually bills depends on which model generated the image (a cheap diffusion draft versus a flagship multimodal render) and, where exposed, the resolution or quality tier — dimensions that stack, so a tier or model swap silently resets the cost.
The corpus splits per-image pricing across two buyer types. Developer-facing APIs like Reka AI, Hyperbolic, and xAI price images as a modality alongside tokens — a separate line item per image submitted to or returned by a multimodal model, which lets a buyer forecast cost-per-output directly. Application platforms like Stability AI price images indirectly through credit pools, so the end user sees credits consumed per generation and has to back-calculate the underlying rate.
How it works
Per-image pricing works by charging a fee each time an image is generated and returned. The fee is set at the API endpoint (or model) level, so the caller controls cost by choosing the model and quality settings before the request is sent. Most platforms expose the rate in dollars per image; some expose it in credits per generation, and OctoAI historically layered an additional GPU-compute-second component that scaled with inference effort.
The dimensions that drive rate variation across the corpus:
| Dimension | What it controls | Example |
|---|---|---|
| Model tier | Base cost of inference — larger/newer models cost more per call | Reka Spark $0.005/image vs Reka Core $0.02/image |
| Resolution / length | Pixel count (and, for clips, duration) drive compute per output | MiniMax Hailuo $0.19–$0.56/clip across 768P–1080P and 6–10s |
| Inference steps | Diffusion quality level — more steps = higher fidelity, higher GPU cost | OctoAI SDXL: per-image base + per-compute-second overage |
| Output modality | Still image vs video clip — video is priced per clip or per second | xAI: still image $0.02–$0.05 vs video $0.05–$0.08/second |
| Credit abstraction | Whether the platform exposes dollar rates or hides them in credits | FLORA: dollar-denominated at $0.151/image (Nano Banana 2) vs Stability AI: credit units |
Unit math: Total image spend = (images generated) × (rate per image for that model/quality tier). For diffusion models with a variable compute meter (OctoAI historically): Total = (images) × (base per-image fee) + (total compute seconds) × (per-second rate).
A worked example using FLORA’s Pro plan: a 4-seat Pro team costs $200/month in seats (4 × $50/seat) and includes a $200/month pooled usage budget (4 × $50/seat included). At FLORA’s published Nano Banana 2 rate of $0.151/image, that pool funds roughly 1,325 images per month before any pay-as-you-go overage. If the team switches to a more expensive model from FLORA’s 60+ integrated options (such as Veo 3.1 for video), the same $200 pool covers far fewer generations. Because FLORA bills at published dollar rates rather than credits, the per-image rate — not a hidden credit conversion — is the variable to manage.
Companies using this
Seven companies in the corpus bill on a per-image unit, spanning developer inference APIs, multimodal platform APIs, and creative application subscriptions. Stability AI is the category-defining company — the originator of Stable Diffusion, which established per-image metering as the standard for AI image generation.
Patterns observed
Per-image is a line item bolted onto a token meter, never standalone. Every API-facing company here bills images alongside per-token text on the same card. Reka Core’s $2/M input tokens and its per-image rate ride one multimodal API; xAI’s grok-imagine sits beside grok-4.3’s $1.25/M input rate; MiniMax draws image-01 and its MiniMax-M2/M3 $0.30/M token rates from one prepaid USD balance. Per-image pricing is an extra meter layered on existing token infrastructure, not its own billing system.
Transparency at the API layer, opacity at the application layer. The API vendors — Reka AI, xAI, MiniMax, and the discontinued OctoAI — all publish explicit dollar rates. The application and infrastructure vendors don’t: Stability AI’s Brand Studio hides the rate behind credits, and Hyperbolic serves SDXL and FLUX but lists only its token and GPU-hour rates, never the per-generation image price. FLORA breaks the layer’s convention by billing at published dollar rates, selling that transparency to agencies that pass costs through to clients.
The rate spread runs past 40x. MiniMax’s $0.0035/image floor and FLORA’s $0.151 Nano Banana 2 ceiling bracket the corpus at roughly 43× apart — a developer embedding images in a pipeline versus a creative team paying for flagship quality. The gap tracks genuine model-capability and inference-cost differences, not pricing philosophy.
Counterexamples & variants
OctoAI’s dual meter shows the limit of a flat per-image rate. Before its October 2024 sunset (NVIDIA acquired the team), OctoAI priced SDXL, SD 1.5, and Stable Video Diffusion on a per-image fee plus a per-GPU-compute-second component — so a high-fidelity, high-step render cost more than a fast draft at the same resolution. It was the most honest model for diffusion, where two images at one resolution can differ sharply by inference depth, but commercially awkward: buyers budgeting per image couldn’t forecast the compute-second line, and after the acquisition the rate card vanished.
Credit abstraction breaks like-for-like comparison. Stability AI’s Brand Studio sells $50/month for 5,000 credits (free 1,000-credit Trial), but the images-per-credit ratio depends on model and quality settings governed by a separate, unpublished Platform API. A developer can’t compare providers on a level field when one quotes dollars-per-image and the other quotes credits-per-month with no public conversion — opacity that softens price competition for the vendor and burdens the buyer, and exactly the pattern FLORA’s dollar-rate billing rejects. xAI is a different variant: grok-imagine is a feature extension on a platform whose real meters are token rates and per-1k-call agentic tools like X Search ($5/1k), so per-image is a convenience add-on, not a core value metric.
What this means for buyers vs vendors
For buyers
Price the model tier you will actually ship at, not the headline rate — the same platform can be 4× apart across its own model family. Confirm the published rate covers your resolution and quality, and flag anything you can’t forecast from the public page: a compute-second component (OctoAI’s old model) or an unpublished image rate (Hyperbolic). Weighing a credit subscription against pay-as-you-go API billing, model the break-even: for spiky or exploratory workloads, transparent per-image billing usually beats prepaying a credit bundle and forfeiting the unused balance. See the usage-based pricing fundamentals guide for the break-even math and choosing the right usage metric for when a per-output unit fits better than per-token or subscription. For xAI, the xAI pricing calculator models token-plus-media cost.
For vendors
Tier your rate card by model and quality — one flat rate either underprices flagship renders or overprices drafts and pushes buyers away. A per-model ladder (Reka AI’s) lets buyers self-select their tier while you hold margin at the top. Decide deliberately between raw dollars and credits: credits blunt direct comparison but breed the opacity sophisticated buyers, especially agencies, distrust — FLORA shows transparency can be the sales argument. For variable-depth diffusion workloads, OctoAI’s per-image-plus-compute hybrid was more accurate but harder to sell; a fixed draft / standard / high-fidelity ladder is the legible alternative.
| Company | Product | Pricing model | Billing units | Free tier | Verified |
|---|---|---|---|---|---|
| Adobe | Adobe's generative-AI monetization — Firefly (image/video/audio generation billed in generative credits) and GenStudio (enterprise gen-AI content platform) | Yes | 2026-08-06 | ||
| DeepInfra | Serverless inference cloud — per-token LLM/embedding APIs, per-image and per-minute media models, per-hour on-demand GPU containers, and reserved DeepCluster GPU clusters | No | 2026-08-04 | ||
| FLORA | AI-powered creative canvas and workflow platform | Yes | 2026-07-23 | ||
| MiniMax | Foundation models, MiniMax-H3 video & per-token API | Yes | 2026-08-04 | ||
| OctoAI | Generative AI inference platform (acquired by NVIDIA, sunset Oct 2024) | No | 2026-07-30 | ||
| PhotoRoom | AI image-editing app and per-image Image Editing / Remove Background API for e-commerce product visuals | Yes | 2026-07-22 | ||
| Reka AI | Natively multimodal models (Edge, Flash, Core) + Research & Vision APIs | Yes | 2026-07-22 | ||
| Stability AI | Brand Studio creative platform and open generative media models | Yes | 2026-06-11 | ||
| Together AI | AI Acceleration Cloud — serverless inference, dedicated endpoints, GPU clusters, Code Sandbox, fine-tuning | Yes | 2026-08-04 | ||
| xAI | Grok API and agentic AI stack | Yes | 2026-08-04 | ||
| Zhipu AI | GLM foundation models, per-token API, and GLM Coding Plan | Yes | 2026-07-22 |
Explore this theme in the knowledge graph
FAQ
What is per-image pricing in AI?
Per-image pricing charges a fee for each AI-generated image, regardless of how long it takes to produce. The rate varies by model, resolution, and inference quality — a cheap diffusion draft and a flagship render can differ by more than 40x in cost across the corpus, even before resolution and step-count effects are added.
How much does AI image generation cost per image?
Published rates span more than two orders of magnitude. MiniMax's image-01 costs $0.0035 per image at the budget end; Reka Spark charges $0.005 and Reka Core $0.02; xAI's grok-imagine runs $0.02–$0.05; FLORA's proprietary Nano Banana 2 is $0.151 per image. Stability AI's Platform API and Hyperbolic's SDXL/FLUX rates are not published on their public pricing pages.
Does the resolution or model choice affect the per-image price?
Yes — significantly. Most vendors tier per-image rates by model. Reka AI charges $0.005 per image on its Spark model but $0.02 on Core, a 4x jump for the same platform. MiniMax's Hailuo video is $0.19–$0.56 per clip depending on resolution (768P–1080P) and length (6–10s). OctoAI (historical) priced SDXL per image plus a GPU-compute-second component that scaled with inference effort.
How is per-image pricing different from credit-based pricing?
Per-image pricing charges a transparent dollar amount per generated image. Credit-based pricing converts the image cost into an opaque credit unit, then sells credits in bundles. Stability AI's Brand Studio uses credits ($50/month for 5,000 credits), while FLORA explicitly bills at published dollar-per-image rates rather than credits — a transparency choice that lets agencies bill clients directly from usage history.
Is per-image pricing or subscription better for image generation?
Per-image pricing is better for variable workloads where generation volume is unpredictable or spiky. Subscriptions (like Stability AI's $50/month Core plan with 5,000 credits) are better for consistent, high-volume use where you want a predictable monthly ceiling. FLORA's hybrid — a subscription that includes a dollar-denominated usage pool — combines both, giving predictability up to the pool limit and pay-as-you-go above it.
Related billing units
- Credit-Based BillingA billing unit where customers pre-purchase or are allocated a pool of credits that deplete as they use the product, often at variable rates per feature.
- Token-Based PricingA billing unit common in LLM and AI products, where customers are charged per input and output token processed.
- Per-Seat PricingA billing unit where the vendor charges a fixed fee per named user, regardless of how much each user consumes.
- Per-Resolution PricingA billing unit unique to AI customer-support products, where the vendor charges only when an AI agent resolves a customer issue without escalation.
- Bandwidth-Based PricingA billing unit where customers are charged per gigabyte of data transferred out of the platform.
- Per-Function-Invocation PricingA billing unit where customers are charged per serverless function invocation, often combined with a separate compute-time charge.
- CPU-Hour PricingA billing unit where customers are charged for the CPU time their workloads consume, typically measured in vCPU-seconds or vCPU-hours.
- GB-Hour PricingA billing unit where customers are charged for the memory their workloads consume over time, measured in gigabyte-hours.
- GPU-Hour PricingA billing unit where customers are charged for GPU time consumed, typically measured per-second or per-hour by GPU type.
- Per-API-Call PricingA billing unit where customers are charged per API request, regardless of payload size or processing time.
- Per-GB Storage PricingA billing unit where customers are charged per gigabyte of data stored on the platform per month.
- Media-Minute PricingA billing unit where customers are charged per minute of audio or video processed — used by speech, voice, and video AI vendors.
- Per-Request PricingA billing unit where customers are charged per request served — the generic meter for inference endpoints, search, scraping, and browser infrastructure.
- Per-Event PricingA billing unit where customers are charged per event ingested — the native meter of observability and billing-infrastructure platforms.
- Vector Storage PricingA billing unit where customers are charged for vectors stored or indexed — the storage dimension of vector database pricing.
- Per-Character PricingA billing unit where customers are charged per character of text processed — the standard meter for text-to-speech and translation.
- Per-Document PricingA billing unit where customers are charged per document processed or generated — common in AI writing, SEO, and document-intelligence tools.
- Per-Page PricingA billing unit where customers are charged per page crawled, parsed, or rendered — the meter for web scraping and document parsing.
- Per-Transaction PricingA billing unit where customers are charged per financial or billing transaction processed — the meter of billing and accounting platforms.
- Active-User PricingA billing unit where customers are charged per monthly or daily active user rather than per provisioned seat.
- Per-Task PricingA billing unit where customers are charged per task an automation or agent executes — Zapier's historical unit, now spreading to AI agents.
- Per-Unit PricingA billing unit used by robotics, hardware AI, and some SaaS companies where the metered object is a physical or abstract 'unit' — a robot deployed, a device sold, or a defined deliverable.
- Workflow Execution PricingA billing unit where each end-to-end workflow or automation run is metered and billed, regardless of the compute steps it contains.
- Per-Message PricingA billing unit where each individual message or reply in a conversation is metered, common in AI chat and voice platforms.
- Per-Invoice PricingA billing unit used by billing infrastructure platforms where each invoice generated or processed is metered as the primary cost driver.
- Per-Action PricingA billing unit where each discrete action taken by an AI agent or automation is metered — common in browser automation and agentic workflow tools.
- Per-Conversation PricingA billing unit where each complete customer conversation — from first message to resolution — is metered as a single chargeable event.
- Per-Record PricingA billing unit where each data record processed, labeled, or extracted is metered — common in data platforms and web scraping services.
- Per-Word PricingA billing unit common in translation and localization platforms where the metered object is the word count of content processed.
- Per-Video PricingA billing unit where each AI-generated video is metered, common in video generation and synthetic media platforms.
- Milestone-Based PricingA billing unit used in drug discovery and biotech AI where payment is tied to achieving defined research milestones rather than time or compute consumed.
- Per-Outcome PricingA billing unit where payment is triggered by verified outcomes delivered — distinct from outcome-based pricing models, this refers specifically to 'outcomes' as a countable billing unit.
- Per-Datapoint PricingA billing unit where each individual data measurement or signal ingested is metered — common in cloud cost intelligence and ML evaluation platforms.
- Per-Interaction PricingA billing unit where each patient-agent or user-agent interaction is metered, common in healthcare AI and customer engagement platforms.
- Data Licensing PricingA pricing structure where access to proprietary datasets or data assets is licensed separately from the software or services, common in AI training data and clinical data platforms.
- Robot-Hour PricingA billing unit where each hour a robot or autonomous system operates is metered — the robotics equivalent of a GPU-hour.
- Per-Contact PricingA billing unit where each contact or lead in the database is metered, common in AI sales development and outbound automation platforms.
- Per-Mailbox PricingA billing unit where each connected email mailbox or sending account is metered, common in AI outbound sales and email automation platforms.
- Browser-Hour PricingA billing unit where each hour of headless browser compute time is metered, common in web scraping and browser automation platforms.
- Per-Generation PricingA billing unit where each AI-generated creative asset — image, video, or design — is counted as a 'generation' and metered accordingly.
- Per-Ticket PricingA billing unit where each customer support ticket handled by an AI agent is metered — common in AI customer service platforms.
- Per-Log PricingA billing unit where each LLM request log ingested or stored is metered — common in AI observability and evaluation platforms.
- Per-Trace PricingA billing unit where each distributed trace — a complete record of an LLM request chain — is metered, common in AI observability platforms.
- Per-IP PricingA billing unit where each IP address or proxy endpoint allocated is metered — used by web scraping proxy providers.
- Per-Device PricingA billing unit where each hardware device or endpoint connected to the AI platform is metered.
- Per-Case PricingA billing unit used in legal AI platforms where each case or matter processed by the AI is metered.
- Per-Report PricingA billing unit where each AI-generated report or analysis document is metered as a discrete output.