> For the complete documentation index, see [llms.txt](https://docs.helix.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helix.org/documentation/readme.md). # Welcome Helix is a decentralized, non-custodial liquidity protocol that provides developers and users with secure, composable access to deep, efficient markets on Base. As a onchain financial infrastructure, Helix enables lending, borrowing, and liquidity provisioning to be seamlessly integrated into decentralized applications, all governed by audited smart contracts and a modular architecture designed for scalability and resilience. Through Helix’s developer suite, builders can integrate directly with the protocol using a range of powerful tools, including the React SDK, TypeScript SDK, and GraphQL API. These resources allow for smooth interaction with the protocol’s core functionalities—such as supplying assets, borrowing liquidity, querying market data, or managing user portfolios—while maintaining composability across the wider DeFi ecosystem. This robust tooling empowers developers to innovate across multiple use cases, from DeFi-native platforms and digital wallets to fintech applications and exchanges. With Helix, projects can automate asset management, build new financial primitives, or deliver dynamic user experiences that combine transparency, security, and real yield opportunities—all within the growing Layer-2 DeFi landscape. --- # 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.helix.org/documentation/readme.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.