> For the complete documentation index, see [llms.txt](https://docs.kaiko.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaiko.com/formerly-vinter-indices/api/vinter-taxonomy-vtaxo.md).
# Vinter Taxonomy (VTAXO)
The VTAXO for crypto assets is a classification framework that organizes digital assets into categories based on their underlying characteristics and use cases.
The taxonomy typically includes categories like Layer1, Smart Contract Platforms, and Metaverse, among others. Each category is defined by specific features such as the asset's intended function, the underlying technology, and its role within the blockchain ecosystem. This framework helps investors, regulators, and market participants better understand and analyze the crypto market. For more detailed information, you can visit the [Vinter Taxonomy Methodology](https://methodology.vinter.co/vinter/taxonomy).
### Active VTAXO
The active VTAXO endpoint returns information on all available categories. And meta information related to the categories.
### VTAXO
The VTAXO endpoint returns assets by categories. Same asset can be present in multiple categories.
---
# 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.kaiko.com/formerly-vinter-indices/api/vinter-taxonomy-vtaxo.md?ask=&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.