Agent-ready OpenAPI document · curated by JenticE CommerceOrder ManagementapiKey7 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Search for live events, venues, and performers across sports, concerts, and theater. Returns pricing, availability, and personalized recommendations via 7 endpoints.
Use for: Find concerts happening in New York this weekend, I need to get ticket price ranges for a specific NBA game, Search for all Taylor Swift tour dates in 2026, List venues within 50 miles of San Francisco with upcoming events
Not supported: Does not handle ticket purchasing, payment processing, or seat selection - use for event discovery and information retrieval only.
Jentic publishes the only available OpenAPI specification for SeatGeek API, keeping it validated and agent-ready. Search and discover live events, venues, and performers across sports, concerts, and theater with structured filtering by date, location, genre, and popularity score. Retrieve event details including pricing ranges, seat maps, and performer taxonomies, plus get personalized recommendations based on user preferences.
Install Jentic One Beta
Connect the SeatGeek API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SeatGeek 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.
1
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%2Fseatgeek.com%2Fseatgeek" | sh2
Step 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%2Fseatgeek.com%2Fseatgeek" | 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.
Capabilities
What an agent can do with SeatGeek API.
Search events by keyword, date range, venue, performer, or geographic coordinates
Retrieve detailed venue information including capacity, location, and upcoming event schedules
Look up performer profiles with genre classification, popularity scores, and tour dates
Filter events by category (sports, concerts, theater) with granular taxonomy codes
Generate personalized event recommendations based on user preference signals
Use Cases
Patterns agents use SeatGeek API for, with concrete tasks.
★ AI Agent Event Discovery
AI agents use the SeatGeek API through Jentic to help users find and compare live events. An agent can search events by location, date, genre, or performer name and return structured results with pricing and venue details - enabling conversational ticket-finding without manual website browsing. The 7-endpoint surface covers events, venues, performers, and recommendations.
Search for all events within 25 miles of zip code 10001 happening between 2026-06-01 and 2026-06-30 and return the top 5 by popularity score
Event Aggregation and Price Comparison
Aggregate event listings from SeatGeek into comparison tools or travel planning applications. The events endpoint supports filtering by date range, location radius, performer, and venue with pagination for bulk retrieval. Each event response includes lowest and highest price, ticket quantity available, and direct purchase links for price-comparison displays.
Retrieve all NBA events in Los Angeles for June 2026 and compare lowest ticket prices across venues
Venue and Performer Analytics
Build analytics dashboards or recommendation engines using SeatGeek's venue and performer data. Query venue details including capacity, address, and event history. Access performer popularity scores, genre tags, and upcoming tour dates. Combine venue and performer data to identify trending entertainment markets or underserved regions.
Look up venue ID 3713 to get its capacity and address, then list the next 10 upcoming events at that venue
Personalized Event Recommendations
Deliver tailored event suggestions to users based on their preferences and past behavior. The recommendations endpoint returns events ranked by relevance to user signals such as favorite genres, previously attended events, and geographic proximity. Integrate into apps, newsletters, or chatbots for automated event curation without manual editorial effort.
Call the recommendations endpoint for a user who likes rock concerts and lives in Chicago to get their top 5 recommended upcoming events
Key Endpoints
7 endpoints — jentic publishes the only available openapi specification for seatgeek api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/events
Search events by keyword, location, date, and filters
GET
/events/{event_id}
Get detailed information for a specific event
GET
/performers
Search performers by name, genre, or taxonomy
GET
/performers/{performer_id}
Get performer details and upcoming events
GET
/venues
Search venues by name or location
GET
/venues/{venue_id}
Get venue details including capacity and address
GET
/recommendations
Get personalized event recommendations
GET
/events
Search events by keyword, location, date, and filters
GET
/events/{event_id}
Get detailed information for a specific event
GET
/performers
Search performers by name, genre, or taxonomy
GET
/performers/{performer_id}
Get performer details and upcoming events
GET
/venues
Search venues by name or location
GET
/venues/{venue_id}
Get venue details including capacity and address
GET
/recommendations
Get personalized event recommendations
Jentic AI Readiness Score
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.
S
SeatGeek API
- Foundational (D+)47/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility48
AI-Readiness & Agent Experience94
Agent Usability15
Security68
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
48
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
40%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
68
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
68%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SeatGeek API by hand means registering for a client_id, appending it to every query string, and paging through events, performers, and venues yourself. Through Jentic you install once, import SeatGeek from the API Directory, store the client_id once, and your agent calls it.
Permission scoping
The SeatGeek API exposes read-only discovery endpoints, with ids like /events/{event_id} and /performers/{performer_id} used to fetch a single record, so scope by operation: limit the agent to the read operations it needs, such as listing events or fetching a venue, none of which change any data.
Credential isolation
Your SeatGeek client_id 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 'find concerts near a city this weekend' or 'look up a performer', and Jentic returns the matching SeatGeek operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using SeatGeek API through Jentic.
Why is there no official OpenAPI spec for SeatGeek API?
SeatGeek does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call SeatGeek API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the SeatGeek API use?
The SeatGeek API uses a client_id API key passed as a query parameter. Through Jentic, your client_id is stored encrypted in your Jentic One instance and injected automatically into requests - agents never see or log the raw key value.
Can I search for events near a specific location with the SeatGeek API?
Yes. The GET /events endpoint accepts lat, lon, and range parameters to filter events within a geographic radius. You can also filter by postal_code for US-based searches. Combine with datetime_utc filters to narrow results to specific date ranges.
What are the rate limits for the SeatGeek API?
SeatGeek allows up to 1000 requests per hour per client_id for free-tier access. Higher-volume access requires contacting SeatGeek's partnerships team. Exceeding the limit returns a 429 status. Jentic handles rate limit backoff automatically when executing requests.
How do I find upcoming concerts for a performer through Jentic?
Search Jentic for 'find upcoming events for a performer' to discover the GET /performers/{performer_id} operation, which returns the performer's event list. Alternatively, use GET /events with a performers.slug filter to search directly. Execute through Jentic and receive structured JSON with dates, venues, and pricing.
Does the SeatGeek API provide ticket prices?
Yes. Event responses include stats.lowest_price and stats.highest_price fields showing the current ticket price range. Individual listing-level pricing requires SeatGeek's partner API access. The lowest_price field reflects the cheapest available ticket at query time.
Can I limit what my agent is allowed to do with the SeatGeek API?
Yes. Because Jentic One is self-hosted, you run it yourself and your own rules decide which SeatGeek operations and credentials the agent may use. The SeatGeek API exposes only read-only discovery endpoints, so you can scope the agent to just the operations it needs, such as GET /events to list events, GET /venues/{venue_id} to fetch a single venue, or GET /performers to look up an act. None of these operations change any data, and your stored client_id is injected at execution time rather than exposed to the agent.
GET STARTED