Sydnee App Sydnee API

Setup

Wiring the Sydnee API by hand means learning its bearer token scheme, pointing at the public-api.sydnee.app host, and writing the request and error handling for its account and user operations yourself. Through Jentic you install once, import Sydnee from the API Directory, store the bearer token once, and your agent calls it.

Permission scoping

Sydnee puts the account id in the URL path (/accounts/{accountId}), so a rule can pin your agent to one account: it can read that account and manage its users and nothing else. You choose the operations it may call, so destructive ones like deleting an account or removing a user are not included unless you add them.

Credential isolation

Your Sydnee bearer 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 'create an account' or 'add a user to an account', and Jentic returns the matching Sydnee operation with its input schema so the agent calls the right endpoint without browsing the reference docs.