Cloudinary Upload API

What authentication does the Cloudinary Upload API use?

The Cloudinary Upload API uses HTTP Basic Authentication where the username is your API Key and the password is your API Secret. Alternatively, uploads can use signature-based authentication where you generate a SHA-1 signature from the upload parameters and your API secret. Through Jentic, these credentials are stored encrypted in the MAXsystem vault — agents receive scoped access without your API secret entering their context.

Can I upload videos and raw files, not just images?

Yes. The upload endpoint accepts a resource_type path parameter that can be 'image', 'video', or 'raw'. Each resource type supports the full lifecycle: upload, explicit transformations, tagging, renaming, and deletion. The same endpoint structure applies to all three types.

What are the rate limits for the Cloudinary Upload API?

The Cloudinary Upload API is rate-unlimited for upload operations according to the API documentation. There is no per-second or per-minute throttle on upload calls. However, your account's storage quota and bandwidth limits still apply based on your Cloudinary plan tier.

How do I upload an image through Jentic with an AI agent?

Install the Jentic SDK with pip install jentic, then search for 'upload image to cloudinary'. Jentic returns the POST /{resource_type}/upload operation schema with required parameters (file, api_key, timestamp, signature). The agent constructs the multipart request and executes it — Jentic handles credential injection so the API secret never appears in the agent's context.

Can I apply transformations to an already-uploaded asset without re-uploading it?

Yes. Use the POST /{resource_type}/explicit endpoint with the public_id of the existing asset and an eager array specifying the transformations you want (resize, crop, format change, quality adjustment). Cloudinary generates the derivatives and caches them on CDN without requiring a new upload.

How do I organize assets with tags via the API?

Use POST /{resource_type}/tags with a JSON body containing the command (add, remove, or replace), the tag value, and an array of public_ids. You can tag multiple assets in a single call. Tags serve as the primary mechanism for filtering and retrieving assets from your media library.