> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/charts.md).

# Charts

- [Overview](https://guides.noloco.io/charts/overview.md): Learn how to use charts in Noloco
- [Line Charts](https://guides.noloco.io/charts/line-charts.md): Learn how to build line charts using X-Axis values and Series
- [Bar Charts](https://guides.noloco.io/charts/bar-charts.md): Learn how to build bar charts using X-Axis values and Series
- [Stacked Bar Charts](https://guides.noloco.io/charts/stacked-bar-charts.md): Learn how to build stacked bar charts using X-Axis values and Series
- [Area Charts](https://guides.noloco.io/charts/area-charts.md): Learn how to build area charts using X-Axis values and Series
- [Donut Charts](https://guides.noloco.io/charts/donut-charts.md): Learn how to build donut charts using categories and values
- [Funnel Charts](https://guides.noloco.io/charts/funnel-charts.md): Learn how to build funnel charts to visualize progressive reduction through stages
- [Radar Charts](https://guides.noloco.io/charts/radar-charts.md): Learn how to build radar charts to compare multiple variables
- [Statistic Charts](https://guides.noloco.io/charts/statistic-charts.md): Learn how to create statistic charts to display key metrics


---

# 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://guides.noloco.io/charts.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.