Ticker: Live Event Ticket Market

Creates a View: a saved predicate over events that records a Match each time an event enters it and sends alerts by email or to an attached alert destination, with an optional Digest. A new View starts sending alerts at once unless enabled is false. Use it when the person asks to be alerted about every event that meets market conditions. Test the predicate with screen_events first; to change a View that exists use update_view; for alerts on one event use watch_event.

Deletes a View and all its Matches permanently; this cannot be undone. Use it only when the person asks to delete a View. To stop its alerts and keep its Matches, use update_view with enabled false.

Returns the account's plan, its dates, which gated reads the plan opens (capabilities, sales_feed), and how much of each quota and limit is used and left. Use it when the person asks about their plan or usage, and before saying which plan includes a reading. For the items behind a count, use list_views, list_watchlist or list_destinations.

Returns one event's market numbers, whole-event: prices, inventory, demand, recent changes, prediction markets, sale windows and weather. Use it for one event's numbers now; for a section or general admission use get_event_sections. Pass range for how they read on each past date, and view sales whenever the question is about this event's sales: completed resale sales, primary seats taken per section, each market's Sales and Interest. For a chart over time use get_event_chart; to compare many events use screen_events; for the news behind a move use research_event. Current values are dated by their source timestamps; changes_close_date names the UTC close used by changes.

Returns a short summary of one event in one call: its headline prices, listings and demand, where its price series started, ended, bottomed and peaked, and its top sections now. Use it when the person wants an overview of one event that needs more than one of those parts. Pass rows true for each part's full rows. get_event_analytics, get_event_chart and get_event_sections each read one part in full.

Returns one event's price or demand history as a series, with a chart image. Use it when the person asks how an event's prices, listings, interest or sales moved over time. metric price (the default) reads one source at a time, vs resale unless source names another, and never mixes primary and resale. metric demand reads Interest and Sales as whole numbers. For the event's numbers now use get_event_analytics; for one section in finer steps use get_event_sections_live with view series.

Returns individual reserved seats at one event from the primary market's seat data: the seats open now or at a past moment, seats that just came on or off sale, one seat's history, or seats once for sale that are not now. Use it when the person asks about a specific seat or row, or the exact seats open in a section. For open-seat counts per section use get_event_sections_live; for section prices and resale listings use get_event_sections.

Returns market data per section: one event's prices and tickets now and over the last 7 days, its listings on sale, each section's level and neighbors, one series across chosen sections, or the section map as a picture. Use it when the person asks about prices or listings by section, or for an event's cheapest listings. Across a performer's shows or several events, view find answers a section, level, ticket count or price in ONE call: never one call per event. view prices (the default) puts the vs, tm_primary and tm_resale markets side by side by section_key, or reads one market with source. For open-seat counts per section use get_event_sections_live; for single seats use get_event_seats.

Returns open-seat counts per section of one event from the primary market's seat data, now or in the past: every section now with prices and capacity, every section at a past moment, one section over time, general admission sections over time, or every section across a window. Use it when the person asks how many seats are open by section, or how availability changed. For section prices and resale listings use get_event_sections; for single seats use get_event_seats.

Returns anonymous seller data for one event: how much of its inventory the largest sellers hold, how lettered sellers moved hour by hour, and chosen sellers' prices and listings. No seller is named; a letter is an arrival order, not a rank, and matches the event page. Use it when the person asks how concentrated an event's inventory is or how its largest sellers price and list.

Returns one performer's numbers: popularity rank, average prices across its events, listings, X activity and their changes, playoff odds and prediction markets. Use it when the person asks about an artist or team rather than one event. view rank, price or social returns one row per date over range. view list returns a page of performers with no performer_id: use it to list or rank performers by category, sub-category or a number. For one event use get_event_analytics.

Returns completed resale sales and primary seats taken, for one event, performer or venue or the account's watchlist, and as rankings across the whole market. Use it for recent sales records, for the events or sections with the most completed sales or primary seats taken over the last 1 hour to 7 days, or for one event's sales per section by date. A completed sale is one recorded resale sale; primary seats taken counts the seats that went off sale on the primary market, a separate measure. Fields the plan does not include are named in withheld. get_event_analytics with view sales reads one event's completed sales beside each market's Sales and Interest.

Lists one venue's upcoming events, soonest first, with sale dates and the get-in price, plus the venue's roof and a 7-day weather forecast. Use it when the person asks what is on at a venue. view venues finds venues and their ids instead. To filter or rank a venue's events by price, demand or inventory, use screen_events.

Shows what one View would have emailed over the last 24 hours under its owner's current settings, and sends nothing. Use it to check a View's alerts before or after create_view or update_view. For the Matches a View has already recorded, and whether each was sent, use list_matches.

Lists the account's alert destinations (Slack, Discord and other channels besides email) with each id, whether it is paused, and the plan's limit and used count. Use it to find a destination id for create_view or update_view. list_views shows which Views deliver to each. New destinations are added in the Ticker web app under Settings.

Lists Matches: the events that entered the account's Views (saved event filters), newest first, each with its delivery_status. Pass view_id for one View's Matches with a summary of the View, or match_id for one Match in full, with the event's numbers frozen when it entered. Use it to review alert history or to check whether an alert went out: read delivery_status, never a timestamp, for whether an email was sent. For what a View would send, use get_view_alert_preview.

Lists every column a screen_events, create_view or update_view predicate can name, with its meaning, unit and the plan that includes it; view presets lists the preset screens instead. Use it before writing any predicate: column names must be used exactly. Pass search with every word you need in one call (price, demand, inventory, rank, date, category) for only the matching columns. A venue's name is v.venue_name. For the values on one event, use get_event_analytics.

Lists the account's Views. A View is a saved event filter: a predicate that Ticker checks on a schedule, which records a Match when an event enters it and sends alerts by email or to alert destinations. Each row has its predicate, whether it is on or paused, the events it holds now (member_count), its Matches in the last 7 days, its alert destinations and whether it sends a Digest; view_id reads one View. Use it when the person asks about their saved filters or alerts. For the events that entered a View use list_matches; for what one View would email use get_view_alert_preview.

Lists the events the account watches, with current prices, armed triggers, alert counts and alerts_live. Watches of events that ended over a week ago are left out unless include_archived is true. Use it when the person asks which events they watch. For saved Views, use list_views.

Returns the event's research brief, the one its event page shows: recent dated news coverage of the event and its performers, each item a short fact with where it was published, and no live market figures. Use it when the person asks what is happening around an event or why its market moved. A brief from the last 24 hours is served as stored. When the stored brief is older, or force is set, the call gathers a fresh one from the public web, which becomes the brief every account sees on the event page; when one cannot be gathered, the stored brief is served and fetched_at says when it was gathered. For the numbers, use get_event_analytics.

Finds upcoming ticketed events whose market data meets conditions (prices and their changes, listings and tickets, demand and sales, performer rank and odds, sale dates, venue, location and date) and ranks them by any of those columns. Use it when the person asks for events that match such criteria, or for a ranked list across many events, such as the games with the largest price drop this week. Write the predicate over the columns list_screen_columns names, with the grammar the predicate input gives; preset or view_id runs a preset screen or a saved View instead. To find one event by name, performer or venue, use search_events; for every number on one event, use get_event_analytics.

Finds the sections of Ticker's published docs (findticker.com/docs) that best answer a question, each with its page, heading, address and text. Use it when the person asks how to do something in Ticker, where something is in the app, what a page, a setting or a plan feature does, or how the API, the MCP or an export works. Answer from the sections it returns and link the section's url. For market numbers, use the data tools.

Finds ticketed events by name, performer, venue or date, and by on-sale, presale or added dates, and returns their event ids. Use it when the person names an event, act or venue, or when a later call needs an event id. It also lists events a page at a time by category, venue capacity, primary tickets left, TM resale get-in, resale-to-primary or completed sales. To filter or rank events by any other price, demand or inventory number, use screen_events. Rows from other tools already carry event_id and event_url, so a second search for the same event is not needed.

Removes one event from the watchlist. Its alerts stop at once and unsent ones are dropped; past alerts stay in list_matches. Use it when the person asks to stop watching an event. To keep the star and turn its triggers off, use watch_event.

Changes a View that exists: name, predicate, channels, email mode, alert destinations, paused state or Digest. Only the fields passed change, and a change can start, stop or redirect its alerts: enabled true resumes them, and attach_destination and detach_destination add or remove an alert destination. Use it when the person asks to edit, pause or resume a saved View. create_view makes a new one; delete_view removes one permanently.

Stars one event and turns on its alerts, or changes the triggers or email mode of an event already starred; only what you pass changes, and the triggers input lists each trigger and its range. Use it when the person asks to watch one event or to be alerted about it. The plan sets how many starred events alert at once, the newest first; dormanted lists the events this star stopped alerting. For alerts on every event that meets a predicate, use create_view.