Ticket Hunter Agent

×

Ticket Hunter Agent

An autonomous AI agent that browses the web in real-time to find you the best available tickets — live.

What is this?

Ticket Hunter is a fully autonomous AI agent that takes a natural-language query like "Taylor Swift Eras Tour NYC" and — without any human intervention — searches Google, opens Ticketmaster, StubHub, SeatGeek, and other ticket platforms, navigates the pages, and returns ranked, structured ticket listings in real-time.

The agent streams its work live to the browser: you watch it browse, click, and extract data as it happens.

Built with Bright Data + Yutori N1

How it works

The agent runs as a 5-stage LangGraph pipeline, streamed live to your browser via Server-Sent Events:

User Query
    │
    ▼
┌───────────���─────────────────────────────────────────────┐
│  Stage 1 · SERP Search                                  │
│  Bright Data SERP API searches Google for ticket sites  │
│  Scores and selects the top 3 most relevant URLs        │
└────────────────────────┬────────────────────────────────┘
                         │
                         ▼
┌─────────────────────────────────────────────────────────┐
│  Stage 2 · Browser Pipeline                             │
│  Connects to Bright Data Browser API via CDP            │
│  Opens each URL with a real Chromium instance           │
│  Takes initial screenshot → streamed to UI live         │
└────────────────────────┬────────────────────────────────┘
                         │
                         ▼
┌─────────────────────────────────────────────────────────┐
│  Stage 3 · Yutori N1 Agentic Loop (up to 15 steps)     │
│  N1 vision model views screenshots and decides actions  │
│  Tools: navigate · click · scroll · type · screenshot   │
│  Iterates until tickets are found or step limit reached │
└────────────────────────┬────────────────────────────────┘
                         │
                         ▼
┌─────────────────────────────────────────────────────────┐
│  Stage 4 · Structured Extraction                        │
│  OpenRouter (Gemini Flash) extracts JSON from findings  │
│  Fields: event, date, venue, section, row, price, url   │
└────────────────────────┬────────────────────────────────┘
                         │
                         ▼
┌─────────────────────────────────────────────────────────┐
│  Stage 5 · Merge & Rank                                 │
│  Deduplicates results across platforms                  │
│  Sorts by price (lowest first) → returned to UI         │
└─────────────────────────────────────────────────────────┘

Tech Stack

Layer	Technology
Framework	Next.js 16 · React 19 · TypeScript 5
Styling	Tailwind CSS 4
Agent Orchestration	LangGraph
Browser Automation	Playwright Core + Chrome DevTools Protocol (CDP)
Web Infrastructure	Bright Data Browser API + SERP API
Vision LLM	Yutori N1 (multimodal, tool-use)
Extraction LLM	OpenRouter → Google Gemini Flash
Rate Limiting	Upstash Redis (per-IP, 1 search / 24h for the demo)
Deployment	Vercel via GitHub Actions

Supported Ticket Platforms

The agent autonomously detects and browses any of these platforms based on Google results:

Ticketmaster
StubHub
SeatGeek
Vivid Seats
AXS
TickPick
Gametime
Eventbrite
Viagogo
TicketNetwork
Tickets.com

Getting Started

Prerequisites

Node.js 18+
A Bright Data account with Browser API + SERP API enabled
A Yutori N1 API key
An OpenRouter API key
An Upstash Redis database (for rate limiting)

1. Clone the repo

git clone https://github.com/brightdata/ticket-hunter-agent.git
cd ticket-hunter-agent

2. Install dependencies

npm install

3. Configure environment variables

Create a .env.local file in the project root:

# Yutori N1 — vision LLM for autonomous browsing
YUTORI_API_KEY=your_yutori_api_key

# Bright Data — Browser API CDP WebSocket endpoint
# Found in your Bright Data dashboard under Browser API > Access Parameters
BRD_CDP_URL=wss://brd-customer-<id>-zone-<zone>:<password>@brd.superproxy.io:9222

# Bright Data — API key for SERP and Web Unlocker
BRIGHTDATA_API_KEY=your_brightdata_api_key
BRIGHTDATA_SERP_ZONE=serp                   # optional, defaults to "serp"
BRIGHTDATA_WEB_UNLOCKER_ZONE=unblocker      # optional, defaults to "unblocker"

# OpenRouter — structured JSON extraction via Gemini Flash
OPENROUTER_API_KEY=your_openrouter_api_key
OPENROUTER_MODEL=google/gemini-flash-1.5    # optional

# Upstash Redis — rate limiting (remove or leave blank to disable)
KV_REST_API_URL=https://your-instance.upstash.io
KV_REST_API_TOKEN=your_upstash_token

4. Run locally

npm run dev

Open http://localhost:3000 and search for any event.

Project Structure

src/
├── app/
│   ├── api/search/route.ts          # POST endpoint — SSE stream orchestrator
│   ├── page.tsx                     # Main UI page
│   └── layout.tsx                   # Root layout + global metadata
├── components/
│   ├── SearchForm.tsx               # Query input with example prompts
│   ├── BrowserView.tsx              # Live browser screenshot panels (1–3 platforms)
│   ├── StatusLog.tsx                # Real-time agent activity log
│   └── ResultCard.tsx               # Ticket card with price, venue, seats
├── hooks/
│   └── useTicketSearch.ts           # SSE consumer + client state management
└── lib/
    ├── agent/
    │   ├── graph.ts                 # LangGraph workflow definition
    │   ├── state.ts                 # Agent state schema
    │   ├── stream-events.ts         # SSE event emitters
    │   ├── runtime-session.ts       # Browser session lifecycle
    │   ├── browser-utils.ts         # Playwright helpers
    │   ├── tools.ts                 # N1 tool schemas (click, scroll, etc.)
    │   └── nodes/
    │       ├── serp-search.ts       # Stage 1: Google SERP via Bright Data
    │       ├── browser-open.ts      # Stage 2: CDP browser connection
    │       ├── browser-pipeline.ts  # Stage 2: per-URL browsing orchestration
    │       ├── n1-browse-core.ts    # Stage 3: N1 agentic loop (15-step max)
    │       ├── n1-browse.ts         # Stage 3: N1 LangGraph node wrapper
    │       ├── extract.ts           # Stage 4: structured JSON extraction
    │       └── merge-and-rank.ts    # Stage 5: dedup + price sort
    ├── bright-data.ts               # Bright Data SDK wrapper
    ├── n1-client.ts                 # Yutori N1 OpenAI-compatible client
    ├── openrouter-client.ts         # OpenRouter extraction client
    ├── rate-limit.ts                # Upstash Redis rate limiter
    └── types.ts                     # Shared TypeScript interfaces

Deployment

The repo includes a GitHub Actions workflow for automatic Vercel deployment.

Deploy to Vercel (one-click)

Then add all environment variables in your Vercel project settings.

Deploy via GitHub Actions

Fork the repo
Connect it to a Vercel project
Add these secrets to your GitHub repo:
- VERCEL_TOKEN
- VERCEL_ORG_ID
- VERCEL_PROJECT_ID
Add all .env.local variables to Vercel's environment settings
Push to main — the workflow deploys automatically

Manual CLI deploy

npm run build
npx vercel deploy --prod

Ticket Result Schema

Each result returned by the agent follows this structure:

interface TicketResult {
  eventName: string;    // "Taylor Swift | The Eras Tour"
  eventDate: string;    // "Friday, June 7, 2025"
  venue: string;        // "MetLife Stadium"
  city: string;         // "East Rutherford, NJ"
  ticketType: string;   // "Floor A · General Admission"
  section: string;      // "GA Floor"
  row: string;          // "N/A"
  seats: string;        // "2 available"
  quantity: number;     // 2
  price: string;        // "$380"
  currency: string;     // "USD"
  platform: string;     // "StubHub"
  url: string;          // Deep link to the listing
  notes: string;        // Any additional context
}

Real-Time Streaming

The agent communicates with the frontend via Server-Sent Events (SSE). Events emitted during a search:

Event	Payload	Description
`status`	`{ message, level }`	Agent log entry (INFO, ACTION, WARN, DONE, etc.)
`screenshot`	`{ data, source }`	Base64 browser screenshot streamed live
`inspect_url`	`{ url, source }`	Current URL the browser has navigated to
`result`	`{ tickets, finalAnswer }`	Final structured ticket results
`error`	`{ message }`	Agent error
`done`	—	Stream complete

Rate Limiting

The live demo enforces 1 search per IP per 24 hours via Upstash Redis.

When running locally with your own keys, this limit is not enforced unless you configure Upstash in your .env.local.

Powered by

Bright Data

Bright Data provides the web infrastructure that makes the agent possible:

Browser API — a real Chromium instance with residential proxy routing, anti-bot bypass, and JavaScript execution, connected via CDP
SERP API — reliable Google search results to discover the right ticket platform URLs

Yutori N1

Yutori N1 is the multimodal vision LLM at the core of the agent loop:

Receives browser screenshots as visual input
Decides which actions to take (click, scroll, navigate, type)
Extracts ticket information from what it sees
Runs up to 15 reasoning steps per URL

Name		Name	Last commit message	Last commit date
Latest commit History 26 Commits
.github/workflows		.github/workflows
public		public
src		src
.gitignore		.gitignore
README.md		README.md
eslint.config.mjs		eslint.config.mjs
next.config.ts		next.config.ts
package-lock.json		package-lock.json
package.json		package.json
postcss.config.mjs		postcss.config.mjs
tsconfig.json		tsconfig.json

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Ticket Hunter Agent

What is this?

How it works

Tech Stack

Supported Ticket Platforms

Getting Started

Prerequisites

1. Clone the repo

2. Install dependencies

3. Configure environment variables

4. Run locally

Project Structure

Deployment

Deploy to Vercel (one-click)

Deploy via GitHub Actions

Manual CLI deploy

Ticket Result Schema

Real-Time Streaming

Rate Limiting

Powered by

Bright Data

Yutori N1

License

About

Uh oh!

Releases

Packages

Uh oh!

Contributors

Uh oh!

Languages

Folders and files

Latest commit

History

Repository files navigation

Ticket Hunter Agent

What is this?

How it works

Tech Stack

Supported Ticket Platforms

Getting Started

Prerequisites

1. Clone the repo

2. Install dependencies

3. Configure environment variables

4. Run locally

Project Structure

Deployment

Deploy to Vercel (one-click)

Deploy via GitHub Actions

Manual CLI deploy

Ticket Result Schema

Real-Time Streaming

Rate Limiting

Powered by

Bright Data

Yutori N1

License

About

Resources

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Contributors

Uh oh!

Languages

Packages