Stream Io Api Stream API

Setup

Wiring the Stream API by hand means generating server-side JWTs, attaching your application api_key on every query, and setting the stream-auth-type header correctly yourself. Through Jentic you install once, import the Stream API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Stream puts the resource name in the URL path (/blocklists/{name}, /campaigns/{id}), so a rule can pin your agent to a single blocklist or campaign: it reads and updates that one and nothing else. You choose the operations it may call, so destructive ones like deleting a blocklist are not included unless you add them.

Credential isolation

Your Stream 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 'get app settings' or 'create a blocklist', and Jentic returns the matching Stream operation with its input schema so the agent calls the right endpoint without browsing the reference docs.