> For the complete documentation index, see [llms.txt](https://gitbook-docs.coinmetrics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook-docs.coinmetrics.io/network-data/network-data-overview/availability/aggregation.md).

# Aggregation

## Definition

The count of underlying assets aggregated to compute metrics for that aggregate asset in that interval.

| Name                    | MetricID    | Unit   | Interval       |
| ----------------------- | ----------- | ------ | -------------- |
| Aggregated Assets Count | AggAssetCnt | Assets | 1 day, 1 block |

## Details

* Coin Metrics computes metrics for aggregate assets (e.g. combined or composite assets) by aggregating data across a set of underlying constituent assets.
* `AggAssetCnt` reports how many underlying assets were included in that aggregation for a given interval.
* This metric is useful for auditing completeness — if the count drops unexpectedly, it may indicate that one or more underlying assets did not report data for that interval.

## Availability for Assets

{% embed url="<https://coverage.coinmetrics.io/asset-metrics/AggAssetCnt>" %}


---

# 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://gitbook-docs.coinmetrics.io/network-data/network-data-overview/availability/aggregation.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.