Running batch jobs through the Meshy API can use up credits quickly if usage isn't planned ahead of time. This guide covers how to estimate costs before you run a large batch.

Each generation task consumes credits based on the stage involved—preview generation, refine generation, and texture generation are typically priced separately. Understanding which stages your workflow uses is the first step in estimating cost.

Preview generations are usually cheaper and faster, useful for quickly evaluating a concept. Refine generations produce a higher-quality final result and typically cost more credits. Consider previewing first before committing to a refine pass at scale.

Failed tasks and retries can add to your credit usage. Build in checks for task status before retrying automatically, so failures don't silently multiply cost.

To estimate the cost of a batch run, multiply the per-task credit cost by the number of tasks, accounting separately for preview, refine, and texture stages if your workflow uses more than one.

Check your account's credit balance regularly during a batch run, especially for large or long-running jobs, so you can pause if usage is higher than expected.

Cost varies by task type and stage (preview, refine, texture). See the related article below for exact figures.

This depends on the failure point—check the related article and API documentation for details, and monitor your balance during retries.

Run a small batch first to confirm your workflow and cost estimate before committing to a large run.