> 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 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 will be able to 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 will move 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 will be updated to reflect this. You will be able to 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 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://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 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.