Product-led growth depends on one thing: how fast someone can go from nothing to a working result.<\/p>\n\n\n\n
For over a decade at Cloudinary, that someone was a developer with a free account and a few lines of code. Today, it’s just as often an agent working on that developer’s behalf.<\/p>\n\n\n\n
But an agent explores differently. It doesn’t read a landing page or compare feature tables. It wants to try it: Spin something up, build against it, run the result, and decide for itself, right now, without waiting on anyone.<\/p>\n\n\n\n
So we removed the one step that couldn’t happen without a human: creating the account. No signup, no email confirmation, no click to wait on mid-build.<\/p>\n\n\n\n
npx @cloudinary\/cloud<\/code><\/h2>\n\n\n\nOne command gives any agent a complete, ready-to-use Cloudinary environment, live from the first call, without requiring an email, payment, or ToS click.<\/p>\n\n\n
npx<\/span> @cloudinary<\/span>\/cloud\n\n\u2192 cloud_name:<\/span> \u2026 claim_url:<\/span> \u2026 expires_at:<\/span> 24<\/span>h<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\nUpload, transform, deliver, and preview your results the moment the command returns. The full pipeline is live from line one:<\/p>\n\n\n\n
\n- Content-aware cropping (
g_auto<\/code>).<\/li>\n\n\n\n- Automatic format and quality (
f_auto, q_auto<\/code>).<\/li>\n\n\n\n- Background removal and generative fill.<\/li>\n\n\n\n
- Video transcoding.<\/li>\n\n\n\n
- Generating images from other images or a prompt, and converting stills into video.<\/li>\n<\/ul>\n\n\n\n
The media plumbing \u2014 provisioning, building and verifying work \u2014 is the agent’s job now. Yours is to ship the app.<\/p>\n\n\n\n
Built for Agents, and for the Parts They Can’t Build Alone<\/h2>\n\n\n\n
Cloudinary wasn\u2019t retrofitted for agents. It\u2019s been API-first since day one, built from the ground up for developers who’d rather integrate than click. That same foundation is what makes it native to agents. We have an MCP server agents call directly, and they already are. Agents are provisioning, uploading, and transforming through it today.<\/p>\n\n\n\n
There’s also a reason an agent reaches for us instead of rolling its own media pipeline. It can write a resize in a few lines of sharp, but it can’t stand up a global delivery network, real-time transformation at scale, AI transforms that run in the delivery path, or durable storage and media governance on its own.<\/p>\n\n\n\n
The Claimable Cloud gives the agent the whole platform immediately, at full production capacity. Claiming it unlocks durability and delivery reach: storage that doesn’t expire, global delivery, and governance over what’s public.<\/p>\n\n\n\n
Try Cloudinary for Yourself<\/h2>\n\n\n\n
You don’t have to take our word for it. Run one line:<\/p>\n\n\n
npx<\/span> @cloudinary<\/span>\/cloud<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\nThe response will include your cloud name, API key and secret, and a clam URL. For example:<\/p>\n\n\n
CLOUD_NAME=a1b2c3d4\nAPI_KEY=123456789012345<\/span>\nAPI_SECRET=\u00abredacted\u00bb\nCLOUDINARY_URL=cloudinary:\/\/123456789012345:\u00abredacted\u00bb@a1b2c3d4<\/span>\nEXPIRES_AT=2026<\/span>-08<\/span>-06<\/span>T08:29<\/span>:07<\/span>Z\nCLAIM_URL=https:\/\/res.cloudinary.com\/users\/agent_email_confirmation?token=\u00abredacted\u00bb<\/span>\nDELIVERY_IPS=203.0<\/span>.113<\/span>.7<\/span>,198.51<\/span>.100<\/span>.42<\/span>\nENV_FILE=.\/.env<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\nDELIVERY_IPS<\/code> is the allowlist. Your assets deliver only to these IP addresses. If you encounter any issues with ACL restriction, claiming the cloud lifts the restriction.<\/p>\n\n\n\nHere’s a quick demo:<\/p>\n\n\n\n <\/video>\n <\/cld-video-player>\n\n\nThen point your agent at something real. Here are some examples:<\/p>\n\n\n\n
\n- A new page, built media-first.<\/strong> Build a performant landing page \u2014 hero video, image gallery, product shots \u2014 with content-aware crops that keep the subject centered from hero to thumbnail, format and quality optimized per browser, backgrounds removed and replaced, a video transcoded with its poster frame taken from the same source.<\/li>\n\n\n\n
- Migrating an application you already have.<\/strong> Point your agent at an existing site and ask it to migrate the imagery: Find all referenced assets, upload them, and rewrite the references to optimized delivery URLs with responsive widths, automatic format and quality, and smart cropping.<\/li>\n\n\n\n
- One source asset, multiple channels.<\/strong> Give your agent a campaign photo or video and the list of output channels for distribution. Produce the set: each aspect ratio cropped, each format and file size matched to its destination, a short vertical cut of the video. What comes back is the full variant set, and a pipeline that can also regenerate it when the source changes.<\/li>\n<\/ul>\n\n\n\n
Agents Build and Verify. Humans Decide What Goes Public.<\/h2>\n\n\n\n
The Claimable Cloud is capped and time-boxed by design, but not simulated. Underneath it is the same infrastructure that serves our production traffic. The limits are on duration and reach, not on what the platform does.<\/p>\n\n\n\n
While it lives, the agent has the full API and can preview its work in allowlisted environments \u2014 everything the build loop needs, and nothing to rebuild when a human claims it.<\/p>\n\n\n\n
What the agent doesn’t get is a durable public URL. Publishing is a human’s call, on purpose. Agents get the freedom to explore, but humans keep accountability for what reaches the world.<\/p>\n\n\n\n
When you like what the agent built and want to ship it, claim the cloud with your email. Everything your app needs transfers intact:<\/p>\n\n\n\n