Accounts 20 InsiderCX ARC API

Setup

Wiring the InsiderCX ARC API by hand means logging in through /users/login, sending its user-token header on every call to apis.insidercx.com, and managing single and bulk ARC object writes yourself. Through Jentic you install once, import the InsiderCX ARC API from the API Directory, store the user-token once, and your agent calls it.

Permission scoping

The ARC API puts the object id in the URL path (/data/ARC/{objectId}), so a rule can pin your agent to one ARC object for read and update. You choose the operations it may call, so destructive ones like deleting an object or running bulk writes are not included unless you add them.

Credential isolation

Your InsiderCX ARC user-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 ARC object' or 'look up an ARC record by id', and Jentic returns the matching InsiderCX ARC operation with its input schema so the agent calls the right endpoint without browsing the reference docs.