Yeti-Switch API

Setup

Wiring Yeti-Switch by hand means sending its admin bearer token against your own server_url host, accepting that the token carries full administrator access, and handling retries yourself. Through Jentic you install once, import Yeti-Switch from the API Directory, store the token once, and your agent calls it.

Permission scoping

Yeti-Switch puts the account id in the URL path (/accounts/{id}), so a rule can pin your agent to one account: it can read and update that account and nothing else. You choose the operations it may call, so destructive ones like deleting an account or correcting a balance are not included unless you add them.

Credential isolation

Your Yeti-Switch token 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 'set an account balance' or 'create an account', and Jentic returns the matching Yeti-Switch operation with its input schema so the agent calls the right endpoint without browsing the reference docs.