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.com%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.com%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.
Create, update, publish, and delete events under an organization
List and search events, including the public event search surface
Read attendees, orders, and ticket classes for a given event
Create ticket classes to define pricing and capacity for an event
List and create venues an organization reuses across events
GET STARTED
Look up the authenticated user and organization context
Patterns agents use Eventbrite API for, with concrete tasks.
★ Agent-run event setup
An AI agent creates an event under an organization, adds ticket classes with pricing and capacity, and publishes it so registration opens, all from a single conversational instruction rather than clicking through the Eventbrite organizer dashboard.
Create an event titled 'Product Launch' for the organization, add a 100-capacity ticket class priced at 25, and publish it
Attendee and order lookup
An agent answers organizer questions by reading the attendees and orders on an event, returning who registered and what was purchased so a support assistant can resolve queries without opening the web console.
List every attendee for event 123456789 and summarize how many tickets were sold per ticket class
Event discovery assistant
An agent searches the public event listings by keyword and location and returns structured results so a user can find and compare upcoming events in a conversation.
Search Eventbrite for music events happening this month and return the top five by start date
14 endpoints — jentic publishes the only available openapi specification for eventbrite api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/events/search/
Search the public event listings by keyword and filters
/organizations/{organization_id}/events/
Create an event under an organization
/events/{event_id}/publish/
Publish an event so it goes live
/events/{event_id}/attendees/
List the attendees for an event
/events/{event_id}/orders/
List the orders placed against an event
/events/{event_id}/ticket_classes/
Create a ticket class for an event
/events/search/
Search the public event listings by keyword and filters
/organizations/{organization_id}/events/
Create an event under an organization
/events/{event_id}/publish/
Publish an event so it goes live
/events/{event_id}/attendees/
List the attendees for an event
/events/{event_id}/orders/
List the orders placed against an event
/events/{event_id}/ticket_classes/
Create a ticket class for an event
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Eventbrite by hand means registering an OAuth application, carrying a Bearer token on every call, and paging through events, orders, and attendees yourself. Through Jentic you install once, import the Eventbrite API from the Directory, store the token once, and your agent calls it.
Permission scoping
The event and organization ids are path parameters, so scope by operation and by resource: allow the agent the read-only listing and lookup operations it needs while withholding create, update, delete, and publish, or confine it to one organization's events.
Credential isolation
Your Eventbrite OAuth token credential 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 'publish a new event' or 'list the attendees for an event', and Jentic returns the matching Eventbrite API operation with its input schema so the agent calls the right endpoint without reading the reference docs by hand.
Alternatives and complements available in the Jentic catalogue.
Specific to using Eventbrite API through Jentic.
Why is there no official OpenAPI spec for Eventbrite API?
Eventbrite documents its API but does not publish a machine-readable OpenAPI specification. Jentic generates and maintains this spec, validates it against the live API, and keeps it current so agents and developers can call Eventbrite through structured tooling. To get started, install the self-hosted Jentic One runtime from its GitHub repository and import the Eventbrite API from the Jentic API Directory.
What can an AI agent do with the Eventbrite API?
An agent can create, update, publish, and delete events, read their attendees, orders, and ticket classes, search public listings, and manage an organization's venues, covering the event lifecycle end to end.
What authentication does the Eventbrite API use?
Requests carry an OAuth 2.0 Bearer token issued by Eventbrite. Jentic One stores that token encrypted in your own instance and attaches it at execution time.
Can I limit what my agent is allowed to do with the Eventbrite API?
Yes. Because event and organization ids are path parameters, you can scope the agent by operation and by resource: permit read-only listing and lookups while withholding the create, update, delete, and publish operations, or restrict it to a single organization's events.
Does the Eventbrite API handle payments or refunds?
No. The spec reads orders and attendees and manages events, ticket classes, and venues, but it does not process payments, issue refunds, or move funds.
Know of an official OpenAPI document? Contribute it →
For Agents
Create, update, publish, and search events, read their orders, attendees, and ticket classes, and manage an organization's venues across 14 endpoints.
Use for: create a new event for my organization, publish an event so tickets go on sale, search Eventbrite for upcoming events by keyword, list the attendees registered for an event
Not supported: Manages events, ticket classes, venues, and reads orders and attendees. Does not process payments, issue refunds, or handle payout settlement.
Jentic publishes the only available OpenAPI specification for Eventbrite API, keeping it validated and agent-ready. The Eventbrite API creates and manages events, publishes them to an organization, and reads back the orders, attendees, and ticket classes attached to each one. It also searches the public event listings and manages the venues an organization uses, so an agent can run the full lifecycle of an event from creation through attendee lookup against a Bearer-authenticated account.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>