Cloudinary APIs for AI Agents
MediaImage ProcessingJentic-Generated SpecsBasic authAgent Ready
Cloudinary API Catalog
2 APIs across 1 product group. All share one credential.
Which Cloudinary API should I use?
| I want to... | Use | Why |
|---|---|---|
| Add new media, apply transformations, or tag and rename assets | Cloudinary Upload API | The Upload API creates and mutates assets: it uploads images, videos, and raw files, applies eager transformations, and handles tagging, renaming, and deletion. |
| List existing resources, organize folders, or monitor account usage | Cloudinary Admin API | The Admin API handles account-level administration: listing and inspecting resources by type, managing folder hierarchies, and reading storage, bandwidth, and transformation-credit usage. |
| Delete a media asset | Cloudinary Upload API | Both APIs can remove assets, but the Upload API destroy operation permanently deletes an asset and its CDN derivatives, while the Admin API delete works on listed resources by type and public ID. |
Install Jentic One Beta
Connect the Cloudinary APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloudinary 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%2Fcloudinary.com" | 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%2Fcloudinary.com" | 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: .
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Cloudinary by hand means configuring Basic auth with your API key and secret, computing upload signatures, and resolving the per-account api.cloudinary.com host for both the Upload and Admin APIs. Through Jentic you install once, add the Cloudinary APIs from the Jentic directory, store the key and secret once, and your agent calls either API.
Permission scoping
Both APIs work within one cloud fixed by the cloud name and address assets by parameters rather than one id pinned in the path, so you scope the agent to the operations it needs, such as uploading, tagging, listing resources, or reading usage. Destructive operations like destroy or resource delete are only in reach if your rules include them.
Credential isolation
FAQs
Specific to using Cloudinary APIs through Jentic.
What is the difference between the Cloudinary Upload API and Admin API?
The Upload API creates and mutates assets: it uploads images, videos, and raw files, applies transformations, and handles tagging, renaming, and deletion. The Admin API handles account-level administration: listing and inspecting resources, managing folder hierarchies, and monitoring usage. Use the Upload API to add and change content, and the Admin API to organize and audit what already exists.
Do the two Cloudinary APIs share one set of credentials?
Yes. Both APIs use HTTP Basic authentication with the same Cloudinary API Key and API Secret, scoped to a single cloud name. One credential pair covers uploading, transformation, resource administration, folder management, and usage monitoring, so an agent set up for one API can call the other without a separate login.
Can an agent both upload media and organize it into folders?
Yes. An agent can create and search folders with the Admin API and upload assets that target those folders through the Upload API. A typical flow creates a folder structure first, uploads and tags the media into it, then lists the folder to confirm placement, keeping ingest and organization aligned in one workflow.
Why does Jentic maintain these Cloudinary specs?
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.
