> For the complete documentation index, see [llms.txt](https://docs.infraredtrading.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraredtrading.com/readme.md). # Why Infrared Infrared compiles multi-asset portfolio rebalances into single atomic transactions, with LP decomposition and causal simulation built in. Infrared is a causal liquidity engine for institutional DeFi execution. It compiles complex portfolio rebalancing intents—spanning LP tokens, vault shares, and yield positions—into single, optimized atomic transactions. Standard aggregators were built for the Retail Era: single-token swaps between two counterparties. Infrared is built for the Institutional Era, where a "trade" is a state-changing event across a portfolio of derivative assets. ## The Three Capabilities ### LP Decomposition Infrared looks inside derivative wrappers. Rather than selling an LP token at a discount on secondary markets, it recognizes that the token represents underlying value—and unlocks that value directly. This eliminates the liquidity gap that standard routers cannot bridge. ### Causal Simulation Before execution, Infrared simulates the full sequence of events in order. If unwinding a large LP position changes the price of ETH, the engine accounts for that shift when pricing subsequent legs. This prevents self-cannibalization—where a naive executor routes trades through the very pools it is draining. ### Multi-Vector Rebalancing Infrared treats a portfolio rebalance as a single equation. All inputs are aggregated into a virtual inventory, netted against desired outputs, and only the strictly necessary swaps are executed to close the gap. This minimizes fees, market impact, and sequencing risk. ## Who It Is For * **Treasury Managers** executing atomic multi-asset rebalances with predictable outcomes * **DAO Operators** who need deterministic execution that matches governance proposal expectations ## Quick Links * [Overview](/overview.md) -- How the API works * [Getting Started](/getting-started.md) -- Authentication and your first request * [API Guides](/api-reference/api-guides.md) -- Detailed endpoint walkthroughs * [Changelog](/resources/changelog.md) -- Release history ## Base URL ``` https://api.infraredtrading.com ``` ## Authentication Quoting and discovery endpoints are open (IP rate-limited); building transactions requires an API key sent via the `X-API-Key` header. See [Authentication](/getting-started/authentication.md) for details. --- # 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.infraredtrading.com/readme.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.