Ticket market data API and MCP
Ticker is ticket market data: primary and resale prices, price history and market activity, in the app, your AI or the API.
Ticker MCP turns Claude, or any MCP client, into a research terminal pointed at the live ticket-resale market. Screen ~488,000 live events with a composable predicate DSL, pull deep per-event and per-performer analytics, save Screens as scheduled Views, and fetch the why behind a move, in plain language, from your AI.
Primitives, not verdicts
The server exposes raw analytics (z-scores, cross-sectional percentiles, quartiles, face-value rollups) and lets you compose the screening logic in predicates. There is no verdict tool. You ask the questions; the data answers.
Get started
Connect your AI
Add Ticker MCP to Claude, Cursor, or any client in 30 seconds.
Using the app
Where each thing lives in the app, page by page.
Skills
Free skills that teach your assistant the screens and checks a seller runs.
The predicate DSL
The JSON filter language every Screen and View is built on.
Tools reference
Every tool Ticker MCP exposes, grouped by what it touches.
Data & concepts
Z-scores, the economic floor, freshness, vocabulary.
The tools at a glance
The server exposes 27 tools. Every connection is signed in, so the groups below are what a tool touches, not what it needs.
Screen and search
Find events, performers and venues, check which events Ticker covers, and learn what the predicate DSL accepts.
| screen_events | Finds and ranks upcoming events by price, demand and inventory. |
| search_events | Finds events by name, performer, venue or date, and gives their Ticker event ids. |
| check_coverage | Checks up to 1,000 events at once: the event each one names and the markets Ticker reads for it. |
| list_screen_columns | Lists every column a screen or a View can name, with its meaning, its unit and the plan that includes it. |
| get_venue_schedule | Shows what is on at one venue, its sale dates and weather; finds venues and ids; or shows what each section costs. |
Event and performer analytics
The numbers for one event or performer, their history, the charts, completed sales, and the context behind a move.
| get_event_analytics | Shows every number for one event as it reads now, its sale windows, or with `range` how its numbers read on past dates. |
| get_event_chart | Charts one event over time: its prices and inventory, or its demand. |
| get_event_bundle | Reads one event's analytics, price series and sections in one call, as a short summary or as each part's rows. |
| get_performer_analytics | Shows one performer's numbers now: rank, prices across its events, X activity, or with `view` any of them by date. |
| get_sales | Shows completed sales and primary seats taken, as the Sales tab reads them: a list, a ranking, or per section. |
| research_event | Reads the event's research brief, as its page shows it: recent dated coverage of the event and its performers, with sources. |
Sections, seats and sellers
Inside one event: section prices and counts, the seats behind them, and how concentrated the sellers are, shown anonymously.
| get_event_sections | Shows one event's market by section: prices and tickets over time, the listings on sale, levels, one series across sections, or a map. |
| get_event_sections_live | Shows open seats per section of one event: now, at a past moment, one section or general admission over time, or the house over a window. |
| get_event_seats | Reads primary seats at one event: what is open now or at a past moment, and seats taken by section, and how that changed over time. |
| get_event_sellers | Shows one event's anonymous sellers: how concentrated they are, how they moved hour by hour, or chosen sellers' prices. |
Saved Views and Matches
Save a Screen so it runs on a schedule, say where it delivers, and read the events entering it.
| list_views | Lists your saved Views, whether each is on or paused, how many events each holds, where it delivers and its Digest. |
| create_view | Creates a View: a saved screen that tells you when events enter it, by email or a destination, with an optional Digest. |
| update_view | Changes a saved View: its name, predicate, delivery, destinations, paused state or Digest. |
| delete_view | Deletes a saved View and every Match it recorded, for good. |
| get_view_alert_preview | Shows what one View would have emailed in the last 24 hours under your current settings, and sends nothing. |
| list_matches | Lists the events that entered your Views, newest first, with whether an alert email carried each; or one Match in full. |
| list_destinations | Lists your alert destinations, such as Slack or Discord channels, and how many your plan holds. |
Watchlist
Follow single events and set what a watch fires on.
| watch_event | Stars one event and turns on its alerts, or changes the triggers of an event you starred already. |
| unwatch_event | Takes one event off your watchlist and stops its alerts. |
| list_watchlist | Lists the events you watch, with current prices, the triggers on each, and how many alerts each has made. |
Your account
Your plan, when it renews, and what is left of each allowance.
| get_account | Shows your plan, its state and dates, which gated reads it opens, and how much of each quota and limit is used and left in this cycle. |
Docs search
Answer a how-to question about the app, the API or the MCP server from these pages.
| search_docs | Finds the sections of these docs that best answer a how-to question, each with its page, heading, link and text. |
A typical loop
- Discover columns:
list_screen_columnsto see what you can filter and rank on. - Screen:
screen_eventswith a predicate over those columns, sorted by a ranking primitive. - Drill in:
get_event_analytics/get_performer_analyticson what stands out. - Explain:
research_eventfor the catalyst behind the move. - Watch it:
create_viewso the next dislocation comes to you as an Alert.