E.A.E GolfNative MCP endpoint
Connect MCP-compatible clients directly to golf search, club retrieval and compact context tools.
Native MCP for golf data
Give your agent access to
Connect MCP-compatible agents, AI assistants, applications and search experiences directly to normalized golf data through MCP or the REST API.
Native MCP endpointModel-independentProduction-ready
MCP SERVERLIVE
API HOST: https://api.eae.golf
POST
/mcp{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "search_golf_clubs",
"arguments": {
"near": "Hamburg",
"maximum_green_fee": 80,
"public": true
}
}
}Compact AI context
Send relevant access, price and course facts without wasting tokens on unnecessary fields.
Unknown stays unknown
Clear null semantics prevent agents from turning missing information into false claims.
Model-independent
Use the same normalized data through MCP, REST, OpenAI, Claude, Gemini or your own agent stack.
Built for useful answers
From natural language to reliable golf results
Growth
Customer acquisition for golf businesses
Identify relevant clubs, segment potential partners and build targeted acquisition workflows using structured location, facility and contact data.
Lead discoverySegmentationPartnerships
Travel
Golf destination experiences
Build curated golf journeys around destinations, combining nearby courses, access requirements, green fees and available facilities.
Golf tourismTravel planningDestinations
Discovery
Club finders and golf maps
Help golfers discover suitable clubs around their location or travel destination using geographic and access filters.
Radius searchAccess filtersMap results
Events
Tournament and event platforms
Help organizers discover suitable venues and compare courses, facilities, access conditions and geographic coverage for golf events.
TournamentsVenue selectionCorporate golf
Applications
Golf apps and member services
Enrich mobile and web products with normalized club information without maintaining a separate data pipeline.
Mobile appsWeb productsProfiles
Intelligence
Market and portfolio insights
Build internal tools, regional comparisons and data products on top of one consistent golf-course model.
CoverageComparisonAnalytics
Agent quickstart
From API key to MCP tool call
Step 1
Choose a trial
Try Fairway core data or Tour extended data for 14 days.
Step 2
Connect to MCP
Point your MCP client at /mcp and authenticate with the same Bearer API key.
Step 3
Let the agent search
The client discovers tools through MCP and calls them using normalized golf facts and the same access rules as REST.
Questions before you build
Frequently asked questions
Does the API run an AI model for me?
No. The platform exposes a native MCP endpoint plus the AI Toolkit and REST API. You bring the model or MCP-compatible client, while the platform provides normalized golf data, tools, prompts, compact context and schemas.
Is the platform MCP compatible?
Yes. MCP-compatible clients can connect directly to /mcp using the same Bearer API key, plan, trial catalogue, data-access policy and rate limits as the REST API.
What is the difference between Fairway and Tour?
Fairway provides the core dataset for search and common club experiences. Tour adds extended course, scorecard, detailed fee and commercial data.
Can I trial either plan?
Yes. Both plans can be evaluated for 14 days with a deterministic 500-club sample and limits of 15 requests per minute and 250 requests per day.
What happens when information is missing?
Missing information is returned as null and must be treated as unknown. The AI Toolkit includes this rule so agents do not present missing facts as false.
Is the API only for AI agents?
No. The REST API also supports websites, mobile apps, internal tools and conventional search interfaces.
Can an API key be placed in browser code?
No. Production keys should remain on your server. Browser applications should call a protected backend or proxy.