Agent readiness · File upload and storage
cloudinary.com
10 of 13 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 2 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.
A · Discovery
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- PASSllms.txt publishedllms.txt present at https://cloudinary.com/llms.txt and https://cloudinary.com/documentation/llms.txt, and the 12 links we sampled across the file all answer
- PASSDocs readable without JavaScript36,092 characters of text without JS, on https://cloudinary.com/documentation/ts_how_to_rotate_api_keys_in_the_console rather than on https://cloudinary.com/documentation
- PASSOn-demand agents not blockedNo on-demand agent is blocked
- N/APaths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- UNMEASUREDAgent entry pointUnmeasurable: 4 of the 9 known agent entry paths answered with a refusal rather than a file or a 404, so what you publish there is not something we measuredLet ordinary HTTP reach these paths and this becomes measurable.
- FAILOAuth dynamic client registrationOAuth metadata published, but no registration_endpoint in it
- FAILMCP surfaceMCP mentioned 4x in your own files, but nothing answered at mcp.cloudinary.com, mcp.cloudinary.com/mcp, mcp.cloudinary.com/v1/mcp, api.cloudinary.com/mcp, /mcp or /api/mcp
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://console.cloudinary.com/signup is not in the server HTML, so its gates are not eitherServer-render the form, or tell us the endpoint it posts to, and the gates become visible to us and to an agent.
- FAILSignup reachable without a browserhttps://console.cloudinary.com/signup is reachable, but its form needs JavaScript
D · Provisioning
- PASSProgrammatic key provisioning2 of 7 provisioning phrases across the 6 documents we read: "management api", "provisioning api"
- PASSFree tier or no-card trial stated in textFree tier or no-card signals at https://cloudinary.com/pricing: "No credit card", "Free forever", "$0"
E · Integration
- PASSTyped SDK on the registrycloudinary@2.10.0 ships types, matched from the registry by who publishes it rather than by a link on your site
- PASSMachine-readable API descriptionDocs serve markdown to machines, at https://cloudinary.com/documentation
Tell me when this changes
The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for cloudinary.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.