Cloudinary Admin API

Name: Cloudinary Admin API API
Brand: Cloudinary Admin API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaImage Processingbasic11 EndpointsREST

For Agents

Administer Cloudinary media assets, folders, and account configuration. List resources by type, organize folder structures, and monitor storage and bandwidth usage quotas.

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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 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

GET STARTED

Start building with Cloudinary Admin API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Cloudinary Admin API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Cloudinary Admin API 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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Cloudinary API Key and Secret are stored encrypted in the Jentic vault (MAXsystem). Agents receive pre-authorized Basic auth headers — raw secrets never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'list images in Cloudinary') and Jentic returns matching Admin API operations with their input schemas, including cloud_name path parameter resolution.

Time to first call

Direct Cloudinary Admin API integration: 1-2 days for auth setup, pagination handling, and rate limit management. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Cloudinary Upload API

Upload and transform media assets with on-ingest processing

Use alongside the Admin API when you need to upload new images or videos with transformations — the Admin API only manages existing resources

Alternative

Backblaze B2 Cloud Storage API

Low-cost object storage without media-specific transformations

Choose Backblaze B2 when you need raw file storage at minimal cost without image/video transformation features

Alternative

Google Cloud Storage

General-purpose object storage with CDN integration

Choose Google Cloud Storage when you need infrastructure-level object storage without media-specific management features like folder organization or usage monitoring by asset type

FAQs

Specific to using Cloudinary Admin API 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 at https://app.jentic.com/sign-up.

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 the MAXsystem vault — 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.