Visibot App Visibot API

Setup

Wiring the Visibot API by hand means passing its bearer token in the Authorization header and driving its video create, edit, and retrieval calls yourself. Through Jentic you install once, import the Visibot API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Visibot carries its video targets in the request body rather than the URL path, so scope the agent to the operations it needs, such as creating or retrieving a video. You choose that set, so a state-changing operation like editing a video is not included unless you add it.

Credential isolation

Your Visibot 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 a video' or 'check my usage', and Jentic returns the matching Visibot operation with its input schema so the agent calls the right endpoint without browsing the reference docs.