> For the complete documentation index, see [llms.txt](https://vigil-1.gitbook.io/vigil-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vigil-1.gitbook.io/vigil-docs/about-vigil/what-is-vigil.md). # What is Vigil The trading agent that keeps watch while you don't. **Vigil is a 24/7 AI trading agent.** **Trading that never sleeps.** ## What Vigil is * An agent that runs **your** plan, written in your own words * A system that shows you exactly what it will do before it does anything * A watcher that stays on duty through every session, weekend and time zone * A tool where every trigger, decision and fill is logged and explainable ## What Vigil is not * A signal group or a "hot picks" feed * A copy-trading product * A fund or a managed account * A black box that "trades for you" without telling you why * A chatbot you have to keep awake with new commands --- # 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://vigil-1.gitbook.io/vigil-docs/about-vigil/what-is-vigil.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.