> For the complete documentation index, see [llms.txt](https://docs.fida.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fida.finance/introduction/readme.md). # Transform Risk into Opportunity! Fida Risk Transfer Protocol Overview You can think of Fida as a crowd funded reinsurance group. The Fida Risk Transfer Protocol decentralizes risk. In so doing, it makes insurance liquid, safe, and efficient for everyone. Users receive coverage on submitted policies, earn premiums from policy payments and collect fees of protocol usage. Our mission is to close the coverage gap, protecting those who would before not have access to insurance by unlocking a new insurance infrastructure within the web3 revolution. These pages document how we've structured the protocol and provide the resources necessary to fully understand how the protocol is able to transfer risk, improve investment liquidity, and allow regulators transparent access to the health and stability of on-chain insurance portfolios. Please join the [Fida Community Discord server](https://discord.gg/jjwnEKh8) to connect with the Fida Finance Core Team. We look forward to answering any of your questions and helping you integrate with and build on top of the Fida Risk Transfer Protocol. It's time to forget risk as we've known it. The key to this new revolution in risk transfer are two on chain contracts: * [The Fida Policy Contract](/fida-policy/policy-contract.md) * [The Fida Investor Contract](/investors/investor-contract.md) --- # 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.fida.finance/introduction/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.