# Introduction

## How does it work?

Clipper has a hybrid onchain/offchain infrastructure. We expose an API to you with price feeds and a k-parameter, and give you the formula that we use to quote prices based on those + onchain data. That way you can route based on predictions of what Clipper will quote. Once you’re ready to use Clipper in a route you request a quote from our servers. Output scales with input so you can compose in multihop trades.

{% hint style="success" %}
**Clipper prioritizes protecting LP yield and restricts toxic bot flow.** Clipper values real users. To  prevent toxic flow Clipper verifies wallets. Specifically it makes a verification on the wallets used for  swaps and checks whether they are EOA (not contracts), have a min amount of ETH, and have done previous txs.
{% endhint %}

## RFQ Swap API <a href="#supported-networks" id="supported-networks"></a>

<figure><img src="/files/cBTsEgtrLWBdfGSmFil0" alt=""><figcaption></figcaption></figure>

1. Client retrieves pool information
2. Client inputs pool information (price feeds, k factor, etc) in the formula to predict quotes.
3. Client retrieves a firm quote from API
4. Client creates a swap transaction in the clipper pool contract using values from previous step.

For more details about integration check [How to use clipper RFQ API?](/disclaimers-and-technical/integrating-with-clipper-rfq/guides/how-to-use-clipper-rfq-api.md)

## Supported Networks <a href="#supported-networks" id="supported-networks"></a>

<table><thead><tr><th width="226">Network</th><th>Chain ID</th></tr></thead><tbody><tr><td>Ethereum Mainnet</td><td>1</td></tr><tr><td>Polygon Mainnet</td><td>137</td></tr><tr><td>Optimism Mainnet</td><td>10</td></tr><tr><td>Mantle Mainnet</td><td>5000</td></tr><tr><td>Arbitrum One</td><td>42161</td></tr></tbody></table>

{% hint style="info" %}
If you want to review our contracts for each supported network, please refer to this [link](/disclaimers-and-technical/smart-contracts.md)
{% endhint %}

## Get Started

[How to use Clipper API?](/disclaimers-and-technical/integrating-with-clipper-rfq/guides/how-to-use-clipper-rfq-api.md)

[Code Examples](/disclaimers-and-technical/integrating-with-clipper-rfq/guides/integration-examples.md)

[Estimate Clipper Prices](/disclaimers-and-technical/integrating-with-clipper-rfq/guides/estimate-clipper-prices.md)

[Interacting with Clipper Exchange](/disclaimers-and-technical/integrating-with-clipper-rfq/guides/interacting-with-the-clipper-exchange-contracts.md)

[API Reference](/disclaimers-and-technical/integrating-with-clipper-rfq/api-reference/api-v1/overview.md)

[Troubleshooting](/disclaimers-and-technical/integrating-with-clipper-rfq/troubleshooting-and-faqs.md)

To see who else has integrated with Clipper, checkout the data page: <https://clipper.exchange/data>


---

# Agent Instructions: 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:

```
GET https://docs.clipper.exchange/disclaimers-and-technical/integrating-with-clipper-rfq/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.