> For the complete documentation index, see [llms.txt](https://docs.themelia.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.themelia.co/collection-and-curation/analyst-filters.md).

# Analyst Filters

Analyst filters let you tap into the token selections of experienced crypto analysts hand-picked by Themelia. Each analyst curates their own index based on market insight, and you can include or exclude any analyst’s picks as part of your strategy. 

For finer control, you can choose how consensus is formed between multiple analysts: **Any** includes tokens selected by *any* of the analysts you’ve chosen, while **All** only includes tokens selected by *all* of them. The same logic applies in reverse for exclusions.

Think of it as building your own committee of analysts - you decide who’s on the team and how much agreement you want between them before a token makes it into (or out of) your index.

| Combination       | Description                                                                               | Example                                                                                                                                                                                                                                            |
| ----------------- | ----------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Include + Any** | For a token to be included in your index, any of your included analysts may select it.    | <p><strong>Bob and Alice are both analysts with their own token selection lists.</strong> </p><p></p><p>If a user selects both Bob and Alice, then as long as either of them has $SOL in their list, $SOL will be included in the user’s index</p> |
| **Include + All** | For a token to be included in your index, all of your included analysts must select it.   | If a user selects both Bob and Alice, then $SOL will only be included in the user’s index if **both** of them have $SOL in their lists.                                                                                                            |
| **Exclude + Any** | For a token to be excluded from your index, any of your excluded analysts may select it.  | If a user selects both Bob and Alice, then if **either** of them has excluded $DOGE from their list, $DOGE will be removed from the user’s index.                                                                                                  |
| **Exclude + All** | For a token to be excluded from your index, all of your excluded analysts must select it. | If a user selects both Bob and Alice, then $DOGE will only be removed from the user’s index if **both** of them have excluded $DOGE from their lists.                                                                                              |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.themelia.co/collection-and-curation/analyst-filters.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.