Setup

Wiring Permutive by hand means setting the X-API-Key header or k query key, choosing between the api.permutive.app and api.permutive.com hosts, and threading cohort, import, and segment ids through your calls yourself. Through Jentic you install once, import the Permutive Audience API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Permutive puts the resource id in the URL path (/cohorts-api/v2/cohorts/{cohortId}, /audience-api/v1/imports/{importId}/segments/{segmentId}), so a rule can pin your agent to one cohort or import. You choose the operations it may call, so writing events or identifying users is included only if you add it and reads can stand alone.

Credential isolation

Your Permutive 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 cohort definition' or 'submit audience events', and Jentic returns the matching Permutive operation with its input schema so the agent calls the right endpoint without browsing the reference docs.