Semantictouch BentoSandbox API

Setup

Wiring BentoSandbox API by hand means implementing its OAuth2 password flow against login.bento-sandbox.com, refreshing tokens for the queue.bento-sandbox.com host, and handling requests and retries yourself. Through Jentic you install once, import BentoSandbox API from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

BentoSandbox API puts the template id in the URL path (/category-attribute-template/{template_id}), so a rule can pin your agent to one template: it can read that template and nothing else. You choose the operations it may call, so writes like updating or deleting a template are not included unless you add them.

Credential isolation

Your BentoSandbox API credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list category attribute templates' or 'create a new template', and Jentic returns the matching BentoSandbox API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.