Pp Ticketdata

<!-- GENERATED FILE — DO NOT EDIT.
     This file is a verbatim mirror of library/media-and-entertainment/ticketdata/SKILL.md,
     regenerated post-merge by tools/generate-skills/. Hand-edits here are
     silently overwritten on the next regen. Edit the library/ source instead.
     See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->

TicketData — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the ticketdata-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install ticketdata --cli-only

2. Verify: ticketdata-pp-cli --version
3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:

go install github.com/mvanhorn/printing-press-library/library/media-and-entertainment/ticketdata/cmd/ticketdata-pp-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

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.

When to Use This CLI

Use this CLI when you need TicketData's get-in price, price history, forecast, or N-day change for specific events, performers, or venues, and especially when you want to track a set of events over time, compute historical price stats, alert on price drops, or compare events, all offline and scriptable. It is ideal for agents answering 'is this ticket cheap right now', 'when should I buy', or 'which of these dates is cheapest'.

Anti-triggers

Do not use this CLI for:

• Do not use this CLI to buy, sell, or list tickets; TicketData is a price tracker, not a marketplace. Use the marketplace buy links from events get and complete the purchase there.
• Do not use it to browse or discover all events in a category; TicketData exposes no list/browse API, so this CLI works from event ids and performer/venue slugs you already have or resolve by name.
• Do not use it for primary on-sale ticket purchasing or seat selection; use the marketplace or box office.

Unique Capabilities

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

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.

Command Reference

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 detail
• ticketdata-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 dates
• ticketdata-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 links
• ticketdata-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

Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

ticketdata-pp-cli which "<capability in your own words>"

which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.

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.

Auth Setup

No account or API key. TicketData's public data API is open; this CLI reads it directly.

Run ticketdata-pp-cli doctor to verify setup.

Agent Mode

Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.

• Pipeable — JSON on stdout, errors on stderr

• Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:

  ticketdata-pp-cli events get mock-value --agent --select id,name,status

• Previewable — --dry-run shows the request without sending

• Offline-friendly — sync/search commands can use the local SQLite store when available

• Non-interactive — never prompts, every input is a flag

• Read-only — do not use this CLI for create, update, delete, publish, comment, upvote, invite, order, send, or other mutating requests

Response envelope

Commands that read from the local store or the API wrap output in a provenance envelope:

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.

Paths and state

Agents should treat the CLI's path resolver as part of the runtime contract:

• Use --home <dir> for one invocation, or set TICKETDATA_HOME=<dir> to relocate all four path kinds under one root.

• Use per-kind env vars only when a specific kind must diverge: TICKETDATA_CONFIG_DIR, TICKETDATA_DATA_DIR, TICKETDATA_STATE_DIR, TICKETDATA_CACHE_DIR.

• Resolution order is per-kind env var, --home, TICKETDATA_HOME, XDG (XDG_CONFIG_HOME, XDG_DATA_HOME, XDG_STATE_HOME, XDG_CACHE_HOME), then platform defaults.

• config contains settings like config.toml and profiles. data contains credentials.toml, data.db, cookies, and auth sidecars. state contains persisted queries, jobs, and teach.log. cache contains regenerable HTTP/cache files.

• Stored secrets live in credentials.toml under the data dir. Existing legacy config.toml secrets are read for compatibility and leave config.toml on the first auth write.

• Run ticketdata-pp-cli doctor --fail-on warn to surface path and credential-location warnings. agent-context exposes a schema v4 paths block for agents that need the resolved dirs.

• For MCP, pass relocation through the MCP host config. The MCP binary does not inherit CLI flags:

  {
    "mcpServers": {
      "ticketdata": {
        "command": "ticketdata-pp-mcp",
        "env": {
          "TICKETDATA_HOME": "/srv/ticketdata"
        }
      }
    }
  }

Fleet precedence: an inherited per-kind env var overrides an explicit --home for that kind. Use TICKETDATA_HOME or per-kind vars as durable fleet levers, and use --home only for a single invocation. Relocation is not reversible by unsetting env vars; move files manually before clearing TICKETDATA_HOME, or doctor will not find credentials left under the former root.

Automatic learning

This CLI ships a self-capturing learning loop. The CLI does its own bookkeeping: every invocation is journaled locally, a failed flag followed by a corrected retry auto-derives a flag_alias candidate, and a teach on a query family without a playbook auto-synthesizes a playbook_candidate from the session's journal. Your job is judgment only: recall first, act on surfaced candidates, teach the final answer, playbook amend when you observe a correction. You never record failures by hand.

Step 1: recall before any discovery

Before list/search/drill commands on a new user question, run:

ticketdata-pp-cli recall "<user's question>" --agent

The response envelope:

{
  "query": "...",
  "normalized": "<normalized form>",
  "query_entities": ["..."],
  "found": true | false,
  "match_score": 0.0,
  "results": [
    { "resource_id": "...", "resource_type": "...", "venue": "...",
      "confidence": 2, "entity_match": "exact|partial|unknown",
      "source": "taught|preseed|pattern", "warnings": ["..."] }
  ],
  "mismatches": [ /* only when --debug-mismatches */ ],
  "warnings": [ /* top-level */ ],
  "candidates": [
    { "id": 12, "class": "flag_alias | playbook_candidate",
      "summary": "...", "sightings": 3, "last_seen": "...",
      "rationale": "...",
      "next_action": ["<trial command>", "ticketdata-pp-cli learnings confirm 12"] }
  ],
  "playbook": {
    "query_family": "...",
    "playbook": {
      "steps": [ { "cmd": "<command with {slot} substitution>", "purpose": "..." } ],
      "entity_slots": ["$ENTITY"],
      "expected_tool_calls": 3
    },
    "slots_resolved": { "$ENTITY": { "token": "<live token>", "canonical": "<canonical>" } },
    "notes": "<workarounds + gotchas for this query family>"
  },
  "notes": "<duplicate surface for non-playbook callers>"
}

Empty-store short-circuit: if the store has no learnings, playbooks, or candidates yet (recall finds nothing and learnings list and learnings candidates are both empty), skip recall for the rest of this session instead of taxing every query; resume recall-first once something has been taught.

Step 2: decision tree

Read candidates, playbook, notes, results[0], and warnings in that order:

if Candidates present (warnings include "candidates_present"):
    -> candidates are try-then-confirm, never facts. Follow each candidate's
       two-step next_action verbatim: run the trial command first, then run
       `learnings confirm <id>` only after the trial verified the behavior.
       Reject a wrong candidate with `learnings reject <id>`.
    -> NEVER re-teach something recall surfaced as a candidate; confirm or
       reject that candidate instead of teaching a duplicate.
    -> candidates ride alongside playbooks and resource hits, not instead of
       them; continue with the branches below after acting on them.

if Playbook present:
    -> READ Playbook.notes verbatim FIRST (workarounds + gotchas the CLI surface doesn't expose)
    -> replay Playbook.steps in order, substituting Playbook.slots_resolved entries
       for the entity slot tokens. If a step's slot is unresolved, fall back to
       discovery for that step only.
    -> the Playbook's expected_tool_calls is a budget; if you find yourself running
       materially more, record the divergence via `ticketdata-pp-cli playbook amend`
       at end-of-session.

elif Notes present (no Playbook):
    -> read Notes verbatim before any discovery step; they carry known gotchas
       for this query family even when no structured choreography exists yet.

elif Found AND Results[0].EntityMatch == "exact" AND Results[0].Confidence >= 2:
    -> skip discovery; fetch live data for Results[*].ResourceID in parallel

elif Found AND Results[0].EntityMatch == "partial":
    -> candidate hint, NOT a hit; read the resource title to validate before trusting

elif (any row in Mismatches[] when --debug-mismatches was passed):
    -> treat as cold start; the stored learning is for a different entity
       (different canonical resolved from query_entities)

else:  // Found == false, no playbook, no notes
    -> cold start; run discovery normally; teach the answer afterward (Step 4).
       If the family has no playbook yet, that teach auto-synthesizes a
       playbook candidate from this session's journal - you do not need to
       record one by hand.

Playbook and Notes are orthogonal to the per-resource path. A recall response can carry both a Playbook AND a Results[] hit - use both: the Playbook tells you which choreography to run; the resource hits short-circuit specific steps. Default to skipping mismatches; pass --debug-mismatches only when investigating cold-start surprises.

Candidate judgment details: learnings confirm <id> prints the candidate's full payload before materializing it - check that the printed payload matches the behavior you verified. learnings reject <id> tombstones the derivation signature so the same candidate does not resurface. The envelope carries only the few candidates worth acting on now; ticketdata-pp-cli learnings candidates lists the full open set.

Graceful degradation: if learnings confirm is an unknown command, you are driving an older binary - ignore the candidates guidance and follow the rest of the protocol.

Step 3: always read warnings

• low_confidence: row exists at confidence<2. Treat as a hint, not a skip-discovery hit.
• resource_not_in_store: the local store doesn't have the resource the learning points at. The match validator couldn't classify entities — direct-fetch and re-evaluate.
• cross_alias_match (per-result): the row was taught under a different alias and matched the live query's canonical via entity_lookups (e.g., a "USA" teach satisfying a "United States" recall). Trust the resource_id.
• similar_shape_different_entity:<canonical> (top-level): a structurally matching row exists but its canonical entity differs from the live query's. Treated as cold start; the warning carries the conflicting canonical as a hint, but the row is NOT promoted into Results.
• ambiguous_alias (top-level): a single query entity resolved to multiple canonicals (e.g., "Cards" → Arizona Cardinals + St. Louis Cardinals). Surface the ambiguity from context before committing to a resource.
• candidates_present (top-level): the envelope carries a candidates section. Handle it via the candidates branch in Step 2 before anything else.
• lookup_refresh_available (top-level): an entity in the query has no lookup row yet, but synced data could provide one. Run ticketdata-pp-cli sync to refresh entity lookups.
• Top-level no_learnings_for_query_family: the table had no rows above the Jaccard floor. Pure cold start.