Connect an agent to golf data

The API supports two agent integration paths: a native MCP endpoint and the AI Toolkit REST endpoints. Both expose normalized golf data and domain rules without executing an AI model on your behalf.

1. Start a trial

Choose the data level the finished integration needs:

Trial	Data	Catalogue	Limits
Fairway	Core	Shared global-trial-v2 sample	15/minute, 250/day
Tour	Extended	Shared global-trial-v2 sample	15/minute, 250/day

Both trials last 14 days. Access stops after expiration unless the selected plan is activated.

Every trial key sees the same 500 clubs. Check /v1/trial/coverage before choosing example places, and treat meta.notice.code: trial_sample_no_match as a sample limitation rather than proof that the full catalogue has no match.

2. Choose the integration

MCP

For an MCP-compatible client, connect to:

https://api.eae.golf/mcp

Authenticate with the same Bearer API key used by the REST API. The MCP server exposes tool and prompt discovery directly through the protocol.

See MCP for the endpoint, available tools, prompts and raw verification requests.

AI Toolkit

If your application manages the model tool-calling loop itself, load the tool definitions:

curl 'https://api.eae.golf/v1/ai/tools' \
  --header 'Authorization: Bearer YOUR_API_KEY'

Pass the returned function definitions to the model using its tool-calling interface.

3. Let the agent choose a tool

A user might ask:

Find public golf clubs near Hamburg under €80.

The model can select search_golf_clubs and generate supported arguments:

{
  "near": "Hamburg",
  "country": "DE",
  "radius_km": 50,
  "maximum_green_fee": 80,
  "public": true,
  "limit": 10
}

For an AI Toolkit integration, your server executes the corresponding authenticated API request and returns the result to the model. With MCP, the client invokes the discovered tool through the MCP endpoint.

near is resolved to coordinates by the API. Agents do not need their own geocoder. town is reserved for exact club-address filtering.

4. Ground the answer

Apply these rules to every generated response:

Use only the supplied golf data.
Treat null as unknown.
Do not infer that a permission, restriction or facility is absent when its value is null.
False means the source explicitly indicates that the condition is not allowed or not available.
Identify important unknown information explicitly.

5. Keep credentials server-side

Never embed a production API key in frontend JavaScript or send it to the model provider. Execute API calls on your server and give the model only the context required for the current task.

Next, configure MCP, try the interactive demo, or inspect the AI Toolkit.