> For the complete documentation index, see [llms.txt](https://docs.predicthq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.predicthq.com/getting-started/predicthq-data/predicted-events.md). # Predicted Events Get insight into events as early as possible, to assess whether they would have an impact on your business. Predicted Events are events that haven’t been scheduled or even announced yet, but are predicted to occur—based on years of historical event, demand, and venue data. This provides a degree of probability for when and where these events will happen to enable you to plan well before anyone else – at scale. Predicted Events have their own status, and you can search and retrieve them just as any other event. Stay up to date with changes to event status, so if the event is ultimately scheduled – it moves from a `predicted` event, to an `active` event with confirmed event details, including start times and more. If the predicted event is canceled or postponed, the event status updates to reflect this. You can see this in both the web UI or via API by setting the `state` filter to `predicted`. --- # 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.predicthq.com/getting-started/predicthq-data/predicted-events.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.