# Cloudinary: L4 · Runs on its own

As of 6 Oct 2026, an AI agent gets into Cloudinary on its own and does 100% of the core work.

Source: https://agentdrives.com/tools/cloudinary?via=md · driven 6 Oct 2026 by AgentDrives's agent · 1 drive so far · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0

Runs on its own: L4 · one unauthenticated call to the provisioning endpoint handed our agent a working cloud, a key and secret. From there it read usage, called the MCP servers and uploaded an asset, confirmed through the admin API, all headless. It stopped at the Console: setting a password for the claimed login sits behind a reCAPTCHA checkbox, so upgrading, which needs a card entered there, was never reached. It had nothing to cancel on the free plan. It deleted every asset and config item through the API, but the account itself needs a support request, which this drive did not file, so the claimed login stays open.

_Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_

L4 · Runs on its own: An agent gets in on its own, does at least 80% of the core work and can stop paying on its own: it cancels any plan it started, or there is nothing to cancel. Whether it can also remove what it made shows next to the level.

- Find: Some docs for agents (llms.txt and an MCP server)
- Access: Sign-up in a browser
- Use: 100% of the work
- Pay: Payment not reached
- Leave: Nothing to cancel (Can't delete its account)
- Ways in: Sign-up in a browser, 9 of 9 core tasks
- Next: pay without a person

## Part scores

- Agent-ready setup: llms.txt found, OpenAPI not found, MCP server found, CLI found
- Not measured in this drive: Holds up, Docs match
- Security: reported privately to the owner

## Who gets in

- Agents on a server: Get in on their own.
- Signed agents: The site opens.
- Agents in a person's browser: Not measured yet.

Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies.

## Checkpoints

- **Docs**: Headless: llms.txt (root and /documentation), /auth.md, markdown docs via Accept: text/markdown and .md URLs
- **Sign up**: Headless: Claimable cloud: unauthenticated POST https://api.cloudinary.com/v1_1/provisioning/clouds returned a working cloud, key/secret and claim_url (auth.md 'anonymous' pattern)
- **Verify**: In a browser: Optional claim: claim page + confirmation mail + 'Verify & activate' in the browser; no bot check on these pages
- **Key**: Headless: api_key/api_secret/CLOUDINARY_URL in the provisioning response; same value works as cloudinary-url header on the MCP servers
- **First call**: Headless: GET /usage 200 (plan Free, 25 credits)
- **First action**: Headless: MCP upload-asset created an image, confirmed through Admin API
- **Pay**: Not reached: No 402/x402/MPP/UCP, not in x402 Bazaar or mpp.dev; docs: upgrade via Console > Billing > Plans by credit card, no billing API. Console login for the claimed cloud needs a password set behind a reCAPTCHA v2 checkbox, so checkout was not reached.
- **Cancel**: Not needed: Nothing to cancel: our agent used the free plan.
- **Delete**: Blocked: All assets and account config (presets, transformations, mappings, streaming profile, metadata field, trigger, folders) deleted headless via the API. The account itself was not deleted: docs state 'You can't delete an account yourself, this requires a support request', and no support request was filed in this drive. An unclaimed cloud would self-delete after 24h, but this cloud was claimed, so the claimed login remains active and no rejected-access evidence exists.

## Does Cloudinary have an MCP server, and can an agent connect to it?

Yes. Cloudinary has an official MCP server.

A new agent can get in on its own: in the drive of 6 Oct 2026, our agent signed up, verified and got its key without a person. Through the MCP server, 13 of our agent's 15 attempts worked.

## How does an AI agent get a Cloudinary API key?

In the drive of 6 Oct 2026, our agent got its Cloudinary API key over the API, without a browser or a person. api_key/api_secret/CLOUDINARY_URL in the provisioning response; same value works as cloudinary-url header on the MCP servers

## Paying the agent way

Payment not reached.

Ways to pay it offers an agent: Card checkout.
It has a free plan.

What would let agents pay on their own:
- Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card.
- List your plans on Stripe Projects: Agents buy a plan with `stripe projects add`, paid with a token under a spend cap the owner sets (projects.dev).
From the drive of 6 Oct 2026.

## What an agent can do

- Get a working cloud and API keys with one unauthenticated API call
- Upload images and videos, by file or by remote URL
- Resize, crop, AI-crop, apply effects and text overlays via URL
- Serve auto-format/quality images and HLS adaptive video from the CDN
- Make a short AI preview clip of a video
- Search, tag, organise in folders, add structured metadata, moderate and restore assets
- Create upload presets, named transformations, upload mappings, streaming profiles and triggers via MCP
- Delete all its assets and settings via the API

## What it cannot do

- Log in to the Console: Setting a password for the claimed account goes through a reCAPTCHA v2 checkbox
- Upgrade the plan: Card payment in the Console only; no billing API or agent payment rail
- Delete the account: Docs: account deletion requires a support request
- Use AI tagging, OCR, AI Vision, people search: Add-on or paid subscription required

## Tips for the owner

1. Let agents delete accounts via the API
2. Set the Console password inside the claim flow
3. Support MCP (the 28 Jul 2026 spec) server/discover
4. Fix the provisioning response docs
5. Offer CIMD and drop PKCE plain
6. Publish OpenAPI for Upload and Admin APIs

Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).

## Also in File storage

- [Backblaze B2](https://agentdrives.com/tools/backblaze.md?via=md): L1 · Needs a person · [Cloudinary vs Backblaze B2](https://agentdrives.com/compare/backblaze-vs-cloudinary?via=md)
- [Box](https://agentdrives.com/tools/box.md?via=md): L1 · Needs a person · [Cloudinary vs Box](https://agentdrives.com/compare/box-vs-cloudinary?via=md)
- [Dropbox](https://agentdrives.com/tools/dropbox.md?via=md): L1 · Needs a person · [Cloudinary vs Dropbox](https://agentdrives.com/compare/cloudinary-vs-dropbox?via=md)
- [Pinata](https://agentdrives.com/tools/pinata.md?via=md): L1 · Needs a person · [Cloudinary vs Pinata](https://agentdrives.com/compare/cloudinary-vs-pinata?via=md)

## Tips for agent builders

- Start with POST /v1_1/provisioning/clouds (or npx @cloudinary/cloud) and give the user the claim_url early: unclaimed clouds are deleted after 24 h
- Use the MCP servers with header cloudinary-url: cloudinary://key:secret@cloud; initialize with 2025-11-25
- Put the asset's real version in delivery URLs; folder names like 'ad_test' can be parsed as transformations otherwise
- Search lags uploads by about a minute; dynamic folders mean 'folder:' does not match public_id paths
- Delivery is IP-locked until the claim: declare the viewer's IP