> 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/about-enzyme/who-are-we.md). # Who are we Founded in 2017 by Mona El Isa, Enzyme was built with a mission to level the investment playing field and drive the democratization of decentralized finance through cutting-edge infrastructure, originally designed exclusively for asset managers. After eight years of pioneering the space with the leading asset management protocol, Enzyme evolved into a Global Infrastructure for Tokenized Finance — empowering any businesses and institutions to scale through tokenization, introducing new products and services to provide them with all the tools they need to achieve their objectives. At Enzyme, we are deeply committed to the ethos of decentralization, embedding it not only in the design of our products but also in the way we approach development. We believe the future of finance is unfolding before us—a great movement of convergence that will ultimately lead to the emergence of ONE finance: a system that grants users greater fairness, transparency, and control. We embrace this era of transformation, empowering visionaries and builders to bring their boldest ideas to life, shaping a more decentralized and equitable future for all. --- # 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/about-enzyme/who-are-we.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.