View Costs and Usage¶
This page explains how to inspect balances and trends, trace usage, review transaction records, and request invoices in Billing Center.
Cost overview¶
Use the Billing Center home page to determine whether the balance is sufficient and which dimensions or workspaces consume Credit.
Credit balance¶
Common information in the balance card:
Information |
Description |
|---|---|
Current balance |
Available Credit |
Today / current month / previous month consumption |
Credit consumed during each period |
Estimated available days |
Estimate based on recent consumption rate, for reference only |
Top-up entry |
Opens the top-up flow |
Short bursts of high usage affect Estimated available days. Use it as a top-up signal and use usage details for precise attribution.
Consumption trends¶
Select a range such as last week, last month, current month, or custom, then switch between:
By billable item: Spending on compute resources, AI services, Genesis, and other items.
By workspace: Consumption by workspace.
Monthly bill overview¶
Monthly summaries commonly include billing period, issue date, total consumption, usage charges, monthly subscriptions, status, and view/download actions.
A monthly bill separates usage charges from monthly subscriptions. If total consumption rises while usage remains similar, check whether a monthly subscription such as dedicated support or enterprise identity was activated.
For top-up instructions, see Top-ups and Account Settings.
Usage details¶
Use billing-period, daily, or hourly details to identify which item, workspace, specification, or scenario generated a charge.
Locate and filter¶
Search by bill number or select a time range.
Select a statistical period: billing period, day, or hour.
Select a statistical dimension: by billable item or workspace.
Narrow the results with billable-item, status, and other filters.
Parent and child details¶
Items with subitems, including compute resources, AI services, and Genesis, commonly use parent and child rows:
Parent row: Total consumption for the item.
Child row: Specific specification, scenario, or model, with unit price, usage, and consumption.
Meaning of billable items in details¶
Item |
Measurement |
Common child breakdown |
|---|---|---|
Compute resources |
Node uptime in hours |
Query/task specifications |
AI services |
Tokens at a unified price |
Service scenario, such as conversation or knowledge base |
Data storage |
GB-month |
Catalog data objects |
Public-network traffic |
Outbound GB |
Generally no child item |
Genesis |
Input/output/cache tokens |
By model, with a link to Genesis usage details |
BYOM |
Token service fee |
By connected model |
Dedicated support / enterprise identity |
Monthly |
Subscription status, monthly fee, and billing period |
AI-service details generally break down by scenario, not model. Use Genesis to inspect tokens by model.
Usage details generally support CSV / Excel export.
Transaction details¶
Transaction details record incoming and outgoing funds such as top-ups, consumption, withdrawals, and refunds. Unlike usage details, these are financial transaction records. Consumption is commonly aggregated by settlement window rather than recorded once per call.
Filters¶
Filter by transaction number, time range, and:
Dimension |
Examples |
|---|---|
Income/expense type |
Income / expense |
Transaction type |
Consumption / top-up / withdrawal / refund |
Transaction channel |
WeChat / Alipay / bank transfer / platform, and others |
The Platform channel generally refers to Credit changes that do not use an external payment channel, such as system deductions or grants, subject to product behavior.
Common detail columns¶
Transaction number, transaction time, income/expense type, transaction type, channel, amount, Credit change, billing period, status, invoice, and more.
Request an invoice¶
You can request an invoice for a successful top-up from its invoice column. First configure the invoice title and taxpayer ID in Settings; see Top-ups and Account Settings. Invoices generally apply only to successful top-ups. Consumption, withdrawals, and refunds are not invoiced separately.