> For the complete documentation index, see [llms.txt](https://www.bluegamma.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.bluegamma.io/documentation/market-data-guides/forward-curves.md). # Forward Curves An overview of forward curves, their construction using market data and bootstrapping, and their key applications in financial modeling and risk management. ### **What Are Forward Curves?** Forward curves represent expected interest rates at different points in the future. They’re widely used in: * **Debt Structuring:** To forecast borrowing costs. * **Swap Pricing:** To calculate future cashflows in interest rate swaps. * **Risk Management:** To assess exposure to interest rate changes. *** ### **How We Calculate Forward Curves** We build each forward curve by **bootstrapping** from the latest market swap rates, with the index's latest published fixing anchoring the short end: working tenor by tenor, we solve for the discount factors that price each swap at par, and the forward rates follow from those discount factors. Where the inputs come from is covered in [Where does BlueGamma's data come from?](/documentation/reference/where-bluegammas-data-comes-from.md), and the method step by step in [How We Bootstrap the Yield Curve](/documentation/methodology/how-to-bootstrap-the-yield-curve.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://www.bluegamma.io/documentation/market-data-guides/forward-curves.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.