> For the complete documentation index, see [llms.txt](https://docs.live-eo.com/surfacescout/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.live-eo.com/surfacescout/surfacescout-product-documentation.md). # SurfaceScout Product Documentation **We monitor changes around critical assets to help our pipeline customers manage third-party interferences and natural risks.** Our AI-powered platform analyzes satellite data to identify issues often missed by traditional inspection methods—detecting four times more real risks, to be exact. **This translates to over €4 million in risk reduction per 1,000 km!** Last but not least, our platform is designed as a single, comprehensive hub, enabling you to efficiently manage thousands of critical Cases and Insights in one place. Get started by clicking this [link](https://surfacescout.live-eo.com/login) to uncover all the details and secrets in the following sections!

--- # 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.live-eo.com/surfacescout/surfacescout-product-documentation.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.