> For the complete documentation index, see [llms.txt](https://support.bancor.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.bancor.network/bancor-amm/trade/price-slippage.md).
# Price slippage
Price slippage refers to the difference between the expected price before a transaction is executed and the actual price at which it is executed.
Slippage happens due to the dynamic variables of the Bancor AMM formula. Every transaction changes the price slightly. The larger the transaction size of a token relative to its liquidity depth, the higher the price slippage. When you see the "price slippage" message, you are still able to proceed with your transaction. This is not an indication that may cause the transaction to fail in any way. If you wish to convert tokens, you may proceed.
You may also set a custom slippage percentage ("Slippage Tolerance") to make sure that any transaction with higher slippage will revert. This is available by clicking at the top right menu next to your wallet.
---
# 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://support.bancor.network/bancor-amm/trade/price-slippage.md?ask=&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.