> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/customer-self-service/subscription-management/customer-portal-usage-information.md).

# Customer Portal Usage Information

For usage-based and metered plans, the customer portal shows customers their **current consumption** alongside their subscriptions — so they can see exactly what they're drawing down and what they're being billed for, with no need to call in. That transparency reduces "bill shock," cuts support contacts, and helps customers self-manage before they hit a limit.

## What the customer sees

Each metered charge appears in a **Current period usage** card with a line per charge — the charge name and a `used / included` reading in its unit of measure (for example `1,200 / 5,000 API calls`), plus a progress bar showing how much of the allowance is consumed. The card header shows the billing period and **days remaining** in it. Charges without an included allowance are labelled **Pay-as-you-go** (the consumed total shows with no bar), and a charge consumed past its limit is flagged as overage.

## How it works

Usage is metered and rated by your billing system and read back through the platform's usage API, then surfaced on the customer's subscription view — customers never see raw meter events, only the rolled-up drawdown. If a subscription has no metered charges, the card shows a quiet empty state ("No metered usage on this subscription"); if the usage read fails it shows "Usage data unavailable" rather than a wrong number. Whether the usage card appears on a given portal page is a page-configuration choice, so you decide where — and for which audiences — consumption is shown.

## Related

* [Customer Subscription Management](/product/customer-self-service/subscription-management/customer-subscription-management.md)
* [Customer Portal Overview](/product/customer-self-service/overview/customer-portal-overview.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/customer-self-service/subscription-management/customer-portal-usage-information.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.