wealthAPI

Setup

Wiring wealthAPI by hand means learning its bearer token alongside the mandator client id and secret headers, pointing at the sandbox host, and handling responses yourself. Through Jentic you install once, import wealthAPI from the API Directory, store those credentials once, and your agent calls it.

Permission scoping

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

Credential isolation

Your wealthAPI token and mandator client 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 accounts' or 'get transactions', and Jentic returns the matching wealthAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.