Billing
MoonNexAI charges depend on the model, action, resolution, duration, output count and task status. Consult the console and API billing records for actual charges.
Billing dimensions
| Capability | Typical billing dimensions |
|---|---|
| Text, chat and visual understanding | Model and usage. |
| Image generation | Model, image size and output count. |
| Video generation | Model, duration, aspect ratio, resolution or output count. |
| Assets | OSS test uploads and asset authentication are free where available; generation is billed by its model. |
| Digital humans | Avatar, voice, audio and video tasks use the corresponding model or action policy. |
| Music / Suno | Music, lyrics, sound effects and post-processing use the model or action policy. |
Task status and charges
| Status | Meaning |
|---|---|
queued / running | Processing is ongoing; wait for a final state. |
succeeded | Completed and billed according to the task policy. |
failed | Consult the final billing record for the outcome. |
canceled | Cancellation charges follow the policy shown in the console. |
When retrying a task, save the original task_id, request parameters and the new task_id to reconcile the results.
Asset billing
| Action | Billing rule |
|---|---|
Upload to MoonNexAI OSS with mode=oss / mode=both | Free where available. |
Asset authentication and model asset ID preparation with mode=asset / mode=both | Free where available. |
| Video or other generation | Billed according to the generation model. |
MoonNexAI OSS supports integration testing. It does not promise long-term file retention, permanent URLs, continuous availability or a long-term storage service level. For production or long-term use, keep media in your own storage and provide direct URLs that remain publicly accessible without login or extra headers throughout task execution.
Result URL formats follow the API response. Save the final URL and original response in your application for subsequent queries and reconciliation.
Recommendations
- Check your balance, quota and model permissions before submitting a task.
- Save every
task_idfor status queries and billing reconciliation. - For long tasks, use webhooks where supported and retain polling as a fallback.
- For batches, record the model, output count, duration and final status for each task.
Current prices
The console displays your balance, model permissions, available quota and current prices. Documentation does not fix monetary amounts; the current console configuration and actual billing record apply.