> For the complete documentation index, see [llms.txt](https://docs.enzyme.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enzyme.finance/user-documentation/getting-started/quickstart/use-cases.md).

# Use Cases

### Versatile by design <a href="#boundless-by-design" id="boundless-by-design"></a>

Enzyme Blue provides businesses and institutions with a seamless solutions to deploy any type of tokenized strategies. The nature of the tokenized products depends on the underlying strategy, this notably includes but is not limited to:

* **Tokenized Funds**, whether native or ad hoc
* **Tokenized Financial Instruments** such as structured products, collateralized debt products, term deposits and more
* **Tokenized Pools** such as TVL Pools, Staking Pools, VC Pools and more


---

# 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.enzyme.finance/user-documentation/getting-started/quickstart/use-cases.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.