Cloudinary Admin API
Browse all Cloudinary APIs41
AI ReadinessFoundational (D-)41/100
Agent-ready OpenAPI document · curated by JenticMediaImage Processingbasic11 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Administer Cloudinary media assets, folders, and account configuration. List resources by type, organize folder structures, and monitor storage and bandwidth usage quotas.
Use for: I need to list all images uploaded to my Cloudinary account, I want to check my current storage and bandwidth usage, Get details about a specific uploaded resource by its public ID, Create a new folder to organize marketing assets
Not supported: Does not handle media upload, image transformations, or video transcoding - use for administrative resource listing, folder management, and usage monitoring only.
Jentic publishes the only available OpenAPI specification for Cloudinary Admin API, keeping it validated and agent-ready. Control media assets, folders, and product environment configuration through 11 administrative endpoints. List and inspect uploaded resources by type, organize assets into folder hierarchies, search folders by expression, and monitor account usage quotas including storage, bandwidth, and transformation credits.
Install Jentic One Beta
Connect the Cloudinary Admin API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloudinary Admin API, 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%2Fcloudinary-admin-api" | 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%2Fcloudinary-admin-api" | 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.
Capabilities
What an agent can do with Cloudinary Admin API.
List uploaded media resources filtered by type (image, video, raw) with pagination and ordering
Inspect individual resource metadata including format, dimensions, tags, and transformation history
Organize assets into nested folder hierarchies with create, rename, and delete operations
Search folders by expression to locate specific organizational structures
Monitor account usage including storage consumed, bandwidth used, and transformation credits remaining
Retrieve and update product environment configuration settings
Use Cases
Patterns agents use Cloudinary Admin API for, with concrete tasks.
★ AI Agent Media Asset Auditing
AI agents audit media asset libraries stored in Cloudinary through Jentic. The agent searches for the operation by intent (e.g., 'list all images in Cloudinary'), receives the schema, and executes resource listing calls to identify unused, oversized, or untagged assets. Usage monitoring endpoints track whether the account is approaching storage or bandwidth limits before costs escalate.
List all image resources using GET /resources/image, then check account usage with GET /usage to verify storage is below 80% of the quota
Media Folder Organization
Organize thousands of media assets into logical folder structures for teams and projects. Create nested folders, move assets between them, and search the folder tree by expression. The Admin API handles folder-level operations while individual asset uploads target specific folders via the Upload API. Folder search supports finding structures by partial name or path.
Create a new folder 'campaigns/2026-q2' using POST /folders/campaigns/2026-q2 and verify it exists with GET /folders
Account Usage Monitoring and Alerts
Track real-time account consumption across storage, bandwidth, and transformation credits. The /usage endpoint returns current period metrics against plan limits, enabling automated alerts before overages trigger additional charges. Monitor derived resources, video processing minutes, and API call counts to forecast upcoming billing.
Retrieve current usage metrics from GET /usage and calculate the percentage of bandwidth quota consumed this billing period
Resource Metadata Inspection
Retrieve detailed metadata for uploaded assets including format, dimensions, file size, creation date, tags, and applied transformations. Use this for quality assurance workflows that verify uploaded media meets size, format, or dimension requirements before publishing to production. Individual resource inspection provides full provenance and transformation history.
Get full metadata for resource 'hero-banner' of type image using GET /resources/image/hero-banner and verify dimensions exceed 1920x1080
Key Endpoints
11 endpoints — jentic publishes the only available openapi specification for cloudinary admin api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/resources/{resource_type}
List all resources of a given type (image, video, raw)
GET
/resources/{resource_type}/{public_id}
Get detailed metadata for a specific resource
DELETE
/resources/{resource_type}/{public_id}
Delete a specific resource by type and public ID
GET
/folders
List all root-level folders
POST
/folders/{folder}
Create a new folder at the specified path
GET
/folders/search
Search for folders by expression
GET
/usage
Get account usage statistics and quota consumption
GET
/config
Retrieve product environment configuration
GET
/resources/{resource_type}
List all resources of a given type (image, video, raw)
GET
/resources/{resource_type}/{public_id}
Get detailed metadata for a specific resource
DELETE
/resources/{resource_type}/{public_id}
Delete a specific resource by type and public ID
GET
/folders
List all root-level folders
POST
/folders/{folder}
Create a new folder at the specified path
GET
/folders/search
Search for folders by expression
GET
/usage
Get account usage statistics and quota consumption
GET
/config
Retrieve product environment configuration
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
Cloudinary Admin API
- Foundational (D-)41/100
87
Foundational Compliance63
Developer Experience & Jentic Compatibility50
AI-Readiness & Agent Experience94
Agent Usability10
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
87
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
50%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
50
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
39%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
61%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
10
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
10%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Cloudinary Admin API by hand means setting up basic auth with your API key and secret and resolving the per-account api.cloudinary.com/v1_1/{cloud_name} host yourself. Through Jentic you install once, import the Cloudinary Admin API from the API Directory, store the key and secret once, and your agent calls it.
Permission scoping
The Admin API works within one cloud fixed by the {cloud_name} host and reaches assets by parameters rather than one id pinned in the URL path, so scope the agent by the operations it needs, such as listing resources, reading folders, or checking usage. You choose that set, so a destructive operation like deleting a resource is only in reach if you include it.
Credential isolation
Your Cloudinary API key and secret are stored once, encrypted, by your own Jentic One instance and injected as the basic-auth header at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list images in Cloudinary' or 'check account usage', and Jentic returns the matching Admin API operation with its input schema, resolving the cloud_name path parameter, so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Cloudinary Admin API through Jentic.
Why is there no official OpenAPI spec for Cloudinary Admin API?
Cloudinary does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cloudinary Admin API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Cloudinary Admin API use?
The Cloudinary Admin API uses HTTP Basic authentication where the username is your API Key and the password is your API Secret. All requests must be made over HTTPS. Through Jentic, these credentials are stored encrypted in your Jentic One instance - agents authenticate without exposing raw API secrets.
Can I list all images in my Cloudinary account with this API?
Yes. The GET /resources/image endpoint returns all image resources with pagination support. Each response includes public IDs, formats, dimensions, creation dates, and tags. Use the max_results parameter (up to 500) and the next_cursor value for pagination through large libraries.
What are the rate limits for the Cloudinary Admin API?
The Admin API is rate-limited to 500 calls per hour on free plans, scaling up with paid plans. The API returns rate limit headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) with each response so you can track consumption and throttle accordingly.
How do I monitor my Cloudinary usage through Jentic?
Search Jentic for 'check Cloudinary storage usage' to load the GET /usage operation schema. This endpoint returns current-period metrics for storage bytes, bandwidth consumed, transformation credits used, and API calls made - all against your plan limits. Install with pip install jentic.
What is the difference between the Admin API and the Upload API?
The Admin API handles account-level operations: listing resources, managing folders, monitoring usage, and reading configuration. The Upload API handles uploading new assets with transformations applied on ingest. Use the Admin API for auditing and organization; use the Upload API for adding new content.
Can I limit what my agent is allowed to do with the Cloudinary Admin API?
Yes. Because you self-host Jentic One, your own rules decide which Admin API operations the agent may call, so you can grant read-only access such as listing resources with GET /resources/{resource_type}, reading folders with GET /folders, and checking quotas with GET /usage while withholding anything else. A destructive operation like DELETE /resources/{resource_type}/{public_id} is only in reach if you explicitly include it in the set you allow. The API also stays within the single cloud fixed by the {cloud_name} host, and your stored API key and secret are injected at execution time rather than exposed to the agent.
GET STARTED