MCP
The Model Context Protocol, an open standard from Anthropic, is how any MCP-capable assistant finds golfx402 and loads its booking tools with no per-integration wiring.
Deep dive
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. Here is the full stack: the network the inventory comes from, the open standards that carry the request, and why the price the agent is quoted is what it is.
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. We walk that flow step by step in how it works, and the request and response shapes live in the developer path.
That flow is the visible part. Underneath it sits a stack of real golf infrastructure that decides whether a booking is genuine, instantly confirmable, and fairly priced. This piece is about that stack.
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, the U.S.-based golf course management platform that already runs those courses' operations on one system.
That distinction matters. A booking made through golfx402 is not a scraped listing or a cached guess: the reservation writes straight to the course's own live tee sheet, the same sheet the pro shop is looking at. That is what lets an agent hand the golfer a confirmed time and a booking reference in the same round-trip, instead of a "request sent, awaiting confirmation" limbo.
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 same thesis behind TeeWire's commission-free, direct-booking philosophy, and it carries over cleanly to agent commerce.
When an AI assistant books on golfx402, the course keeps its inventory, its pricing, and its relationship with the golfer. The agent pays the course's own rate settled over x402, not a marketplace markup, and the course is not trading tee times away for exposure. A rail that respects who owns the tee sheet is a rail courses will actually connect to, which is what makes the inventory deep enough for agents to rely on.
Why the price an agent is quoted moves
Tee-time pricing is no longer three static buckets of prime, mid, and twilight. On the same platform, demand-based pricing from Golf Signals turns real-time demand — hour, day, season, even weather — into a suggested fee for each individual slot. So when an agent asks for a Saturday 7:40, the price it sees back reflects live demand for that exact time, not a fixed rate card.
Golf Signals reads the same first-party tee-sheet data an agent booking writes to, which is why the numbers stay first-party and real-time rather than synced from a third party once a day. For automated bookings that also means reliability can be priced in: the operator keeps floors, ceilings, and member protections, and the agent simply books at whatever the course has decided a given tee time is worth right now.
The open standards that carry it
Three open standards do the machine-to-machine work between the assistant and the tee sheet.
Tee-time API
A REST tee-time API queries live inventory from the network and requests a reservation on the golfer's behalf, 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 without a checkout page.
Who builds it
golfx402 is built by the team behind TeeWire, part of CourseLogix, a company that has built websites, booking, and software for golf courses since 2004. It is not a crypto project bolting onto golf: it is golf-operations people putting an agent-native booking rail on top of infrastructure that already runs real tee sheets, points of sale, and pricing every day.
That is the whole stack. The x402 and MCP layer is what agents talk to; the golf platform underneath is what makes the answer real: live inventory, a direct booking that lands on the course's own tee sheet, and a price that reflects what the tee time is actually worth.
Build on the golf agent rail.
Whether you are building an AI golf assistant or you run a course and want your tee sheet payable by agents, get on the list for early API access.