Cloudinary vs Dropbox for AI agents
As of 12 Oct 2026, Cloudinary gets an AI agent further: L4 · Runs on its own against L1 · Needs a person.
- 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.
Got in; payment not reached. Next: pay without a person
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.
Gets furtherDriven 6 Oct 2026 · The drive and its evidence- Find: Some docs for agents: llms.txt and an MCP server.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: needs a human. Next: let an agent sign up on its own
A person has to sign up: L1 · Needs a person. Sign-up stops first: the web form shows an Arkose Labs puzzle after "Agree and sign up," so our agent never reached verification, a key, or a first call. Even without an account, Dropbox's agent surface holds up: public API docs, an llms.txt file, an official MCP server, and headless OAuth client registration through DCR all worked. The Standard trial checkout asks for a card, PayPal, or IBAN; no account was ever created, so cancelling and deleting were never tested.
Driven 12 Oct 2026 · The drive and its evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
CloudinaryGot in; payment not reached
DropboxStopped at sign up: needs a human
| Checkpoint | Cloudinary | Dropbox |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Headless | Needs a human |
| Verify | In a browser | Not reached |
| Key | Headless | Not reached |
| First call | Headless | Not reached |
| First action | Headless | Not reached |
| Pay | Not reached | Not reached |
| Cancel | Not needed | Not reached |
| Delete | Blocked | Not reached |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| Cloudinary | Dropbox | |
|---|---|---|
| Headless (checkpoints) | 5 | 1 |
| In a browser (checkpoints) | 1 | 0 |
| Needs a human (checkpoints) | 0 | 1 |
| Blocked (checkpoints) | 1 | 0 |
| Not tested (checkpoints) | 1 | 7 |
| Work done | 100% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | No | No |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | No |
| SDK | Yes | – |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Cloudinary | Dropbox | |
|---|---|---|
| Bot check | Console password reCAPTCHA; account delete needs support; it got in another way | Arkose Labs (FunCaptcha) stopped it at sign up, with a visible challenge |
| Wall type | A challenge on the form | A challenge on the form |
| First wall | Got in; payment not reached | Arkose puzzle on the sign-up form |
| A person helped | No | No |
A challenge on the form: It asks every visitor to prove they are human. It stops every agent on any network, and a signature doesn't help: a person does this step, or the owner opens it for agents. Where we drive from.
Level and part scores.
| Cloudinary | Dropbox | |
|---|---|---|
| Level | L4 · Runs on its own | L1 · Needs a person |
| Agent-ready setup | 75 of 100, fair | 75 of 100, fair |
| Standards | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) · MCP client registration (behind) · OpenAPI 3.0.3 (2 versions behind) | MCP client registration (behind) |
| Security | Reported privately to the owner | No review in this drive |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Cloudinary | Dropbox | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Free plan | Trial with a card |
| Cancel | Not needed | Not reached |
| Delete the account | Blocked | Not reached |
How each one takes payment
- Cloudinary: Payment not reached.
- Dropbox: Payment not reached.
Cloudinary vs Dropbox: the short answers.
Which can an AI agent use, Cloudinary or Dropbox?
Cloudinary gets an AI agent further: L4 · Runs on its own against L1 · Needs a person. With Cloudinary our agent got in (payment not reached); with Dropbox it was stopped at sign up (needs a human). Driven 6 Oct 2026 (Cloudinary) and 12 Oct 2026 (Dropbox).
Can an AI agent sign up for Cloudinary and Dropbox on its own?
Cloudinary: yes, headless. Dropbox: no, needs a human.
Do Cloudinary and Dropbox have an MCP server?
Cloudinary: yes (official). Dropbox: yes (official).
Can an AI agent delete its Cloudinary or Dropbox account?
Cloudinary: blocked. Dropbox: not reached.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.