<!--
title: How golfx402 works — x402 + MCP tee-time booking
canonical: https://golfx402.com/how-it-works
description: How golfx402 works — AI agents discover the MCP server, search live TeeWire tee-time inventory, and pay automatically via the x402 (HTTP 402) protocol.
-->

# How golfx402 works

> golfx402 combines three open standards: **MCP** for discovery, a **tee-time API** for inventory, and **x402** for payment. Together they turn "find me a tee time" into a completed, paid reservation with no human checkout.

## The agent booking flow, step by step

1. **Discover the MCP server.** An AI assistant that speaks the Model Context Protocol (MCP) finds golfx402 in the MCP registry and loads its tools — `search_tee_times`, `hold`, `book`, `cancel`. This makes golfx402 usable by any MCP-capable assistant without custom glue code.
2. **Search live inventory.** The agent queries the golfx402 tee-time API for real availability across the TeeWire network — filtering by course, date, number of players, and price.
3. **Request a booking.** The agent requests a reservation on the golfer's behalf. golfx402 responds with **HTTP 402 Payment Required**, describing the amount due and the accepted stablecoin — the machine-readable equivalent of a checkout page.
4. **Pay via x402.** The agent settles with a stablecoin wallet using the x402 protocol and automatically retries the request with proof of payment. No card entry, no redirect, no human.
5. **Receive confirmation.** golfx402 confirms the tee time and returns a booking reference the assistant can show the golfer. Done in one automated round-trip.

## Why x402 and MCP together?

**MCP** solves discovery and interface — it's how an AI assistant knows golfx402 exists and how to call it. **x402** solves settlement — it's how the agent pays for a booking in the same HTTP round-trip, with no human. Neither alone is enough for autonomous commerce; together they turn "find me a tee time" into a completed, paid reservation. This is the same pattern the broader agentic-commerce ecosystem is converging on, now that Cloudflare and AWS support x402 payments at the edge.

| Standard | Role |
|----------|------|
| **MCP** | Discovery & interface. An open standard from Anthropic. Any MCP-capable assistant can find golfx402 and call its booking tools with no per-integration wiring. |
| **x402** | Payment & settlement. An open protocol on HTTP 402. The agent pays in stablecoins in the same request cycle — no invoicing, no stored card, no checkout page. |

---
*Next: developer integration — <https://golfx402.com/for-developers> · Full FAQ — <https://golfx402.com/faq>*
