# Liquidity Abstraction Today's DeFi ecosystem suffers from **fragmented liquidity**, scattered across countless different chains, protocols, and pools. \ \ Functor solves this by creating a layer of **liquidity abstraction**, allowing users and agents to treat the entire multi-chain financial landscape as a single, unified pool of capital. This is made possible by combining a **single signer** identity with our **cross-chain execution** logic. \ \ An autonomous agent can seamlessly tap into liquidity wherever it exists - to find the best swap price, the highest yield, or the lowest borrowing rate - without the user needing to manually bridge assets or manage different accounts. ### Demo: Automated Cross-Chain Liquidity Pool Management. **Controlled by the user, managed by an AI agent, powered by Functor.** {% embed url="" %} ### **Automated Liquidity Provision** Agents can automatically move liquidity to DeFi pools with the highest yield or lowest slippage across any chain, ensuring capital is always in its most productive location. ### **Enhanced Capital Efficiency** This abstraction eliminates idle capital. Assets can be moved and utilized instantly where they are most needed, responding in real-time to market opportunities across any ecosystem. ### **Simplified User and Developer Experience** For users, this means accessing deep liquidity for any action without worrying about the underlying chain. \ For developers, it means building applications that can leverage a global pool of capital from day one. --- # 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://functor.gitbook.io/functor-network-docs/use-cases/liquidity-abstraction.md?ask= ``` 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.