> 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/methodology/public-website-curves-vs-platform-curves.md).

# Public Website Curves vs. Platform Curves

Why the curves shown on bluegamma.io marketing pages differ from the curves in the app, API, and Excel Add-in, and which one to use for modelling.

The curves on the public bluegamma.io marketing pages are end-of-day snapshots that, for most indices, are built from a separate market data feed, while the app, API and Excel Add-in all use BlueGamma's platform curves, updated intraday for most indices. Use the platform curves for any modelling, valuation or pricing; the website curves are a reference only, and small differences between the two on the same day are expected.

***

## The short answer

|                                       | **Public website**                                                                                           | **Platform (app, API, Excel Add-in)**                                                                              |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ |
| Where                                 | Marketing pages on [bluegamma.io](https://www.bluegamma.io) (e.g. `/usd-swap-rates`, `/sonia-swap-rates-uk`) | [app.bluegamma.io](https://app.bluegamma.io), [api.bluegamma.io](https://api.bluegamma.io), BlueGamma Excel Add-in |
| Purpose                               | Marketing and quick reference                                                                                | Modelling, valuation, risk, pricing                                                                                |
| Data                                  | End-of-day snapshot, from a separate market data feed for most indices                                       | BlueGamma's platform rate data, updated intraday for most indices                                                  |
| Calibration                           | Bootstrapped separately, from that feed's rates                                                              | Bootstrapped into calibrated zero, discount and forward curves                                                     |
| Recommended for production modelling? | No                                                                                                           | Yes                                                                                                                |

***

## Why they differ

The public website curves exist to give visitors a quick snapshot of where rates are today. They are updated end-of-day and are presented as a reference only.

The platform curves (app, API, Excel Add-in) all use the same rate data. Most indices update throughout their market hours and a few update once a day (see [How Often Is Your Data Refreshed?](https://www.bluegamma.io/documentation/reference/how-often-is-your-data-refreshed.md)). That data runs through the BlueGamma curve construction engine, which bootstraps calibrated zero, discount and forward curves. These are the curves you see in the app, the curves returned by every `api.bluegamma.io/v1/*` endpoint, and the curves the Excel Add-in formulas resolve to.

Because the two have different snapshot timings and, for most indices, different inputs, you will see small numerical differences between the website curve and the platform curve for the same index on the same day. This is expected.

***

## Which should I use?

Use the **platform** (app, API, or Excel Add-in) for anything you intend to rely on: pricing, valuation, risk, reporting, or any downstream modelling. The curves on the public marketing pages are not intended for that use and we do not recommend relying on them.

If you need to validate platform data against another provider, see:

{% content-ref url="/pages/fdpIgta8cl9r4C4XFThe" %}
[How do I compare BlueGamma data with Bloomberg or other platforms?](https://www.bluegamma.io/documentation/reference/validating-bluegamma-api-data-against-bloomberg-or-other-platforms.md)
{% endcontent-ref %}

***

## Related

* [How We Bootstrap the Yield Curve](https://www.bluegamma.io/documentation/methodology/how-to-bootstrap-the-yield-curve.md)
* [Available Indices](https://www.bluegamma.io/documentation/data-coverage/whats-available/available-indices.md)
* [API Reference](https://www.bluegamma.io/documentation/integrations/api/api-reference.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/methodology/public-website-curves-vs-platform-curves.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.
