> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/platform/billing/details.md).

# Details

The reference for the billing screens: Usage and its tabs, the invoice, and Payment Methods.

The field-by-field reference for your billing.

There are no steps here: you can find out what each screen shows, what your invoice contains, and how we charge you. Consult it whenever you need the exact data.

### Explore the details

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Usage</strong></td><td>The screen where you can see your usage, your subscriptions, and your invoices, organized into three tabs.</td><td><a href="https://docs.plenit.com/docs-en/platform/billing/details/usage.md">Usage</a></td></tr><tr><td><strong>The Invoice</strong></td><td>What the document we issue contains and how to download it.</td><td><a href="https://docs.plenit.com/docs-en/platform/billing/details/the-invoice.md">The Invoice</a></td></tr><tr><td><strong>Payment Methods</strong></td><td>How we charge you: credit card or SEPA direct debit, and how to change the active method.</td><td><a href="https://docs.plenit.com/docs-en/platform/billing/details/payment-methods.md">Payment Methods</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plenit.com/docs-en/platform/billing/details.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
