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
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.
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.
Add balance in the console. Once it arrives, it can be used for model calls.
Use the unified API to call text, image, video, speech, and related models.
The system deducts by model price, input/output usage, task units, and actual consumption.
Review consumption and request status through usage logs and billing records.
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 galleryNetwork, timeout, or upstream errors are usually not charged as successful results.
Video jobs that fail because prompts violate platform policies may incur a ÂĨ0.01 handling fee.
Whether a charge applies is ultimately based on usage logs, task status, and billing records.
Review call records, balance changes, and bills to reconcile model usage and costs. Enterprise projects can also confirm invoices, contracts, and reconciliation documents.
Usage logs show model, time, consumption, and status for troubleshooting and attribution.
Top-ups, consumption, and balance changes are recorded for budget control.
Invoice materials can be prepared based on top-ups, usage, or contract terms.
Enterprise procurement can discuss contracts, postpaid billing, monthly reconciliation, and dedicated support.
Discuss pricing options based on model mix, usage volume, and production requirements.
For steady traffic and budget approval workflows, discuss postpaid billing, monthly settlement, and reconciliation cycles.
Support invoice materials, purchasing contracts, seal workflows, and dedicated coordination for internal approval.
Common decisions before launch: how deductions work, where to review usage, invoice and contract support, price updates, and failed-task billing boundaries.