> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/metrics/getting-started/analysis.md).

# Analysis

All the available Commerce Layer Metrics API helper endpoints

Commerce Layer Metrics API lets you extract and aggregate relevant metric data from your organizations. Combining the 4 available types of queries ([breakdown](/metrics/getting-started/queries/breakdown.md), [date breakdown](/metrics/getting-started/queries/date-breakdown.md), [stats](/metrics/getting-started/queries/stats.md), and [search](/metrics/getting-started/queries/search.md)) on the 3 available resources ([orders](/metrics-api-reference/resources/orders.md), [returns](/metrics-api-reference/resources/returns.md), and [carts](/metrics-api-reference/resources/carts.md)) and adding the appropriate [filters](/metrics/getting-started/filters.md) lets you cover a wide range of use cases that can fit your business needs. 

{% content-ref url="/pages/FTNt5mLTpi5Ru0U8lVJW" %}
[Use cases](/metrics/getting-started/use-cases.md)
{% endcontent-ref %}

Anyway, since some use cases are more common than others — e.g. determining any correlations between the products added to the shopping cart, identifying the most popular ones, calculating the frequency with which specific products are purchased, etc. — we decided to expose a list of dedicated endpoints (more to come!) that can help you get these results with simple yet customizable queries. See them as helpers to accelerate the use of the Metrics API and feel free to get in touch with us to share your most frequent use cases so we can evaluate covering them in this section.


---

# 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.commercelayer.io/metrics/getting-started/analysis.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.