> For the complete documentation index, see [llms.txt](https://docs.squidrouter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.squidrouter.com/api-and-sdk-integration/coral-intent-swaps/become-a-solver.md).

# Become A Solver

Whitelabeling Squid Intents

### Overview

<mark style="color:yellow;">**With Squid intents whitelabeling, integrators can deploy their own solver network and multi-chain liquidity within Squid’s cross-chain routing infrastructure.**</mark> This enables a seamless, branded trading experience while leveraging Squid Intents' intent-based order system.

### Why Whitelabel Squid Intents?

* **Brand & Liquidity Control**: Enable your users to swap seamlessly between ecosystems under your brand, managing liquidity and user experience end-to-end.
* **Revenue Opportunities**: Capture spread, fees, and revenue from every order routed through your network.
* **Scalability**: Leverage Squid’s vetted cross-chain connectivity without reimplementing complex bridging and messaging logic.

### Prerequisites

* **On-Chain Liquidity**: Provision assets across one or more EVM-compatible chains.
* **Solver Infrastructure**: Host an orderbook and execution engine capable of generating quotes in Squid Intents' RFQ format.
* **Technical Alignment**: Support REST or WebSocket endpoints and adhere to Squid Intents' order lifecycle conventions (RFQ, fill, settlement).

### Business Case

Whitelabeling Squid Intents allows you to:

* Integrate seamlessly into existing trading terminals or DeFi frontends.
* Extend your market-making services to permissionless cross-chain order filling
* Differentiate with proprietary pricing algorithms and liquidity incentives.

### Getting Started

1. **Discuss Partnership**: Reach out to Squid to align on requirements and liquidity commitments.
2. **Production Launch**: Go live under your own brand, supported by Squid Intents' monitoring and support.

### Contact

For more information or to express interest, please fill out our [partnerships form](https://squidrouter.typeform.com/partnerships) and a member of the Squid team will follow up.


---

# 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.squidrouter.com/api-and-sdk-integration/coral-intent-swaps/become-a-solver.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.