Policy-driven by default
Every action an agent takes is subject to the same brand, licensing, and content rules a human reviewer would apply — enforced as the work happens rather than at a final gate.
This is what agentic DAM looks like when it stops being a category description and becomes a product. Cloudinary ships four specialist agents — Taxonomy, Search, Moderation, and Workflow — fronted by a Coordinator Agent that reads your intent and deploys whichever of them the job needs.
They were announced in May 2026 and are built on the same Model Context Protocol servers Cloudinary brought to the DAM market in June 2025 — which is why the second layer of this story, covered on Claimable Clouds & Agent Experience, runs on exactly the same foundation.
The single entry point. Describe the outcome you want and the Coordinator interprets the intent, then deploys the right agent — or the right sequence of agents — to deliver it.
A sentence in plain language — no query syntax, no knowledge of which agent owns which step.
It interprets the intent, decides which specialists are involved, and sequences them.
Taxonomy structures, Search retrieves, Moderation judges, Workflow moves the result downstream.
A finished deliverable plus the record of how it was produced — and a flag on anything that needs a human.
Builds and maintains the metadata structure — keeping tags consistent, values normalized, and the taxonomy safe to evolve as the library grows.
“Add custom fields for expiration and model name to this collection.”
Finds assets by intent rather than by field, so nobody has to know the schema to retrieve the right approved image.
“Show me a final, approved product shot of a handbag from our summer season that can be used for a print campaign only.”
Evaluates assets for quality, consistency, and compliance against brand guidelines and content rules — approving, rejecting, or escalating with its reasoning attached.
“Reject anything with a stock watermark; flag low-quality shots for review.”
Turns a plain-language description of a process into a governed automation spanning ingest, transformation, approval, and delivery.
“When an asset is uploaded to the Products folder, generate alt text, add it to metadata, and send the info to Shopify.”
The reason these agents can be trusted with production libraries is not that they are cautious — it is that every action is policy-driven, permission-aware, and configurable, with human review reserved for the cases that genuinely need judgment.
Every action an agent takes is subject to the same brand, licensing, and content rules a human reviewer would apply — enforced as the work happens rather than at a final gate.
Agents inherit the scoping of the person or system they act for. A search cannot surface an asset the requester was never entitled to see.
Ambiguous decisions route to a reviewer with the agent’s reasoning attached, so a person judges the hard 1% instead of processing the easy 99%.
Automated decisions carry a trail: what was changed, by which agent, on what basis. Autonomy stays reviewable instead of becoming a black box.
Every capability on this page rests on structured metadata: seasons, SKUs, usage rights, approval state, expiry dates. That is why the Taxonomy Agent exists and why it comes first in the lifecycle.
When those fields are consistent, a request like “approved, in-window, print-only” becomes a query an agent can actually satisfy. When they are not, an agent guesses — confidently and wrongly. The unglamorous work of normalizing a taxonomy is what converts a media library into something autonomous systems can reason about, which is also what makes a brand portal like this one trustworthy for the people browsing it.
How enrichment on ingest works
Layer one is Cloudinary's own agents acting on your library. Layer two is the reverse direction: a coding assistant, a chat interface, or an agent inside your own product provisioning a Cloudinary environment and calling media operations as typed tools. Same platform, opposite direction of control — and you need both before “agentic DAM” means anything durable.
Agent names, descriptions, and dates on this page follow Cloudinary's own published material. Screenshots are Cloudinary product imagery. For current capabilities and availability, see Cloudinary's announcement.