> For the complete documentation index, see [llms.txt](https://docs.wirexpaychain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wirexpaychain.com/wirex-pay/wirex-pay-zk-infrastructure/wirex-pay-and-agglayer-integration.md). # Wirex Pay and AggLayer Integration AggLayer is a revolutionary concept introduced by Polygon that enhances the interoperability and scalability of blockchain ecosystems. By integrating Wirex Pay with AggLayer, we unlock new potential for seamless liquidity movement and interconnected blockchain operations. * Unified Liquidity: AggLayer enables Wirex Pay to tap into a vast pool of liquidity across various EVM chains, ensuring that assets can move smoothly and efficiently between networks. * Interoperability: With AggLayer, Wirex Pay can easily interact with multiple blockchains, providing users with a unified and consistent experience across different platforms. * Scalability and Flexibility: The aggregation of different chains through AggLayer allows Wirex Pay to scale dynamically, accommodating growing user demands without compromising performance or security. --- # 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.wirexpaychain.com/wirex-pay/wirex-pay-zk-infrastructure/wirex-pay-and-agglayer-integration.md?ask=&goal= ``` `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.