VBOUT API

Setup

Wiring the VBOUT API by hand means appending its api_key query parameter to every call against api.vbout.com and coding each social media channel, calendar, and post operation yourself. Through Jentic you install once, import the VBOUT API from the API Directory, store the key once, and your agent calls it.

Permission scoping

VBOUT social media operations carry the post and channel targets in the request body and query, so limit the agent to the operations it needs, such as listing channels or adding a post. You choose that allowed set, so writes like deleting a post are excluded unless you add them.

Credential isolation

Your VBOUT 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 'schedule a social media post' or 'get social channel stats', and Jentic returns the matching VBOUT operation with its input schema so the agent calls the right endpoint without browsing the reference docs.