> For the complete documentation index, see [llms.txt](https://docs.north.cloud/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.north.cloud/docs/features/visibility/explore-costs.md).

# Explore costs

{% embed url="<https://www.loom.com/share/577ddca9774744f997e8909f70d5ae7c>" %}

**Explore** allows you to view your cloud cost and usage data at multiple levels of granularity—including by month, day, or even by hour—so you can zoom in or out as needed.&#x20;

You can filter and group your data by up to two attributes at once (such as service, region, project, or tag), making it easy to analyze specific cost drivers or usage trends. Automated KPIs are generated to highlight your largest spend areas and the groups with the highest percentage increases, so you immediately see where your attention is needed most. All results are presented in a table that you can easily export to share insights with your team.


---

# 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.north.cloud/docs/features/visibility/explore-costs.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.
