canonical: https://jentic.com/apis/PredictHQ/predicthq # PredictHQ Events API The PredictHQ Events API searches real-world events and returns them ranked by predicted attendance and impact. It exposes a single events search operation that filters by keyword, location radius, country, category, date range, and active window, and returns each event with its rank, local rank, and predicted attendance. It reads structured event data and is suited to demand forecasting, planning, and alerting rather than ticketing. ## For AI agents Search PredictHQ for real-world events filtered by keyword, location, country, category, and date, returning each with predicted attendance and rank. Returns structured event data for demand forecasting, planning, and alerting. ## Scope Does not sell tickets, manage attendees, or create events. Use for event data search and ranking only. ## Capabilities - Search real-world events by keyword, location radius, and country - Filter events by category, date range, and active window - Rank results by predicted attendance and local or global rank - Page through results with limit and offset controls - Sort events by rank, relevance, or date ## Use cases ### AI Agent Demand Signals An AI planning agent connected through Jentic searches PredictHQ for events near a business location and reads back their predicted attendance and rank to explain expected demand spikes. The agent filters by category and date range, so a forecasting assistant can flag the concerts, sporting fixtures, and conventions likely to move footfall. Example prompt: Search PredictHQ for events within 20 km of a store over the next month and return them ranked by predicted attendance ### Location-Based Event Feeds A market intelligence tool pulls upcoming events by country and location radius, filtering on category and active window so the feed reflects what is happening in each region. PredictHQ returns structured records with rank and attendance, which the tool aggregates into a demand calendar. Example prompt: Retrieve active events in a country for a date range and group them by category and rank ### Attendance-Ranked Alerts A notification service watches for high-impact events entering a region by querying PredictHQ on a schedule and filtering on rank and predicted attendance. When a major event is detected the service alerts staffing or pricing systems to prepare for the demand. Example prompt: Search for events above a chosen rank near a location and alert when a new one appears ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/v1/events/` | Search real-world events filtered by location, category, and date, ranked by predicted attendance | ## Key resources - **Events** — Search real-world events filtered by keyword, location, country, category, and date, ranked by predicted attendance and impact ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 63 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 74 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 46 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 63 / 100 - **View full report:** https://jentic.com/apis/PredictHQ/predicthq/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the PredictHQ API by hand means registering an app, handling the bearer token, and shaping the location, category, and rank filters yourself. Through Jentic you install once, import PredictHQ from the API Directory, store the token once, and your agent calls the events search operation with structured inputs. - **Permission scoping:** The PredictHQ endpoint is a read-only events search, so a rule can bound your agent to just that one operation. You choose which operations it may call, so it can read ranked event data and reach nothing else in your account. - **Credential handling:** Your PredictHQ bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'search ranked events' or 'events near a location', and Jentic returns the matching PredictHQ operation with its input schema so the agent calls it without reading the reference docs. ## Related APIs - **Ticketmaster Discovery API** — Ticketmaster Discovery lists ticketed events, attractions, and venues. - **SeatGeek API** — SeatGeek surfaces live events with ticket pricing for sports and concerts. - **Eventbrite API** — Eventbrite searches community and professional events by location and category. ## FAQ ### What authentication does the PredictHQ Events API use? The PredictHQ Events API authenticates with an OAuth 2.0 bearer token per its OpenAPI spec: you pass the token in the Authorization header as a bearer credential on each request. Through Jentic the token is stored once, encrypted, by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs. ### Can I search events by location and rank with the PredictHQ API? Yes. The events search operation accepts a location radius, country, keyword, category, and date range, and returns each event with its rank, local rank, and predicted attendance. You can sort and page the results to focus on the highest-impact events first. ### Is there a PredictHQ MCP server? You don't need an MCP server to give your agent the PredictHQ API. Jentic connects it directly from the API Directory: import PredictHQ, store your token once, and your agent calls the events search operation. Discovery happens on demand, so no extra server's tool definitions sit in the agent's context. ### Can I limit what my agent is allowed to do with the PredictHQ API? Yes. Write a rule that permits only the events search operation, so the agent can read ranked event data but reach nothing else in your PredictHQ account, and every call it makes is logged. You choose the operations it may call, so nothing beyond read access is included unless you add it. ### What are the rate limits for the PredictHQ Events API? The OpenAPI spec does not specify rate limits. Check the PredictHQ documentation at https://www.predicthq.com for current limits and quota details. ### How do I search PredictHQ events through Jentic? Import the PredictHQ API from the Jentic directory, store your bearer token once, and have your agent search with an intent such as 'ranked events near a location'. Jentic returns the events search operation with its input schema so the agent supplies the filters and reads the ranked results. To run it on your own infrastructure, install Jentic One from its GitHub repo.