> 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/chains-and-tokens/integrate-your-chain.md). # Integrate Your Chain ## Adding a New Chain to Squid To onboard a new chain to Squid, the integration is executed through **Squid Intents**, our intent-based cross-chain routing protocol. Squid Intents enables seamless, efficient, and secure swaps across a wide network of supported blockchains by connecting users directly with market makers. ### What We Need From You To support your chain within Squid, we require: * **A market maker loan** to enable Squid Intents to execute swaps on your chain with deep liquidity and guaranteed execution quality. This loan ensures that Squid intents market makers can fulfill intents rapidly, securely, and with zero slippage for users transacting with your chain. ### Why Integrate with Squid? Squid is designed for scalable, low-latency cross-chain interactions. By integrating with Squid, your chain gains: * **Access to 100+ Chains** already supported by Squid, including Solana, BTC, and major EVMs * **Execution in Under 5 Seconds** for most swaps * **Zero Slippage**, with direct market maker fulfillment * **Up to 90% Gas Cost Reduction** compared to traditional AMM-based routing * **MEV Protection** and **Enterprise-grade Security** ### Technical Requirements * Squid Intents uses a **RFQ intent-based protocol design** and **TEE-verified batched settlement**. * Smart contracts are **audited**, **non-upgradeable**, and **ownerless**, ensuring security and neutrality. ### Next Steps If you're interested in adding your chain to Squid via Squid Intents, please submit our [partnerships form](https://squidrouter.typeform.com/partnerships) to begin integration discussions. 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/chains-and-tokens/integrate-your-chain.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.