> For the complete documentation index, see [llms.txt](https://numerical.gitbook.io/numericalfi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://numerical.gitbook.io/numericalfi/welcome-to-numerical.md). # Welcome to NUMERICAL Building the optimal DEFI block sequence so you don't have to NUMERICAL falls under what we'd like to call "DEFI as a service", I.E, serving the purpose of providing a shortcut to Investors who aren't Real DEFI savvy but still would like to take advantage of the Numerous opportunities in terms of real yield generation across all blockchains.\ \ We use a self-labeled process called "Block optimization sequence" or BOS for short. \ What this essentially means is that we map the best pathways to achieve optimal yield through either a stable coin or a blue-chip volatile coin strategy. In turn, users can leverage the outcome by simply providing their USDC to the platform and reap the rewards. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://numerical.gitbook.io/numericalfi/welcome-to-numerical.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 `build a script that syncs our docs to a CMS` 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.