01

Credits are a budget, not an output guarantee

Studio allocates plan credits, while generation models, retries, mesh work, textures and other operations can change the cost of a finished asset. The useful metric is total spend divided by exports that pass your real validation.

  • Record the balance before and after a complete job.
  • Include failed attempts and refinements.
  • Add cleanup time when comparing usable-output cost.
02

Which plan should you choose?

Free is the correct first step for most new users. Pro is the practical paid benchmark for a regular solo creator. Max only makes sense after measured volume or concurrency exceeds Pro, while Team is about shared workspace and administration rather than a better single output.

  • Upgrade for a proven limit, not curiosity.
  • Do not buy volume to fix poor inputs.
  • Recheck the checkout total and renewal cadence.
03

Privacy, downloads and renewal checks

Free output is currently described as public, while paid plans list private models and commercial use. Confirm the active privacy control, download availability, storage history, cancellation timing, taxes and unused-credit treatment before payment.

  • Do not use confidential references in a public workflow.
  • Download important assets and keep local source files.
  • Archive the terms used for commercial work.
04

Studio subscription versus API billing

Studio is the interactive creator product. The API is a separate developer platform with its own credentials, endpoints and usage cost. A Studio model estimate should not be used as an API budget.

  • Price endpoint calls, retries and polling separately.
  • Protect API keys server-side.
  • Confirm rate, retention and model-version rules in developer documentation.