Box vs Cloudinary 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: Docs for agents: llms.txt, an OpenAPI 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
L1 · Needs a person describes Box today. Our agent stopped at signup: both the personal and developer forms put an hCaptcha checkbox in front of account creation, and there is no API or CLI path around it. Everything before that door works well: Markdown docs with llms.txt, a public OpenAPI reference, a CLI and an official OAuth MCP server. Past that wall, work, keys and paying all wait in the Developer Console and web checkout, so a person has to open the account before any of it runs.
Driven 12 Oct 2026 · The drive and its evidence- 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 evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
BoxStopped at sign up: needs a human
CloudinaryGot in; payment not reached
| Checkpoint | Box | Cloudinary |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human | Headless |
| Verify | Not reached | In a browser |
| Key | Not reached | Headless |
| First call | Not reached | Headless |
| First action | Not reached | Headless |
| Pay | Not reached | Not reached |
| Cancel | Not reached | Not needed |
| Delete | Not reached | Blocked |
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
| Box | Cloudinary | |
|---|---|---|
| Headless (checkpoints) | 1 | 5 |
| In a browser (checkpoints) | 0 | 1 |
| Needs a human (checkpoints) | 1 | 0 |
| Blocked (checkpoints) | 0 | 1 |
| Not tested (checkpoints) | 7 | 1 |
| Work done | Not measured | 100% of the core |
| API | Yes | Yes |
| OpenAPI | Yes | No |
| MCP server | Yes (official) | Yes (official) |
| CLI | Yes | Yes |
| SDK | Yes | Yes |
| llms.txt | Yes | Yes |
Bot checks, and where a person was needed.
| Box | Cloudinary | |
|---|---|---|
| Bot check | hCaptcha stopped it at sign up, with a visible challenge | Console password reCAPTCHA; account delete needs support; it got in another way |
| Wall type | A challenge on the form | A challenge on the form |
| First wall | hCaptcha on the sign-up form | Got in; payment not reached |
| 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.
| Box | Cloudinary | |
|---|---|---|
| Level | L1 · Needs a person | L4 · Runs on its own |
| Agent-ready setup | 100 of 100, good | 75 of 100, fair |
| Standards | OpenAPI 3.0.2 (2 versions behind) | MCP spec of 25 Nov 2025 (1 version behind) · MCP discovery (behind) · MCP client registration (behind) · OpenAPI 3.0.3 (2 versions behind) |
| Security | No review in this drive | Reported privately to the owner |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| Box | Cloudinary | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not reached | Not needed |
| Delete the account | Not reached | Blocked |
How each one takes payment
- Box: Payment not reached.
- Cloudinary: Payment not reached.
Box vs Cloudinary: the short answers.
Which can an AI agent use, Box or Cloudinary?
Cloudinary gets an AI agent further: L4 · Runs on its own against L1 · Needs a person. With Box our agent was stopped at sign up (needs a human); with Cloudinary it got in (payment not reached). Driven 12 Oct 2026 (Box) and 6 Oct 2026 (Cloudinary).
Can an AI agent sign up for Box and Cloudinary on its own?
Box: no, needs a human. Cloudinary: yes, headless.
Do Box and Cloudinary have an MCP server?
Box: yes (official). Cloudinary: yes (official).
Can an AI agent delete its Box or Cloudinary account?
Box: not reached. Cloudinary: blocked.
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.