# Embedded Swaps #### Universal Swap Integration Enclave's swap functionality can be embedded into any application with just a few lines of code. Our universal swap engine supports multiple virtual machines and provides the deepest liquidity across the entire crypto ecosystem. **Multi-VM Support:** * **EVM Chains**: Ethereum, Polygon, Arbitrum, Optimism, BSC, Avalanche, and 50+ other networks * **Solana VM**: Native Solana token swaps with Jupiter aggregation * **Bitcoin Network**: Lightning Network swaps and ordinals trading * **Cross-VM Swaps**: Seamlessly trade between different blockchain ecosystems **Integration Features:** * **One-Line Integration**: Add swap functionality with a single SDK call * **Customizable UI**: White-label swap interface that matches your app's design * **Headless API**: Build custom interfaces with our swap engine * **Real-Time Pricing**: Live price feeds and market data * **Route Optimization**: Automatically find the best prices across all DEXs and chains #### Monetization Integrating applications can monetize their user base by earning a percentage of trading fees generated through embedded swap functionality. This creates a new, passive revenue stream that complements existing business models. * **Fee Revenue**: Earn a cut of every swap transaction made through your application * **No Additional User Cost**: Users pay standard market rates while you earn from volume * **Scalable Income**: Revenue grows with your user base and trading activity * **Zero Infrastructure**: No need to build or maintain trading infrastructure * **Transparent Reporting**: Real-time analytics on trading volume and earned fees --- # 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.enclave.money/introducing-enclave-money/embedded-swaps.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.