Sondar

Setup

Wiring Sondar by hand means passing its api_token query key on every call, pointing at the SwaggerHub-hosted base URL, and handling retries on its workflow endpoints yourself. Through Jentic you install once, import Sondar from the API Directory, store the API key once, and your agent calls it.

Permission scoping

Sondar exposes workflow operations that carry their target in the request body rather than a resource id in the URL path, so limit the agent to the operations it needs, such as importing a ticket or listing bundles. You choose which operations are in the allowed set, so anything you do not add stays out of reach.

Credential isolation

Your Sondar API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'import a ticket' or 'list bundles', and Jentic returns the matching Sondar operation with its input schema so the agent calls the right endpoint without browsing the reference docs.