Skip to main content

Try an agent-style search

Enter a golf request in everyday language. The demo shows which tools the agent selects, the arguments it generates, and the live results returned by the API.

The hosted demo uses restricted trial access, so some clubs or data may not be available. An empty result does not necessarily mean that no matching club exists in the full dataset.

Selected toolWaiting for request
Generated arguments
Run the demo to generate arguments.

Run a request to see the tool call and grounded API results.

The request is translated into a published Golfclubs tool call. The gateway validates and executes it with restricted server-side credentials. No API key is sent to the browser.

What the demo shows​

The agent workflow remains visible from request to result:

  1. Interpret the natural-language request.
  2. Select one or more supported tools.
  3. Generate structured arguments.
  4. Validate the tool calls against the API contract.
  5. Execute authenticated requests.
  6. Return results grounded in the API response.

The model is not limited to a predefined search flow. It can select from the tools exposed by the gateway and chain them when necessary.

For example, a request such as info about Green Eagle can first search for the club by name, take the matching result's UUID, and retrieve details with get_golf_club({ identifier: UUID }). Both tool calls and their arguments remain visible in the demo.

Tool catalogue​

The gateway uses an approved copy of the published tool catalogue. Every selected tool and its arguments are validated against that contract before execution.

The catalogue is loaded when the gateway starts rather than fetched during individual visitor requests. Newly published tools become available after the catalogue is synchronized and the gateway is restarted.

There is no phrase-specific parser translating requests into API calls. Tool selection and argument generation are performed by the model using the available tool definitions.

Demo limits​

The public demo is intentionally restricted and is not a substitute for authenticated API access.

It also has a monthly model-request quota. If that quota is exhausted, the demo returns demo_monthly_quota_reached without issuing another model request.