Call it from any backend
Call golfx402 directly from any backend. Endpoints for availability, holds, bookings, and cancellations. x402 returns a 402 with payment terms your agent settles automatically.
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.
Integrate
Two ways to integrate
Point any assistant at it
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 protocol
The x402 request, illustrated
A booking request, a 402 with payment terms, and a paid retry — one clean round-trip.
→ 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: <signed x402 payload>)
← 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
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.
- Per-booking via x402
- Metered plans for volume
- No invoicing
- No stored cards
What you get at launch
- REST endpoints: availability, hold, book, cancel
- MCP server with the same tools
- x402 payment terms on every booking
- Live tee-time inventory
- 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.