AI

Tickets.dev AI

This repo is the home for using Tickets.dev with AI agents. Tickets.dev returns live ticket listings, all-in prices and seat maps from Ticketmaster, StubHub, SeatGeek, Vivid Seats, TickPick, Gametime, Viagogo and more, in one schema.

Tickets.dev is a standard HTTP API, so any agent that can make web requests can use it. This repo adds an agent skill, plugins for popular agent tools, and how to connect the hosted MCP server.

What you can ask

I have 2 seats in section 110, row 36 for the Eagles at Sphere. What are the same and nearby seats listed for on each marketplace?

Show the seat map for this StubHub event with the cheapest all-in price in each section.

How many tickets are listed for each Sphere show next month, and what's the get-in price?

Write a script that saves the listed tickets and get-in price for these events every morning.

Use the API with any agent

Give your agent the OpenAPI spec, the agent docs and your API key. Get a key at tickets.dev and send it in the x-api-key header.

Most tasks take two calls. Find the event, then capture one marketplace page:

curl "https://api.tickets.dev/v1/events?query=eagles%20sphere" \

-H "x-api-key: $TICKETS_DEV_KEY"

curl -G "https://api.tickets.dev/v1/capture" \ --data-urlencode "url=https://www.ticketmaster.com/eagles-live-at-sphere-las-vegas-nevada-12-11-2026/event/17006483D6FAFC60" \ -H "x-api-key: $TICKETS_DEV_KEY"

Agent skill

The tickets-dev skill covers the details of ticket data that agents tend to get wrong, such as all-in prices, sellable quantities, and why a listing that disappears isn't proof of a sale. It's plain Markdown, so you can add it to any agent's instructions.

Plugins

If you use one of these agent tools, we recommend installing the Tickets.dev plugin. It includes the skill and tools your agent can call directly. The first time the tools are used, you sign in at tickets.dev and approve the connection, so there's no API key to copy.

Claude Code

Run these commands in Claude Code:

/plugin marketplace add Tickets-dot-dev/ai

/plugin install tickets-dev@tickets-dev

Then run /mcp, pick tickets-dev and choose Authenticate to sign in.

Codex

Run this command:

codex plugin marketplace add Tickets-dot-dev/ai

Then restart Codex, install Tickets.dev from the Plugins directory, and sign in:

codex mcp login tickets-dev

Cursor

Install the plugin from cursor.directory, or use the MCP server.

Gemini CLI

Run this command:

gemini extensions install https://github.com/Tickets-dot-dev/ai

Then run /mcp auth tickets-dev in Gemini CLI to sign in.

Grok Build

The plugin is coming to the Grok Build marketplace. Until then, use the MCP server.

MCP server

The tools are hosted at https://api.tickets.dev/mcp (Streamable HTTP).

Add that URL and sign in. You'll be sent to Tickets.dev to sign in and approve the connection, which creates an API key for that app. Disconnect it any time from your account settings.

In Claude Code:

claude mcp add --transport http tickets-dev https://api.tickets.dev/mcp

Then run /mcp, pick tickets-dev and choose Authenticate.

In Claude or ChatGPT, add it as a custom connector with the same URL.

In clients that take a URL, for example .cursor/mcp.json:

{

"mcpServers": { "tickets-dev": { "url": "https://api.tickets.dev/mcp" } } }

For scripts and clients that can't sign in, send an API key as a header instead, for example "headers": { "Authorization": "Bearer tk_live_..." }, or in Claude Code --header "Authorization: Bearer $TICKETS_DEV_KEY".

Clients that only start local servers, such as Claude Desktop's claude_desktop_config.json, can run the tickets-dev-mcp package. It's a small bridge that forwards to the same hosted server:

{

"mcpServers": { "tickets-dev": { "command": "npx", "args": ["-y", "tickets-dev-mcp"], "env": { "TICKETS_DEV_KEY": "tk_live_..." } } } }

The tools only read data. They can't buy, hold or list tickets.

API key

You only need a key for the HTTP API, scripts, and clients that can't sign in. The tickets-dev-mcp package and the skill's direct API calls read it from the TICKETS_DEV_KEY environment variable:

export TICKETS_DEV_KEY=tk_live_...

Restart your agent after setting it. Don't paste your key into a chat. If the key is missing, the agent tells you how to add it.

Each capture of one event on one marketplace is billed, the same as a direct API call. One tool call uses at most 15 captures, and up to 3 tool calls can run at once per account. See pricing.

More from Tickets.dev

• API documentation
• Guides: compare ticket prices across marketplaces, price and inventory alerts
• Examples: price comparison app, price alerts, price tracker

Development

npm install

node --test # offline tests TICKETS_DEV_E2E_KEY= node --test # end-to-end through api.tickets.dev/mcp (uses a few captures)

License

MIT. Not affiliated with any ticket marketplace.