Vivid Seats icon Tickets MCP

Vivid Seats MCP

Launch ticket discovery, event search, and ticket-browsing experiences inside your AI product without building and maintaining your own ticketing integration stack.

  • check_circle Ship event discovery and ticket-shopping UX faster than building a direct partner integration yourself
  • check_circle Returns widget-ready custom_attachments for event and ticket carousels
  • check_circle Includes lookup helpers for performer, venue, category, and location resolution so agents stay precise

Quickstart

{
  "tool": "SearchEvents",
  "arguments": {
    "query": "Taylor Swift",
    "dateStart": "2026-04-10",
    "sortBy": "DATE"
  }
}

{
  "tool": "BrowseTicketsForEvent",
  "arguments": {
    "eventId": 6641236,
    "quantityNeeded": 2,
    "section": "Section 6"
  }
}

If you want this ticketing surface in your app, reach out and we can enable access and help wire it into your agent UX.

Tools

The public surface is designed for real AI shopping and discovery workflows: one event-search tool, one ticket-browsing tool, and the lookup helpers needed to keep results precise and production-ready.

Core tool

SearchEvents

stadium

Search for live events and return an event carousel with images, dates, venues, pricing bands, and IDs you can pass into BrowseTicketsForEvent.

Common inputs

  • query
  • performerId, venueId
  • dateStart, dateEnd

Useful filters

  • lat, lng, radius
  • categoryId, subCategoryId
  • sortBy, excludeParking

Returns

  • structuredContent.context[]
  • structuredContent.custom_attachments[]
  • _meta.openai/outputTemplate

Core tool

BrowseTicketsForEvent

confirmation_number

Fetch ticket listings for one event. This is the ticket-detail surface: it returns listing IDs, sections, rows, prices, delivery methods, seat views, section/group summaries, and checkout links.

Required input

  • eventId

Useful filters

  • quantityNeeded
  • section
  • minPrice, maxPrice
  • deliveryMethod

Returns

  • availableSections[]
  • availableGroups[]
  • listings[]
  • custom_attachments[]

Lookup helpers

Resolver tools

search

These helper tools make the main event and ticket calls more precise by resolving user text into stable IDs or coordinates.

LookupSearchSuggestions resolves performer, team, venue, or event names.

LookupLocation resolves a location string into lat, lng, and radius.

LookupCategory returns category and subcategory IDs.

LookupEvent returns event IDs without rendering the event carousel.

SearchPoliciesReference searches policy/reference content when the policy docs need a direct lookup.

Response JSON

The Vivid Seats MCP is built for agent experiences that need to show real inventory, not just summarize it. The important fields are the human context lines, the custom_attachments array that drives the carousel, and the promoted openai/outputTemplate metadata.

custom_attachments[]

Primary UI payload. Event searches render event carousels and ticket browsing renders ticket cards with actions and checkout links.

context[]

Compact assistant-ready guidance about what is on screen and what filters can be applied next.

_meta

Includes openai/outputTemplate so chat clients can mount the ticket widget automatically.

Embedded listing data

The text payload also embeds sections, prices, delivery methods, and checkout URLs, which is useful for fallback reasoning.

{
  "structuredContent": {
    "context": [
      "Your golden tickets await..."
    ],
    "custom_attachments": [
      {
        "type": "custom",
        "data": "{\"eventInfo\": {...}, \"tickets\": [...]}"
      }
    ]
  },
  "_meta": {
    "openai/outputTemplate": "ui://widget/sierra-attachment.html"
  }
}

Quickstart

For best results, resolve names first, search events second, and browse tickets third. That gives your product a cleaner sales funnel: better search precision up front, then richer ticket cards when the user is ready to buy.

  1. Use LookupSearchSuggestions when the user names a performer, team, venue, or event.
  2. Use LookupLocation when the user provides a city, ZIP code, or coordinates.
  3. Call SearchEvents with those resolved IDs or coordinates.
  4. Call BrowseTicketsForEvent with the chosen eventId and any ticket filters.
{
  "jsonrpc": "2.0",
  "id": "tickets-1",
  "method": "tools/call",
  "params": {
    "name": "BrowseTicketsForEvent",
    "arguments": {
      "eventId": 6641236,
      "quantityNeeded": 2,
      "section": "Section 6",
      "maxPrice": 60
    }
  }
}

Access

Access

This MCP is available through Infoseek. Reach out to get access enabled for your app or agent workflow.

Integration

We’ll help you wire the MCP into your chat product, agent workflow, or discovery UI once access is enabled.

Why these outputs matter

Event discovery agents

Turn vague entertainment intent into clickable event options and keep the user inside your product instead of sending them to search results pages.

Ticket comparison UX

Render carousels immediately from custom_attachments without building your own card layer, ticket parser, or event-to-listing handoff.

Structured checkout handoff

Preserve listing IDs, ticket metadata, and checkout URLs so your assistant can move from discovery to a purchase-ready handoff with less custom engineering.

Need an MCP? Contact us.