# The golf-tech stack behind agent-native tee-time booking > When an AI agent books a round on golfx402, a lot happens between "find me a tee time" and a paid, confirmed reservation. The stack: live inventory from courses on the TeeWire network, a booking that writes to the course's own tee sheet, demand-based pricing from Golf Signals, and the open standards (MCP + a tee-time API + x402) that carry the request. ## What actually happens when an agent books a tee time In one automated round-trip, an AI agent discovers the golfx402 MCP server, searches live tee-time inventory, requests a reservation, receives an `HTTP 402 Payment Required` response, settles it with a stablecoin, and gets back a confirmed booking reference. No forms, no card entry, no human checkout. The step-by-step flow is in [how it works](https://golfx402.com/how-it-works), and the request/response shapes are in the [developer path](https://golfx402.com/for-developers). That flow is the visible part. Underneath sits real golf infrastructure that decides whether a booking is genuine, instantly confirmable, and fairly priced. ## Where the tee times come from golfx402 does not invent inventory. Every tee time an agent can book is live availability from courses running on [the TeeWire network](https://teewire.com/), the U.S.-based golf course management platform that already runs those courses on one system. A booking made through golfx402 is not a scraped listing. The reservation writes straight to [the course's own live tee sheet](https://teewire.com/tee-sheet-software), the same sheet the pro shop sees, which is what lets an agent return a confirmed time and booking reference in the same round-trip. ## Why an agent books the course directly The rail is built on a simple stance: agents should book the course directly, not through a middle layer that skims the round. That is the thesis behind TeeWire's [commission-free, direct-booking](https://teewire.com/barter-free-online-tee-times-philosophy) philosophy, and it carries over to agent commerce. The course keeps its inventory, pricing, and golfer relationship; the agent pays the course's own rate over x402, not a marketplace markup. ## Why the price an agent is quoted moves Tee-time pricing is no longer three static buckets. On the same platform, [demand-based pricing](https://www.golfsignals.com/dynamic-pricing/) from Golf Signals turns real-time demand — hour, day, season, weather — into a suggested fee for each slot, so the price an agent sees reflects live demand for that exact time. Golf Signals reads the same [first-party, real-time](https://www.golfsignals.com/why-golf-signals/) tee-sheet data the booking writes to, with operator floors, ceilings, and member protections intact. ## The open standards that carry it | Standard | Role | |----------|------| | **MCP** | Discovery and interface. An open standard from Anthropic; any MCP-capable assistant finds golfx402 and loads its booking tools with no per-integration wiring. | | **Tee-time API** | A REST API that queries live inventory from the network and requests a reservation by course, date, players, and price. | | **x402** | An open payment protocol on HTTP 402. The agent settles in a stablecoin in the same request cycle, so a booking is paid and confirmed with no checkout page. | ## Who builds it golfx402 is built by the team behind TeeWire, part of [CourseLogix](https://www.course-logix.com/), a company building websites, booking, and software for golf courses since 2004. It is golf-operations people putting an agent-native rail on infrastructure that already runs real tee sheets, points of sale, and pricing. --- *Next: how it works — · Developer path — · FAQ — *