> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/ai/mcp-server/use-cases/query-billing-data.md).

# Query Billing and Cost Data

**Who this is for:** Finance teams, account owners, and DevOps engineers who must understand <code class="expression">space.vars.ionos\_cloud</code> spending, validate invoices, or build cost-attribution reports, without digging through the DCD billing console.

Use the Billing tools to inspect invoices, review usage, and understand your <code class="expression">space.vars.ionos\_cloud</code> spending through natural language.

## View invoices

> List my last three invoices.

> Get the details of invoice `INV-2026-05`.

> Show me all invoices from Q1 2026.

## Analyze usage

> Show my resource usage for this month.

> What is my usage for Frankfurt data centers this week?

> Compare my daily usage for the last seven days.

## Review traffic

> How much outbound traffic have I used this month?

> Show my traffic for the last billing period.

## Check pricing

> What is the current price for a dedicated core server?

> List the pricing catalog for Object Storage.

## Common patterns

Combine multiple Billing tools to answer complex questions:

> What were my top three cost drivers last month based on usage?

> How does my usage this month compare to last month?

{% hint style="info" %}
**Note:** Billing tools are always available at startup; no loader step is required.
{% endhint %}


---

# 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.ionos.com/cloud/ai/mcp-server/use-cases/query-billing-data.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.