Every TicketData price signal for any event, performer, or venue, plus a local price-history store for trend math, drift alerts, and cross-event comparisons no ticket tool ships.
TicketData tracks each event's get-in price (the lowest all-in resale price across marketplaces), its full price history, a forecast, and 3/7/14/30-day change. This CLI exposes all of it as scriptable, agent-native JSON and keeps the raw price series in local SQLite, so stats can compute historical lows and volatility, drift can alert when a floor drops to your target, board can rank your whole watchlist, and compare can pick the cheapest date, none of which the website surfaces.
Authentication
No account or API key. TicketData's public data API is open; this CLI reads it directly.
Quick Start
# Confirm the CLI can reach the TicketData data API.
ticketdata-pp-cli doctor --dry-run
# Resolve a name to its canonical performer and stats.
ticketdata-pp-cli performers search --query "ariana grande"
# Get an event's current get-in price, forecast, and N-day change.
ticketdata-pp-cli events get 22323960 --agent
# Track the event so sync starts building its local history.
ticketdata-pp-cli watch add 22323960
# See the historical low, percentile, and best day to buy.
ticketdata-pp-cli stats 22323960 --agent
Unique Features
These capabilities aren't available in any other tool for this API.
Local price store that compounds
-
watch — Track a set of events locally so one sync re-fetches all their current prices.
Reach for this first: everything downstream (board, drift, stats, compare) reads the watchlist the CLI syncs.
ticketdata-pp-cli watch add 22323960
-
board — One sortable table of every watched event: get-in price, N-day change, forecast direction, and where today sits in its own history.
Use it for a whole-watchlist snapshot; for what changed since last sync use drift, for one event's distribution use stats.
ticketdata-pp-cli board --sort change --agent
-
drift — Diff the two most recent snapshots per watched event, flag floors that moved past a threshold, and fire price-target hits.
Use it for what moved since the last sync and for buy-when-it-hits-my-price alerts.
ticketdata-pp-cli drift --threshold 10 --target 22323960=150 --agent
Price intelligence the site chart hides
-
stats — Historical low/high, median, current percentile, volatility, and the weekday the floor is typically lowest, from the local price series.
Use it to judge whether today's get-in price is actually low for one event and which day tends to be cheapest.
ticketdata-pp-cli stats 22323960 --agent
-
compare — Rank multiple watched events, or all of one performer's watched events, by get-in price and percent change.
Use it to pick the cheapest city or date; for a single event's own history use stats.
ticketdata-pp-cli compare --performer ariana-grande --agent
-
zones — Rank an event's zones by current get-in price and by each zone's drop versus its own history to surface the underpriced section.
Use it to pick a section by value; for the plain section-name catalog use events sections.
ticketdata-pp-cli zones 22323960 --agent
Agent-native plumbing
-
search — Local full-text search across synced events, performers, and venues, returning multiple matches.
Use it to browse offline matches; for the single canonical resolve of a name use performers search or venues search.
ticketdata-pp-cli search "ariana" --type performers --agent
Recipes
Is this ticket cheap right now?
ticketdata-pp-cli watch add 22323960 && ticketdata-pp-cli sync && ticketdata-pp-cli stats 22323960 --agent
Track the event, pull its history, and see where today's get-in price sits in its own distribution.
Alert me when a floor drops to my price
ticketdata-pp-cli drift --target 22323960=150 --threshold 8 --agent
Flags target hits and any floor that moved more than 8% since the last sync.
Which date is cheapest for this artist?
ticketdata-pp-cli compare --performer ariana-grande --agent
Ranks all of the performer's watched events by get-in price and percent change.
Narrow a large event payload for an agent
ticketdata-pp-cli events get 22323960 --agent --select tickets.get_in_price,tickets.number_of_listings,forecast_value,price_trend.direction
Pulls only the decision-relevant fields from the verbose event response using dotted select paths.
Find the best-value section
ticketdata-pp-cli zones 22323960 --agent
Ranks the event's zones by current get-in price and by each zone's drop versus its own history.
Usage
Run ticketdata-pp-cli --help for the full command reference and flag list.
Paths & environment variables
This CLI separates local files into four path kinds:
| Kind | Contents |
|---|
config | User-editable settings such as config.toml and saved profiles |
data | Durable local data such as data.db |
state | Runtime state such as persisted queries, jobs, and teach.log |
cache | Regenerable HTTP/cache files |
Each kind resolves independently. The ladder is:
- Per-kind env var:
TICKETDATA_CONFIG_DIR, TICKETDATA_DATA_DIR, TICKETDATA_STATE_DIR, or TICKETDATA_CACHE_DIR
--home <dir> for this invocationTICKETDATA_HOME for a flat relocated root- XDG env vars:
XDG_CONFIG_HOME, XDG_DATA_HOME, XDG_STATE_HOME, XDG_CACHE_HOME
- Platform defaults matching existing installs
For containers and agent sandboxes, prefer a single relocated root:
export TICKETDATA_HOME=/srv/ticketdata
ticketdata-pp-cli doctor
Under TICKETDATA_HOME=/srv/ticketdata, the four dirs resolve to /srv/ticketdata/config, /srv/ticketdata/data, /srv/ticketdata/state, and /srv/ticketdata/cache.
MCP servers do not receive CLI flags from the host. Put relocation in the host env block:
{
"mcpServers": {
"ticketdata": {
"command": "ticketdata-pp-mcp",
"env": {
"TICKETDATA_HOME": "/srv/ticketdata"
}
}
}
}
Precedence matters in fleets: an ambient per-kind variable such as TICKETDATA_DATA_DIR overrides an explicit --home for that kind. Use TICKETDATA_HOME or the per-kind variables for durable fleet relocation; treat --home as the weaker per-invocation lever.
Relocation is one-way. Unsetting TICKETDATA_HOME does not move files back to platform defaults, and doctor cannot find files left under a former root. Move the files manually before unsetting relocation variables.
Existing installs keep working because the platform-default rung matches the legacy layout. Run ticketdata-pp-cli doctor --fail-on warn to check path warnings in automation.
Commands
events
Look up ticket events, their get-in price, price history, and section catalog
ticketdata-pp-cli events get - Get an event's current get-in price, forecast, N-day change, marketplace links, and venue/performer detailticketdata-pp-cli events history - Get the full get-in-price time series for an event (hundreds of points), plus per-zone series and on/presale datesticketdata-pp-cli events sections - List the section names catalogued for an event
performers
Look up performers (artists, teams) and resolve names to canonical performer pages
ticketdata-pp-cli performers get - Get a performer's stats (upcoming events, avg/min/max get-in price) and resale/social linksticketdata-pp-cli performers search - Resolve a search query to the best-matching performer
venues
Look up venues and resolve names to canonical venue pages
ticketdata-pp-cli venues get - Get a venue's stats (upcoming events, location)ticketdata-pp-cli venues search - Resolve a search query to the best-matching venue
Self-learning loop
This CLI caches per-question discovery so repeat queries skip the walk and structurally similar queries get answered via entity substitution. The loop also self-captures: every invocation is journaled locally, and failed-flag corrections plus fresh teaches surface as candidates on the next recall for confirm/reject judgment. Agents call recall before discovery and fire teach & after answering. See the ## Automatic learning section in SKILL.md for the full protocol.
ticketdata-pp-cli recall <query> - Look up cached resources for a query before running discoveryticketdata-pp-cli teach - Record a query -> resource mapping (silent on success, safe to background with &)ticketdata-pp-cli learnings list - Inspect taught rowsticketdata-pp-cli learnings forget <query> - Undo a teachticketdata-pp-cli learnings candidates - List auto-captured candidates awaiting confirm/rejectticketdata-pp-cli learnings stats - Local loop metrics: recall hit rate, teach-to-reuse, playbook resolution, candidate countsticketdata-pp-cli teach-pattern - Install a query/resource template up frontticketdata-pp-cli teach-lookup - Add an entity mapping (e.g. country code, team alias) for pattern substitution
Pass --no-learn or set TICKETDATA_NO_LEARN=true to disable the loop for deterministic flows.
The local store's schema version stamp is one-way: once this version of ticketdata-pp-cli opens the database, older binaries refuse it with a version error — upgrade the binary rather than downgrading.
Output Formats
# Human-readable table (default in terminal, JSON when piped)
ticketdata-pp-cli events get mock-value
# JSON for scripting and agents
ticketdata-pp-cli events get mock-value --json
# Filter to specific fields
ticketdata-pp-cli events get mock-value --json --select id,name,status
# Dry run — show the request without sending
ticketdata-pp-cli events get mock-value --dry-run
# Agent mode — JSON + compact + no prompts in one flag
ticketdata-pp-cli events get mock-value --agent
Agent Usage
This CLI is designed for AI agent consumption:
- Non-interactive - never prompts, every input is a flag
- Pipeable -
--json output to stdout, errors to stderr
- Filterable -
--select id,name returns only fields you need
- Previewable -
--dry-run shows the request without sending
- Read-only by default - this CLI does not create, update, delete, publish, send, or mutate remote resources
- Offline-friendly - sync/search commands can use the local SQLite store when available
- Agent-safe by default - no colors or formatting unless
--human-friendly is set
Exit codes: 0 success, 2 usage error, 3 not found, 5 API error, 7 rate limited, 10 config error.
Health Check
ticketdata-pp-cli doctor
Verifies configuration and connectivity to the API.
Configuration
Run ticketdata-pp-cli doctor to see the resolved config, data, state, and cache directories. The platform-default config path is ~/.config/ticketdata/config.toml; --home, TICKETDATA_HOME, and per-kind env vars can relocate it.
Static request headers can be configured under headers; per-command header overrides take precedence.
Troubleshooting
Not found errors (exit code 3)
- Check the resource ID is correct
- Run the
list command to see available items
API-specific
- A command returns an empty board or 'no data' for stats/drift/compare — Run
ticketdata-pp-cli sync first; these read the local store, which is empty until you watch events and sync.
- Intermittent HTTP 403 / Cloudflare challenge — Retry; the CLI ships a Chrome-fingerprint HTTP transport that clears it. Persistent 403s usually mean a transient challenge, not a block.
- events get returns found=false — The event id no longer exists on TicketData. Re-resolve it with
performers search then look up the performer's current events on the site.
HTTP Transport
This CLI uses Chrome-compatible HTTP transport for browser-facing endpoints. It does not require a resident browser process for normal API calls.
Generated by CLI Printing Press