> 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/getting-started/use-cases.md).

# Use Cases

Enzyme empowers industry leaders across sectors to achieve immediate goals and long-term growth

<details>

<summary>Tokenized Funds</summary>

Create natively tokenized funds for efficient and innovative digital asset management. The tokenized nature of Enzyme Vaults enables you to create investment funds that are tokenized by design, or to add as a tokenization layer to existing centralized investment vehicles.

</details>

<details>

<summary>Financial Instruments</summary>

Enzyme enables financial institutions and businesses to issue and distribute fully on-chain financial instruments ranging from exchange-traded product to advanced debt and structured products.

</details>

<details>

<summary>Tokenized Pools</summary>

Seamlessly attract and consolidate liquidity through incentivized and fully decentralized vehicles.

</details>

<details>

<summary>Real World Assets</summary>

Real-World Assets (RWAs) represent one of the most promising frontiers for value creation in digital finance—but tokenization alone is not enough. Enzyme provides the execution layer that unlocks utility, composability, and on-chain programmability, enabling RWAs to operate seamlessly within decentralized financial ecosystems.

</details>


---

# 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/getting-started/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.