> For the complete documentation index, see [llms.txt](https://docs.kaiko.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaiko.com/getting-started/kaiko-examples/compare-price-slippage-between-exchanges.md).

# Compare price slippage between exchanges

Price slippage measures how liquid a market is by measuring the gap between the expected and actual price of a marker order. When markets drop and there are large sell-offs, slippage often increases and it becomes harder to buy or sell at your desired price. This varies by exchange, trading pair, and time of day. Using Kaiko's data, we can measure potential BTC slippage across exchanges for different trade sizes. This provides valuable insight for market traders looking to minimize losses.

<figure><img src="https://815309201-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzwO3AMVXsp37KK2FngVc%2Fuploads%2FxozeqlAuL7ZwVJ1nQNtk%2FPrice%20Slippage.png?alt=media&#x26;token=28eae261-1790-49c7-b7a1-79d13ac274d0" alt=""><figcaption><p>The chart above shows how price slippage increased on Itbit between 5th and 7th August for BTC-USD, suggesting liquidity troubles.</p></figcaption></figure>

### <mark style="color:blue;">How to build the request</mark>

Use [Order Book Snapshots](/rest-api/cefi-spot-market-data/order-book-aggregations/price-slippage-aggregation.md) (slippage) with the following parameters to replicate this chart.

| Parameter          | Value                                                                                                                                   |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
| `exchange`         | <p><code>cbse</code><br><br>... and then<br><br><code>stmp</code><br><code>itbi</code><br><code>krkn</code></p><p><code>okcn</code></p> |
| `instrument_class` | spot                                                                                                                                    |
| `intrument`        | btc-usd                                                                                                                                 |

Here's an example of a cURL string request using the values above:

{% code overflow="wrap" %}

```url
curl -X GET "https://us.market-api.kaiko.io/v2/data/order_book_snapshots.v1/exchanges/cbse/spot/btc-usd/ob_aggregations/slippage?slippage=100000&interval=1h" -H "accept: application/json" -H "X-Api-Key: YOUR_API_KEY"
```

{% endcode %}

When you receive your response, search for the following fields to find the data you need:

* `timestamp`
* `ask_slippage`
* `bid_slippage`

{% hint style="warning" %}
Order Book Snapshots are available through the API with a 1-month rolling window. While this means you can't recreate the example shown above, the instant live data meets most trading and analysis needs.
{% endhint %}


---

# 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.kaiko.com/getting-started/kaiko-examples/compare-price-slippage-between-exchanges.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.