Teampass API

Setup

Wiring the Teampass API by hand means calling its auth endpoint for an API key, pointing every request at your own self-hosted host, and writing the folder and item paging and retry glue yourself. Through Jentic you install once, import the Teampass API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

The Teampass API puts the item id in the URL path (/api/index.php/item/{itemId}), so a rule can pin your agent to one item: it can read and update that item and nothing else. You choose the operations it may call, so destructive ones like deleting an item are not included unless you add them.

Credential isolation

Your Teampass 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 'read a stored item' or 'list folders', and Jentic returns the matching Teampass API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.