> 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-event-spend.md). # Predicted Event Spend PredictHQ’s Predicted Event Spend is a dollar figure that reflects the predicted amount of consumer spend across **accommodation, hospitality,** and **transportation** in a specific area as a result of events happening nearby. At the core of this figure sits our market leading global event coverage, Predicted Attendance, local accommodation demand, third party data, and more which culminate into a contextual and attributable dollar figure that can be used to power both insights and forecasting models. Predicted Event Spend demonstrates how individual or groupings of events drive massive spending on behalf of visitors and is a reflection of the total amount of additional spending within a defined area as a result of a specific event. All Predicted Event Spend values are in United States Dollars (USD$). ## Coverage Predicted Event Spend is available for the following [event categories](/getting-started/predicthq-data/event-categories.md): * Sports * Conferences * Expos * Concerts * Festivals * Performing Arts * Community Within each event category, Predicted Event Spend covers the following industries/sectors: * Accommodation - Hotels, lodgings, and hosts. * Hospitality - Food and Beverage. Hotel restaurant spend is contained here. * Transportation - Ground-based public and private transportation. ## Using Predicted Event Spend You can access Predicted Event Spend here: * [In the Events API](/api/events/search-events.md) --- # 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-event-spend.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.