Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Eventbrite API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2FEventbrite%2Feventbrite" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2FEventbrite%2Feventbrite" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Eventbrite API.
Search public events by location, date, and keyword using latitude, longitude, and a search radius
Retrieve full event details including venue, organizer, and ticket status by event id
Browse the Eventbrite category taxonomy to refine event searches
Filter event searches by price, format, and start-date range
Sort event search results by date, distance, or best match
GET STARTED
Patterns agents use Eventbrite API for, with concrete tasks.
★ AI Agent Event Discovery
An AI travel or concierge agent connected through Jentic searches Eventbrite for events matching a user's city, date window, and interests, then returns venue, timing, and ticket status. The agent calls the event search operation with location and start-date filters and expands individual events for full details, so a planning assistant can assemble an itinerary without a human browsing the site.
Search Eventbrite for music events within 20 miles of Austin between two dates, then retrieve full details for the top three results
Local Event Aggregation
A city guide or listings site pulls upcoming events by neighborhood using latitude, longitude, and a search radius, refreshing categories and formats so the feed stays current. Eventbrite returns structured event records with venue and timing, which the site renders as a browsable calendar.
Retrieve all events within a 10 mile radius of a set of coordinates and group them by category
Interest-Based Event Alerts
A notification service watches for new events matching a user's chosen categories and price ceiling, querying Eventbrite on a schedule and alerting the user when a matching concert, workshop, or festival is announced. Filters on category, format, and price keep the alerts relevant.
Search for free workshops in a chosen category and return any new events added since the previous run
3 endpoints — the eventbrite api searches public events by location, date, category, and keyword and returns full event details including venue, organizer, and ticket status.
METHOD
PATH
DESCRIPTION
/events/search/
Search public events by location, date, category, and keyword
/events/{event_id}/
Get full details for a single event by its id
/categories/
List the Eventbrite event categories
/events/search/
Search public events by location, date, category, and keyword
/events/{event_id}/
Get full details for a single event by its id
/categories/
List the Eventbrite event categories
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Eventbrite API by hand means registering an OAuth app, handling the bearer token, and building the location and date query parameters yourself. Through Jentic you install once, import Eventbrite from the API Directory, store the token once, and your agent calls the search and detail operations.
Permission scoping
The Eventbrite endpoints are read-only event lookups, so a rule can bound your agent to just the search and single-event operations. You choose which operations it may call, so it can discover and read events and reach nothing more.
Credential isolation
Your Eventbrite 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.
Intent-based discovery
Agents search Jentic by intent such as 'search events by location' or 'get event details', and Jentic returns the matching Eventbrite operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Eventbrite API through Jentic.
What authentication does the Eventbrite API use?
The Eventbrite 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 with the Eventbrite API?
Yes. The event search operation accepts latitude, longitude, and a within radius, plus address, keyword, category, format, price, and start-date range filters, and returns matching public events. Retrieve a single event by its id to get venue, organizer, and ticket details.
Is there an Eventbrite MCP server?
You don't need an MCP server to give your agent the Eventbrite API. Jentic connects it directly from the API Directory: import Eventbrite, store your token once, and your agent calls the event search and detail operations. 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 Eventbrite API?
Yes. Write a rule that permits only the event search and single-event read operations, so the agent can discover and read events but reach nothing else, and every call it makes is logged. You choose which operations it may call, so nothing beyond read access is included unless you add it.
What are the rate limits for the Eventbrite API?
The OpenAPI spec does not specify rate limits. Check the Eventbrite platform documentation at https://www.eventbrite.com/platform for current limits and quota details.
How do I search Eventbrite events through Jentic?
Import the Eventbrite API from the Jentic directory, store your bearer token once, and have your agent search with a query such as 'find events near a location'. Jentic returns the event search operation with its input schema so the agent supplies location and date filters and reads the results. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Know of an official OpenAPI document? Contribute it →
For Agents
Search Eventbrite for public events by location, date, category, and price, and retrieve full event details including venue, organizer, and ticket status. Returns structured event data for discovery, aggregation, and alerting.
Use for: Find all concerts happening near a city this weekend, Search for tech conferences in San Francisco next month, Get the venue and start time for a specific event, List the available event categories on Eventbrite
Not supported: Does not handle ticket purchases, event creation, attendee management, or payments. Use for public event search and discovery only.
The Eventbrite API searches public events by location, date, category, and keyword and returns full event details including venue, organizer, and ticket status. It exposes an OAuth 2.0 bearer-authenticated search operation with latitude, longitude, radius, price, and start-date filters, an operation for retrieving a single event by its id, and a category listing used to refine searches. It reads live event data and is suited to discovery, aggregation, and alerting rather than ticket sales.