Taggbox Widget API

Setup

Wiring the Taggbox Widget API by hand means appending your user_key to the query string on every request and paging through galleries, feeds, and posts yourself. Through Jentic you install once, import the Taggbox Widget API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Taggbox's read calls pass their gallery target as a query parameter rather than a path resource, so limit the agent to the operations it needs, such as listing galleries or feeds, rather than to any one gallery. Every operation the agent can run is one you chose to allow.

Credential isolation

Your Taggbox user 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 'get gallery information' or 'list social feeds', and Jentic returns the matching Taggbox operation with its input schema so the agent calls the right endpoint without browsing the reference docs.