How OfflineCreator MCP generation pricing works

Account for failure and human purchase boundaries

The pricing and product pages state that provider failures return reserved credits. The published MCP package lists cancel_generation among its nine tools, and product copy documents refunds for failed jobs, but this research did not test timing or every provider state. Verify the job and ledger after a failure or cancellation rather than assuming an automatic balance change completed.

Top-up discovery and Checkout creation remain human browser actions on the pricing page; the published MCP tool list covers model discovery, balance checks, generation, upload, status, wait, download, cancel, and history, not payment tools. Engine web and social coverage was degraded and supplies no evidence about typical spend, savings, or customer value, so none is claimed.

Procurement should compare a documented workflow envelope with current plan and top-up rules, not divide a plan balance by the cheapest model and call the result expected output. Record monthly versus annual treatment, expiring versus non-expiring credits, concurrency needs, tax handling, and who may complete Checkout. Refresh every input from the current pricing page and published model catalog before purchase.

Price the selected model in credits before generation

OfflineCreator uses one Studio credit balance across web, MCP, CLI, and API generation. The current published catalog prices FLUX Schnell at 1 credit, FLUX 1.1 Pro Ultra at 8, Recraft V3 at 5, Kling 2.6 Pro at 42, Kling 2.6 Pro Motion at 42, and Veo 3.1 Fast at 96 per generation. These are current product values from the live pricing and MCP product pages, not a permanent catalog or a quality ranking.

Use list_models and get_credits before submission. Budget by the exact workflow and model rather than an average image or video price. A 96-credit video attempt consumes a very different share of a plan than a 1-credit draft, and mixed-model iteration changes any simple yield estimate. The published MCP package exposes those discovery tools alongside generate and lifecycle tools; it does not invent a different credit ledger for agents.

Estimate a workflow without turning it into a promise

Start with a concrete production plan rather than the marketing shorthand for a plan's maximum yield. List the models the workflow may use, their current credit costs, the number of draft attempts allowed, and any final video or animation pass. Multiply each model cost by its approved attempt count, then reserve a margin for a revised prompt or a different aspect ratio. The arithmetic describes a budget envelope; it does not predict how many outputs will pass creative review.

Compare that envelope with the plan balance and concurrency needed by the team. Concurrency controls how many generations can run at once, while credits control how much catalog work the account can reserve over the period. A team doing many low-cost image drafts and an occasional premium video has a different consumption pattern from a team using only one model, so the pricing page's single-model examples should not be combined into a mixed-workflow guarantee.

Document what happens at the edges. Monthly credits expire with the billing period, top-ups do not expire and are used after plan credits, and annual credits follow the annual rule shown on the current pricing page. Keep top-up purchasing human-controlled, verify the balance after documented provider-failure credit returns, and refresh every model and plan value before using this page for a later procurement decision.

For example, eight FLUX Schnell drafts at one credit, two FLUX 1.1 Pro Ultra refinements at eight, and one Kling 2.6 Pro clip at forty-two create a 66-credit envelope before contingency. That arithmetic uses the cited catalog values and makes the model mix visible. It does not predict that eight drafts, two refinements, or one clip will be sufficient or acceptable.