Try an agent-style search
Enter a request in everyday language. The demo shows every selected tool, its generated arguments and live results returned by the API.
The hosted demo uses a restricted trial credential. Its results come from the shared global-trial-v2 catalogue, and the interface identifies that catalogue explicitly. An empty result may therefore mean that no matching club exists in the sample, not that none exists in the full dataset.
Waiting for requestRun 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 proves
The interface separates the agent workflow into visible steps:
- Interpret the request.
- Select a supported API tool.
- Generate structured arguments.
- Execute the authenticated request server-side.
- Present only grounded results.
The demonstration uses tool calling. The model can select any tool in the gateway's approved copy of the published tool catalogue. A request such as info about Green Eagle can first search by club name and then retrieve the matching club by slug, so both calls remain visible.
The catalogue is a persistent local snapshot loaded when the gateway starts. It is never downloaded during a visitor request. An operator must explicitly run the catalogue sync command and restart the gateway before newly published tools become available. Every selected tool and argument is validated against the approved API contract before execution. No phrase-specific parser rewrites the model's interpretation.
The gateway also applies a persistent monthly model-request quota. When that quota is exhausted, the demo returns a clear demo_monthly_quota_reached message without making another model request.