Backblaze B2 vs Cloudinary for AI agents
As of 6 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: Can't sign up.
- Use: 0% of the work.
- Pay: Payment not reached.
- Leave: Nothing to cancel: Can't delete its account.
Stopped at verify: blocked. Next: let an agent sign up on its own
Needs a person stops this one before it starts: both sign-up pages show a Google reCAPTCHA v2 checkbox on Backblaze's own Security Check page, so our agent never got past the form to verify, get a key, or make a call. Pay and cancel never came up either: our agent had no account to check out from or close. What works well sits past that wall: Markdown docs, an llms.txt file, and an official MCP server with a wide set of tools, all ready once a person signs up, verifies, and makes the key by hand. Deleting the account, per the docs, is a web-console step only.
Driven 6 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.
Backblaze B2Stopped at verify: blocked
CloudinaryGot in; payment not reached
| Checkpoint | Backblaze B2 | Cloudinary |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | Needs a human (a person did it) | Headless |
| Verify | Blocked | In a browser |
| Key | Blocked | Headless |
| First call | Blocked | Headless |
| First action | Blocked | Headless |
| Pay | Not reached | Not reached |
| Cancel | Not needed | Not needed |
| Delete | Blocked | 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
| Backblaze B2 | Cloudinary | |
|---|---|---|
| Headless (checkpoints) | 1 | 5 |
| In a browser (checkpoints) | 0 | 1 |
| Needs a human (checkpoints) | 1 | 0 |
| Blocked (checkpoints) | 5 | 1 |
| Not tested (checkpoints) | 1 | 1 |
| Work done | 0% of the core | 100% of the core |
| API | Yes | Yes |
| OpenAPI | No | 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.
| Backblaze B2 | Cloudinary | |
|---|---|---|
| Bot check | Google reCAPTCHA v2 checkbox (on Backblaze's own 'Security Check' page; reCAPTCHA Enterprise script on the form) 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 | reCAPTCHA interstitial on the sign-up page | Got in; payment not reached |
| A person helped | sign up (human) | 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.
| Backblaze B2 | Cloudinary | |
|---|---|---|
| Level | L1 · Needs a person | L4 · Runs on its own |
| Agent-ready setup | 75 of 100, fair | 75 of 100, fair |
| Standards | MCP spec of 28 Jul 2026 (current) · MCP discovery (current) | 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.
| Backblaze B2 | Cloudinary | |
|---|---|---|
| Pay | Payment not reached | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not needed | Not needed |
| Delete the account | Blocked | Blocked |
How each one takes payment
- Backblaze B2: Payment not reached.
- Cloudinary: Payment not reached.
Backblaze B2 vs Cloudinary: the short answers.
Which can an AI agent use, Backblaze B2 or Cloudinary?
Cloudinary gets an AI agent further: L4 · Runs on its own against L1 · Needs a person. With Backblaze B2 our agent was stopped at verify (blocked); with Cloudinary it got in (payment not reached). Both driven 6 Oct 2026.
Can an AI agent sign up for Backblaze B2 and Cloudinary on its own?
Backblaze B2: no, needs a human. Cloudinary: yes, headless.
Do Backblaze B2 and Cloudinary have an MCP server?
Backblaze B2: yes (official). Cloudinary: yes (official).
Can an AI agent delete its Backblaze B2 or Cloudinary account?
Backblaze B2: blocked. 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.