Shotstack APIs for AI Agents
MediaVideo ProcessingImage ProcessingMixed ProvenanceAPI keyAgent Ready
For Agents
APIs2 in catalogue
Endpoints25 indexed
AuthAPI key — 1 credential for all 2 APIs
ProvenanceMixed provenance
An agent can submit a JSON edit to render a video or image, poll for render status, render from a saved template, and then fetch or delete the produced asset by render id. It works across Shotstack's rendering, template, and asset endpoints from a single API key.
Shotstack describes an entire video, image, or audio edit as JSON and renders it in the cloud, so agents produce media programmatically without local editing software or timeline tooling. Reusable templates let an agent generate many variations of the same design by swapping data rather than rebuilding each edit.
Shotstack API Catalog
2 APIs across 1 product group. All share one credential.
Which Shotstack API should I use?
| I want to... | Use |
|---|---|
| Queue a render, manage templates, and control the full edit lifecycle | Shotstack API |
| Retrieve or delete a rendered asset by render id | Shotstack |
Install Jentic One Beta
Connect the Shotstack APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Shotstack APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fshotstack.io" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fshotstack.io" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “render a video from JSON and fetch the finished asset”.
What AI Agents Can Do with Shotstack
Each workflow spans multiple Shotstack APIs. Jentic routes each operation to the right API automatically.
Render a video then fetch the finished asset
An agent submits a JSON edit to queue a render on the main Shotstack API, polls render status until it completes, then retrieves the produced asset by its render id from the assets API. This spans the render and asset-retrieval halves of the portfolio in one flow.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Shotstack by hand means sending your API key on every request against the versioned api.shotstack.io host and polling render status yourself across both APIs. With Jentic you install Jentic One once, add the Shotstack APIs from the Jentic directory, and store the key a single time for your agent to use.
Permission scoping
Shotstack puts render, template, and asset ids in the URL path, so your own rules in Jentic One can pin an agent to specific operations. You decide which calls it may make, so destructive ones like template or asset deletion are excluded unless you add them.
Credential isolation
Your Shotstack API key is stored encrypted by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context, and one key covers both APIs.
Intent-based discovery
An agent searches the Jentic directory by intent, such as 'render a video from JSON' or 'get rendered asset by render id', and Jentic returns the matching Shotstack operation with its input schema so the agent calls the right endpoint without reading the reference docs.
FAQs
Specific to using Shotstack APIs through Jentic.
What can an agent do across the Shotstack APIs?
An agent can submit JSON edits to render videos, images, and audio, poll for render status, create and render reusable templates, and retrieve or delete the resulting assets. The two APIs together cover the full path from defining an edit to serving the finished file.
Do the two Shotstack APIs share the same credential?
Yes. Both APIs use the same Shotstack API key sent in the x-api-key header, so a single credential authorizes rendering, template, and asset operations. You do not need separate keys for each API.
When should I use one API over the other?
Use the main Shotstack API for queuing renders, managing templates, and controlling the full edit lifecycle across its 20 endpoints. Use the assets-focused API when you mainly need to fetch render status or serve and delete a finished asset by its render id.
How does an agent move data between the two APIs?
The render id ties them together. An agent submits an edit and receives a render id from the rendering endpoints, then passes that same id to the asset endpoints to fetch or remove the produced file once the render completes.
Does Shotstack handle anything beyond media rendering?
No. Shotstack is scoped to video, image, and audio rendering, template management, and asset serving. It does not cover payments, messaging, or crm, so pair it with other APIs for those parts of a workflow.
Are renders synchronous or does the agent poll?
Renders are queued and processed asynchronously. An agent submits an edit, receives a render id, and polls the render status endpoint until the job reports completion, at which point the asset location is available.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.