> 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/asseteodcompletiontime.md).

# Asset Completion Time

## Definition

The time that the last metric for the asset was calculated, indicating that all metrics for that asset have been calculated.

| Name            | MetricID               | Unit         | Interval |
| --------------- | ---------------------- | ------------ | -------- |
| Completion Time | AssetEODCompletionTime | EPOC seconds | 1d       |

## Details

Our metric calculation begins at 00:00 UTC. Given that our asset metrics finish calculating at different times each asset AND each asset's last metric calculation will occur at different times, we've created a metric so users can determine when the entire metric set for a given asset is fully calculated (has completed its daily processing).

The result provides a "time" string in EPOC seconds.

## Availability for Assets

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


---

# 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/asseteodcompletiontime.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.