> For the complete documentation index, see [llms.txt](https://docs.finops.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finops.softwareone.com/analysis/cost-map/view-cost-map.md).

# View the cost map

The cost map enables you to visualize your cloud expenses by region/location and service, so you can detect areas with high spending across cloud providers. 

A cost map can also be used to view data transfer and connectivity costs.

To view the cost map: 

1. From the left sidebar, navigate to **Cost map**.
2. (Optional) Adjust the date range to display data for a specific period. 
3. Use the [Region cost map](/analysis/cost-map.md#region-cost-map) to visualize your spending geographically across cloud deployments:
   * Hover over a circle to see detailed expense information. Use the **Show resources** link to open the **Resources** page and view all corresponding resources.
   * Toggle between the full-screen and regular view.
   * Use the **Summary by region** table to view details, such as expenses for your specified time period, the percentage of total expenses, and related cloud resources. 
4. Select the [Network traffic cost map](/analysis/cost-map.md#network-traffic-cost-map) to analyze costs associated with data transfer and connectivity.


---

# 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.finops.softwareone.com/analysis/cost-map/view-cost-map.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.