# golfx402 for developers > Ship golf tee-time booking to your agent. A REST tee-time API and an MCP server, with **x402 pay-per-booking** built in. Search real inventory, reserve, and settle payment — no human checkout. ## Two ways to integrate - **REST API.** Call golfx402 directly from any backend. Endpoints for availability, holds, bookings, and cancellations. x402 returns a 402 with payment terms your agent settles automatically. - **MCP server.** Point any MCP-capable assistant (Claude, agent frameworks, custom bots) at the golfx402 MCP server and it gets booking tools instantly — no per-integration wiring. ## The x402 request, illustrated ```http → POST /v1/bookings { "course": "pebble-dunes", "date": "2026-08-02", "time": "07:40", "players": 4 } ← HTTP/1.1 402 Payment Required { "accepts": [{ "scheme": "x402", "asset": "USDC", "amount": "220.00", "network": "base" }], "resource": "/v1/bookings", "expires": "2026-08-02T00:05:00Z" } → POST /v1/bookings (X-PAYMENT: ) ← HTTP/1.1 200 OK { "status": "confirmed", "booking_ref": "GX402-9F3A", "course": "pebble-dunes", "time": "07:40" } ``` *Illustrative shape only — final field names are published in the API reference at launch.* ## Pricing model golfx402 is designed for usage-based monetization: a per-booking fee settled through x402, or a metered plan for higher-volume partners. Because payment is native to the protocol, there's no invoicing or card-on-file to manage — the agent pays as it books. ## What you get at launch - REST endpoints: availability, hold, book, cancel - MCP server with the same tools - x402 payment terms on every booking - Live inventory via the TeeWire network - Booking references for confirmations ## Request early API access We're onboarding a first wave of AI app and agent developers. Tell us what you're building and we'll send API keys and the MCP endpoint. Email **hello@golfx402.com** (subject: "golfx402 early API access"). --- *How it works — · For courses — *