1. Get Started
PixVerse Platform Docs
  • Get Started
    • What Is PixVerse AI?
    • Model Capability Map
    • Billing and Usage
    • Quick Start
    • Contact Us
    • Privacy and Data Protection
  • API
    • Preparation
      • Start Here
      • Concurrency Rules
      • Query Task Status
      • Error Codes
      • FAQ
      • Webhook Callbacks
      • Upload Image
      • Upload Media (Video and Audio)
      • Verify Uploaded Audio
      • Get Effect Template List
      • Get TTS Speaker List
      • Get Restyle Effect List
      • Query Task Status
      • Get Account Balance
      • Usage Deduction Query
      • Create Custom Voice
      • Delete Custom Voice
    • Core Capabilities
      • Text-to-Video
      • Image-to-Video and Video Templates
      • First and Last Frame Video
      • Reference-to-Video (Fusion)
      • Multi-Transition Video
      • Video Extend
      • Image Template Generation
      • Get Image Generation Result
    • Solutions
      • Video Upscale
      • Video Restyle
      • Lipsync
      • Video Edit (Modify)
      • Image Avatar
      • Select Video Mask
      • Sound Effect
      • Subject Replacement (Swap)
      • Motion Control (Mimic)
      • One-click Real Estate Video
      • One-click VibeMV
  • Pricing
    • PixVerse API Pricing
  • Changelog
    • Changelog
  1. Get Started

Billing and Usage

PixVerse API usage is measured in Credits. Review the account balance, usage records, and purchases in the PixVerse API Platform.
For current model and capability rates, see Pricing > PixVerse API Pricing in this documentation.

Where to Check Usage#

ItemLocation
Credit balance, usage records, and purchasesPixVerse API Billing
Current balance through the APIGET /openapi/v2/account/balance
Model and capability pricingPricing > PixVerse API Pricing

How Billing Works#

The Credit amount depends on the selected model, resolution, duration, optional audio, video-reference mode, and capability.
A creation endpoint may return Resp.credits. Use this value for display and preliminary reconciliation. Valid debit and refund records in the account ledger are the final charging record. Promotions, free allowances, refunds, or asynchronous settlement may cause the final balance change to differ from the value returned when the task was created.
For a failed task, a callback may trigger an immediate idempotent refund, with delayed processing as a fallback. Treat the refund as complete only after the refund record appears and the account balance is restored.

Recommended Reconciliation Fields#

Record the following for each task:
API account
video_id
Request time
Ai-trace-id
Resp.credits
Final task status
Credit balance before and after the request

Notes#

Keep API Credits separate from PixVerse consumer-app subscriptions.
Do not treat Credit values in response examples as fixed prices.
Review the Billing ledger when a failed, moderated, or timed-out task appears to have been charged.
HTTP 200 and ErrCode=0 confirm that the creation request was accepted; they do not confirm that generation completed.
Previous
Model Capability Map
Next
Quick Start