For ticket work, pick the assistant that can read ticket market data and your inventory file. ChatGPT and Claude both take custom connectors and spreadsheet uploads, Gemini suits sellers whose inventory lives in Google Sheets, and Perplexity answers best from public web pages.
The three things that matter
- Market data. Can it call a ticket data service through a connector? Without one, every price is a guess.
- Your file. Can it read your inventory sheet and write a column back?
- Your rules. Can you save pricing instructions once and reuse them in every chat?
| Assistant | Market data | Your file | Your rules |
|---|---|---|---|
| ChatGPT | Apps and custom connectors built on MCP | Reads CSV and Excel uploads and runs analysis on them | Projects, custom instructions, custom GPTs |
| Claude | Custom connectors built on MCP | Reads CSV and Excel uploads and runs analysis on them | Projects with project instructions |
| Gemini | Connects to Google apps; check your plan for outside connectors | Works inside Google Sheets | Gems |
| Perplexity | Searches the public web and cites its sources | Reads uploaded files | Spaces with instructions |
Features change often. Check each vendor's help pages before you commit.
Why market data decides it
Marketplace floors for one event can sit far apart. For Death Becomes Her, the lowest all-in price ran from $74 on Gametime to $246.85 on Ticketmaster resale. An assistant reading one web page sees one of those numbers. Ask any assistant lowest price on each marketplace and compare its answer with the worked one.
A quick test before you pick
Run the same three prompts in each assistant you are weighing: lowest price on each marketplace, tickets listed in each section and how wide the price range is. The one whose answers match the worked numbers, with fees stated and sources named, is the one to keep.
Connect Ticker MCP to ChatGPT, Claude, Cursor or Perplexity.