Try a browser agent for concert tickets, then stop before payment

A developer asked a browser agent to buy two general-admission Ticketmaster tickets, but captchas and a stubborn seat map kept it from finishing.

Done with Custom agent· Advanced

What they did
They used agent-browser on Ticketmaster for a class side project and gave it a simple goal: get two general-admission tickets into the cart. They noticed it handled tokens more cleanly than a Playwright MCP setup, but the site soon introduced captchas, modal windows, and an interactive seating chart. After that, the agent fell into repeated attempts, including reopening the same popup 11 times, while the person monitored the run and stepped in as needed.
How it went
Roughly 40 minutes later, the purchase still had not gone through. The cart reservation timed out twice, and they finished with no tickets. They said the manual route still performs better on this site.
Tips
Ticket sites can be difficult for browser agents when they rely on captchas, shifting seat maps, and short-lived cart holds. If the flow starts repeating, have the agent pause and report back before any payment step.

Try it yourself with Claude in Chrome

Please help me secure [number] general-admission tickets for [event] at [venue] on [date] through [ticket site], with a limit of [price] per ticket. Open the listing, move the tickets into the cart, and then pause so I can review the cart, total, and fees myself. If you run into a captcha, a queue, a seat map, or a popup that keeps returning, stop and tell me exactly what is blocking you. Do not place the order or submit payment until I give you explicit approval.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on reddit.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.