> 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/platform/billing/details.md).

# Detalles

La referencia de las pantallas de facturación: Uso y sus pestañas, la factura y Métodos de Pago.

La referencia campo a campo de tu facturación.

Aquí no hay pasos: encuentras qué muestra cada pantalla, qué contiene tu factura y con qué te cobramos. Consúltalo cuando necesites el dato exacto.

### Explora los detalles

<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>Uso</strong></td><td>La pantalla donde ves tu consumo, tus suscripciones y tus facturas, organizada en tres pestañas.</td><td><a href="https://docs.plenit.com/platform/billing/details/usage.md">Uso</a></td></tr><tr><td><strong>La Factura</strong></td><td>Qué contiene el documento que emitimos y cómo lo descargas.</td><td><a href="https://docs.plenit.com/platform/billing/details/the-invoice.md">La Factura</a></td></tr><tr><td><strong>Métodos de Pago</strong></td><td>Con qué te cobramos: tarjeta de crédito o domiciliación bancaria SEPA, y cómo cambiar el método activo.</td><td><a href="https://docs.plenit.com/platform/billing/details/payment-methods.md">Métodos de Pago</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/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.
