> 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/market-data/methodologies.md).

# Methodologies

This section holds the published methodology documents that govern how Coin Metrics evaluates the exchanges behind the Market Data Feed.

## Talos Exchange Scorecard

The Talos Exchange Scorecard is the quantitative evaluation Coin Metrics applies to trading venues. It scores exchanges on the quality and integrity of their reported activity, and that score is an input wherever a data product needs a vetted rather than an exhaustive set of venues. It determines which exchanges count toward trusted volume, and it feeds the candidate market selection behind the [Coin Metrics Prices](/coin-metrics-prices/coin-metrics-prices.md).

{% content-ref url="/pages/NSVpY6mkAOMrH3i69NAd" %}
[Talos Exchange Scorecard](/market-data/methodologies/talos-exchange-scorecard.md)
{% endcontent-ref %}

## Related

* [Market Data Overview](/market-data/market-data-overview.md): the data types and metric families the scorecard is applied within.
* [Volume Metrics](/market-data/market-data-overview/volume-metrics.md): the trusted volume series that uses the scorecard to define its exchange set.
* [Coin Metrics Prices](/coin-metrics-prices/coin-metrics-prices.md): the reference rates and principal market prices, whose own governing methodology and policies live in that 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://gitbook-docs.coinmetrics.io/market-data/methodologies.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.