> For the complete documentation index, see [llms.txt](https://docs.transit.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.transit.finance/start-to-use/quick-start-guide/what-is-slippage.md).

# What is Slippage?

Slippage is the difference between the expected price when submitting a trade and the actual execution price.

In blockchain trading, token prices fluctuate with market activity and liquidity. During the time between order submission and on-chain confirmation, price changes may occur, resulting in slippage.

## Causes of Slippage:

* Market Volatility: Prices shift as other trades are executed while waiting for confirmation.
* Low Liquidity: Large orders can significantly impact pool prices, pushing them up or down.
* Network Congestion: Longer confirmation times increase the likelihood of price changes.

## Slippage Tolerance:

On decentralized trading platforms, users can set a “slippage tolerance,” i.e., the maximum acceptable deviation percentage. If the price change exceeds this range, the transaction is automatically canceled to prevent excessive losses.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.transit.finance/start-to-use/quick-start-guide/what-is-slippage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.