What is in place
Each claim links to the place an agent can check it.
| Discovery | llms.txt, an RFC 9727 API catalog, an agent skills index and an MCP server card. Pages link to the API catalog, OpenAPI description and llms.txt. llms.txt · api-catalog · skills |
|---|---|
| MCP server | Streamable HTTP. Public course search and scorecards need no account. Distance to the flag and caddie advice need GolfCore OAuth and Premium. A signed-in golfer can request a Stripe checkout link for a chosen Premium plan. server card · OAuth metadata |
| REST API | Keyless, CORS-open JSON with an OpenAPI 3.1 description. Search by name, place, coordinates or mapping coverage; read a full scorecard by slug. OpenAPI · status |
| Hand-off to the person | Every course the API or MCP server returns carries app_url, which opens that course's map, on a hole if asked. A signed-out person starts as a guest. On a phone with GolfCore installed, the same link opens the native iOS or Android app. skill |
| Browser agents in the app | In a browser with WebMCP, golfcore.app registers tools to find courses, open one, read the hole on screen with the player's distance to the pin, and change holes. Without it, the controls are labelled buttons and the hole selector names the hole and par. app auth.md |
| Pages an agent can read | Every course page on this site is static HTML: the card in tables, every figure in text, and GolfCourse structured data. Course pages on golfcore.app link to both by Link header and in noscript. course directory |
| Access | Public course data needs no key or sign-up. Fair-use rate protection may return 429 during sustained excessive traffic. Browser agents can start a guest session for the course map; personal caddie and distance tools require GolfCore sign-in and Premium. auth.md · robots.txt |
What an agent can do for a golfer
| Which courses near me have green contour maps? | MCP search with near and coverage "contours", or https://api.golfcore.org/v1/courses?near=lat,lng&coverage=contours |
|---|---|
| What's the par and yardage on every hole at Pebble Beach from the blue tees? | MCP search with scope ["slug","scorecards"], or https://api.golfcore.org/v1/courses/pebble-beach |
| Show me the 7th green at Pebble Beach. | Give the person the course's app_url with &hole=7, or call open_course in the app |
| How far am I from the pin? | MCP distance_to_flag with GolfCore OAuth and Premium, or get_current_hole in the app once the player has shared their location |
Connect
{
"mcpServers": {
"golfcore": { "url": "https://mcp.golfcore.org/mcp" }
}
}The full reference, with every parameter, is on the developers page.
For personal agents that use a browser
Open a course result's app_url for the golfer and read scorecard facts from the public API. The web app can start a guest session for the map. A guest cannot use personalized distance or caddie tools. Those tools require the golfer to sign in to GolfCore and have Premium. When the golfer chooses a Premium plan, the subscribe_premium MCP tool creates a Stripe checkout link; show the current price and renewal terms and let the golfer complete payment on Stripe. A checkout link is not a completed purchase.
Where the line is
Agents can read public course data and move the map. The MCP server can also return a distance to the flag, AI caddie advice, and a Stripe checkout link after GolfCore sign-in. Distance and caddie advice require Premium. The checkout tool does not charge the golfer; they review and pay on Stripe. Agents cannot book tee times, write scores, send messages or access club rosters through these tools. The satellite map, yardage and scoring are free. Green contours, illustrated maps, modeled wind and offline downloads require Premium after any complimentary preview.