> For the complete documentation index, see [llms.txt](https://thecontentforge.gitbook.io/thecontentforge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thecontentforge.gitbook.io/thecontentforge-docs/investor-intel/execution-intelligence.md). # Execution Intelligence (Investor Intel) > This is the Investor Intel execution page. For the content-side On-Chain feature of the same name, see [Execution Intelligence](/thecontentforge-docs/web3-intelligence/execution-intelligence.md). Execution Intelligence answers a question most research tools skip: if you actually traded this asset, how badly would the market punish you for it? It assesses swap execution quality, price impact, and liquidity depth so you understand the practical side of a position before you act anywhere. ### What it measures * **Price impact** - how much a swap of a given size would move the price against you * **Liquidity assessment** - how deep the available liquidity really is, and how quickly impact grows with size * **Execution quality rating** - a single classification per check: **Strong**, **Reasonable**, **Thin**, or **Poor** * **Per-venue breakdown** - how execution looks venue by venue, since the same swap can be fine on one venue and brutal on another ### AI execution report Every check can produce an AI execution report: a straightforward read on what the numbers mean, where the liquidity risks are, what size the market can absorb, and what to verify before relying on the result. ### How to use it 1. Pick the asset and the swap you want to evaluate 2. Read the quality rating first, then the price impact and liquidity detail 3. Check the per-venue breakdown if the headline number looks rough; the picture often varies by venue 4. Generate the AI report when you want the full explanation in writing ### Why this matters A token can look great on a chart and still be untradeable at size. Thin liquidity means entering or exiting moves the price against you, sometimes badly, and it is the kind of risk that only shows up when you try to leave. Checking execution quality before building any position, anywhere, is basic hygiene. This matters double for small-cap and memecoin positions. ### What this is not Execution Intelligence is analysis only. It does not execute swaps, route orders, or connect to your funds, and a Strong rating is not a recommendation to trade. It tells you what the market could absorb, not whether you should act. ### Limits Execution checks with AI reports count against your daily AI allowance, which depends on your plan. See [Pricing](/thecontentforge-docs/reference/pricing.md). ### Related * [Markets](/thecontentforge-docs/investor-intel/markets.md) - exchange availability and spreads for the same asset * [DeFi Intelligence](/thecontentforge-docs/investor-intel/defi-intelligence.md) - liquidity context on the yield side * [Compare](/thecontentforge-docs/investor-intel/compare.md) - execution quality is one axis when comparing two assets --- # 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://thecontentforge.gitbook.io/thecontentforge-docs/investor-intel/execution-intelligence.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.