canonical: https://jentic.com/apis/lotadata.com/lotadata # LotaData The LotaData API returns geocoded events and places across categories and genres. It finds event occurrences in an area, retrieves the details of a specific event, searches venues, landmarks, and regions, and returns the details of a specific place. Responses are JSON, so an agent can discover what is happening near a location or look up a venue without maintaining its own events dataset. ## For AI agents Find geocoded events in an area, look up event details, search places, and retrieve place details. ## Scope Reads geocoded events and places from LotaData; it does not create or edit events, sell tickets, or manage the underlying dataset. ## Capabilities - Find event occurrences within an area - Retrieve details for a specific event - Search venues, landmarks, and regions - Retrieve details for a specific place - Filter events by category and genre - Query results around a geographic point ## Use cases ### Discover events near a location Planning around what is happening in an area starts with finding local events. The LotaData API returns event occurrences in a geographic area, so an application can surface concerts, activities, and gatherings near a point. Each result carries a location and category the caller can filter on. Example prompt: Find event occurrences near the given location and return them. ### Look up event details Once an event is identified, an application often needs its full record. The LotaData API retrieves the details of a specific event by its identifier, returning the information needed to display or act on it. This lets an application enrich a listing without a second data source. Example prompt: Retrieve the details for a specific event by its identifier. ### Search places and venues Mapping activity to real-world locations needs place data. The LotaData API searches venues, landmarks, and regions and returns the details of a specific place, so an application can attach a venue to an event or answer a place query. Results include the geographic context of each place. Example prompt: Search for a venue or landmark and return its details. ### Agent-driven event discovery An AI agent can find local events for a user without a developer wiring each call. Through Jentic the agent matches an intent such as 'what events are near this location' to the LotaData events operation, runs it, and returns the matches. The API key stays in the user's Jentic One instance and never reaches the agent's prompt. Example prompt: Find events near the requested location and return the matching occurrences. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/events` | Find event occurrences in an area. | | GET | `/events/{id}` | Retrieve details for a specific event. | | GET | `/places` | Search venues, landmarks, and regions. | | GET | `/places/{id}` | Retrieve details for a specific place. | ## Key resources - **Events** — Find event occurrences in an area and read event details. - **Places** — Search venues, landmarks, and regions and read place details. ## Why Jentic - **Setup:** Wiring LotaData yourself means managing an API key and handling each events and places query. With Jentic you install once, import LotaData from the API Directory, and store the key a single time. - **Permission scoping:** Jentic lets you grant your agent only the operations it needs, such as reading events and places, and enforces that on every call. - **Credential handling:** Your LotaData API key is stored once, encrypted, by your own Jentic One instance. It is injected when a call runs and never enters the agent's prompt, logs, or context. - **Discovery method:** Agents find LotaData through Jentic's intent search, matching a request like 'find events near this place' to the right operation without hardcoded endpoints. ## Related APIs - **Foursquare Places** — Rich place and point-of-interest data. - **Yelp Fusion** — Local business listings, reviews, and events. - **SeatGeek** — Ticketed events and live event listings. ## FAQ ### What can an AI agent do with the LotaData API through Jentic? An agent can find events near a location, read event details, search places, and read place details. Through Jentic the agent matches an intent to the right operation and runs it with your API key injected at execution time. ### How do I authenticate with the LotaData API? LotaData authenticates requests with an API key passed as the api_key query parameter. You store the key once in your Jentic One instance, and it is added to each call at run time rather than exposed to the agent. ### Can LotaData filter events by category? Yes. The events search accepts a location and returns occurrences that carry category and genre information, so an application can narrow results to the kinds of events it cares about. Each event also includes its place context. ### Does the LotaData API document rate limits? The OpenAPI specification does not state rate limits; request allowances depend on your LotaData plan. Check the current limits for your account in LotaData's documentation. ### Can I control which LotaData operations my agent can call? Yes. Jentic lets you allow only the operations your agent needs, for example searching events and places while withholding others. Your Jentic One instance enforces that boundary on every call and keeps the API key outside the agent's context.