> For the complete documentation index, see [llms.txt](https://arbydex.gitbook.io/arbydex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arbydex.gitbook.io/arbydex/arbydex-technology/profitability-analysis.md). # Profitability Analysis ### Evaluating Real Execution Conditions Profitability Analysis determines whether an opportunity remains economically viable after relevant costs and execution conditions are considered. The engine moves beyond the simple difference between two prices. #### Profitability Model ``` Potential Price Difference ↓ Transaction Costs ↓ Liquidity Impact ↓ Execution Conditions ↓ Estimated Result ↓ Qualification Decision ``` The purpose is to distinguish between a visible price difference and an opportunity that may remain viable under actual execution conditions. #### Intelligence Over Raw Spread A large spread does not automatically represent a suitable opportunity. ARBYDEX evaluates the complete execution environment before an opportunity can proceed to the next stage. --- # 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://arbydex.gitbook.io/arbydex/arbydex-technology/profitability-analysis.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.