> 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/swap-rates/advanced/benchmarking-a-swap-rate-with-a-bank.md).

# Benchmarking a Swap Rate with a Bank

How to benchmark a bank's swap quote: share your notional profile, ask for the mid and all-in rate, and compare against BlueGamma's Swap Pricer on the same profile.

1. **Schedule a Benchmarking Session:**
   * Contact your chosen bank and agree on a time for the exercise.
2. **Share Your Notional Profile:**
   * Provide the bank with your notional profile in Excel format a few hours in advance to ensure they have time to generate rates.
3. **Request Key Rate Information:**
   * Ask the bank to supply:
     * **Mid-Swap Rate**
     * **All-In Rate** (Mid Rate + Execution Spread + Credit Spread)
4. **Use BlueGamma for Analysis:**
   * Log into BlueGamma and input the same notional profile into the **Swap Pricer** tool. Follow this guide

{% content-ref url="/pages/yAEYZXVZ9Xmoyxuce8uC" %}
[Swap Pricer](/documentation/pricers/calculating-a-swap-rate.md)
{% endcontent-ref %}

Compare the rates provided by the bank with the indicative rates generated by BlueGamma.


---

# 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/swap-rates/advanced/benchmarking-a-swap-rate-with-a-bank.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.