Model Pricing and Usage-Based Billing

WisGate CN uses independent model-based pricing: after you add account balance, each request is charged by the selected model, input/output usage, task type, and actual consumption. Records are traceable for budgeting and reconciliation.

Billing method
Model usage
Account balance
Prepaid
Reconciliation
Usage logs
Procurement
Contract/invoice

Choose the right starting path for your usage scale

For small tests, add balance and start calling models. For production traffic, team procurement, and larger budgets, contact sales to discuss pricing, contracts, invoices, and postpaid billing.

Pay as you go

Recharge your balance and pay only for actual model usage.

  • No subscription or monthly commitment
  • Top up the balance amount you need
  • Balance is deducted as you use it

Sales and procurement

If you are evaluating production traffic, team procurement, or a larger budget, we recommend confirming the model mix, pricing basis, billing cycle, and reconciliation workflow with sales before launch.

Pricing
Contract rate
Terms
Monthly / postpaid
Materials
Contract / invoice

Trace every step from balance to reconciliation

  1. Add balance

    Add balance in the console. Once it arrives, it can be used for model calls.

  2. Call models

    Use the unified API to call text, image, video, speech, and related models.

  3. Meter usage

    The system deducts by model price, input/output usage, task units, and actual consumption.

  4. Reconcile records

    Review consumption and request status through usage logs and billing records.

Different models use their matching billing units

Text models are commonly billed by input and output tokens. Image, video, speech, and other models may use request count, image count, duration, pixel tiers, or result-based units. Use model details and usage logs as the source of truth.

View model gallery

Standard failures are free

Network, timeout, or upstream errors are usually not charged as successful results.

Policy handling fee

Video jobs that fail because prompts violate platform policies may incur a ÂĨ0.01 handling fee.

Logs are the source

Whether a charge applies is ultimately based on usage logs, task status, and billing records.

Usage, balance, contracts, and invoices stay traceable

Review call records, balance changes, and bills to reconcile model usage and costs. Enterprise projects can also confirm invoices, contracts, and reconciliation documents.

Traceable Usage Logs

Usage logs show model, time, consumption, and status for troubleshooting and attribution.

Clear Balance Records

Top-ups, consumption, and balance changes are recorded for budget control.

Invoice Support

Invoice materials can be prepared based on top-ups, usage, or contract terms.

Contracts and Postpaid

Enterprise procurement can discuss contracts, postpaid billing, monthly reconciliation, and dedicated support.

Contract pricing and price sheets

Discuss pricing options based on model mix, usage volume, and production requirements.

Postpaid billing and monthly reconciliation

For steady traffic and budget approval workflows, discuss postpaid billing, monthly settlement, and reconciliation cycles.

Contracts, invoices, and procurement

Support invoice materials, purchasing contracts, seal workflows, and dedicated coordination for internal approval.

Billing Questions

Common decisions before launch: how deductions work, where to review usage, invoice and contract support, price updates, and failed-task billing boundaries.

Add funds to your account first. Each call is deducted by model price, input/output tokens, image or video units, duration, and actual usage. No subscription is required.

Ready to Begin?

Add funds to start