> 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/reference/where-bluegammas-data-comes-from.md).

# Where does BlueGamma's data come from?

BlueGamma builds its swap rates and forward curves from broker-dealer and electronic trading venue quotes, plus central bank fixings and policy rates, for more than 40 benchmark curves.

BlueGamma's swap rates and forward curves are built from live and indicative quotes from broker-dealer networks and electronic trading venues, with benchmark fixings and policy rates from central banks and reference institutions.

We aggregate data from:

* **Broker-dealer networks:** capturing live and indicative pricing across OIS and IRS markets.
* **Electronic trading venues:** reflecting real, tradeable market levels, liquidity conditions, and daily rate movements.
* **Central banks and reference institutions:** providing benchmark fixings and policy rates.

We use these market inputs to construct our **forward curves,** blending swap rate data, fixings, and benchmark levels to produce smooth representations of the market across maturities. The method is documented in [How We Bootstrap the Yield Curve](/documentation/methodology/how-to-bootstrap-the-yield-curve.md).

This combination of live market data and benchmarks allows BlueGamma to deliver a representative dataset for more than **40 benchmark curves**, including **SOFR, SONIA, CORRA, EURIBOR, SARON, BBSW**, and others. See [Available Indices](/documentation/integrations/available-indices.md) for the full list.

All data is made available through our **API**, **Excel Add-in**, and **web platform**, making it easy to integrate into models, pricing tools, or portfolio analytics.


---

# 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/reference/where-bluegammas-data-comes-from.md?ask=<question>&goal=<user_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.