> For the complete documentation index, see [llms.txt](https://eigenmaps.gitbook.io/eizen-video-intelligence/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eigenmaps.gitbook.io/eizen-video-intelligence/eizen-video-intelligence.md). # Eizen Video Intelligence Video has become more than just a medium of entertainment; it's now a powerful source of valuable insights and intelligence. Video intelligence is the art of transforming raw video data into actionable information, opening a world of possibilities in diverse fields. Imagine the ability to detect anomalies, track objects, recognize faces, and analyze behaviors—all in real time. Video intelligence is the key to unveiling hidden patterns, enhancing security, optimizing businesses, and revolutionizing decision-making. In this era of AI and technology, video intelligence isn't just a tool; it's a window into a smarter, safer, and more efficient future. Get ready to dive into a world where video becomes a language, and the insights it offers shape the way we live, work, and interact with our environment. --- # 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://eigenmaps.gitbook.io/eizen-video-intelligence/eizen-video-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.