Videnly API

Setup

Wiring the Videnly API by hand means formatting its apiKey as a Bearer value in the Authorization header and polling its render queue for progress yourself. Through Jentic you install once, import the Videnly API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Videnly puts the queue id in the URL path (/v1/queue/progress/{queueId}), so a rule can pin the agent to reading progress for a given job. You choose the operations it may call, so a state-changing one like clearing the queue is not included unless you add it.

Credential isolation

Your Videnly 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 'list my rendered videos' or 'check render queue progress', and Jentic returns the matching Videnly operation with its input schema so the agent calls the right endpoint without browsing the reference docs.