DigitalOcean: the 360 agent-readiness check
DigitalOcean scores 74 of 100 on Ora's agent-readiness scan, a B, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 2: an OpenAPI specification, a public API. An OpenAPI file and an MCP server, with the OAuth discovery document missing.
On 9 November 2026 the public site at digitalocean.com scored 74 of 100 on Ora's agent-readiness scan, a B, in Ora's Infrastructure category. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. This check reads the act layer first, because that is what the directory records, then the door, what an agent can read, and whether the company is found and recommended. Ora's one-line summary: DigitalOcean offers well-documented APIs and SDK packages, but lacks OAuth 2.0 support for agent authentication.
The score
| Layer | Asks | Points | Share |
|---|---|---|---|
| Usability | Can agents use it | 57 of 77 | 74% |
| Access | Can agents read it | 43 of 59 | 73% |
| Discovery | Can agents find and recommend it | 14 of 18 | 78% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade B | 74 of 100 | 74% |
What an agent can do
The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, OAuth metadata, a command line. This is the layer the directory records, so it comes first.
In the directory, DigitalOcean sign-in required, tools not seen, not counted; the connector run of 4 November 2026 is on the entry page. Ora's MCP server check for the same domain reads partial; the two look for different things, the directory for a server that answers a handshake and lists tools, Ora for a server it can find from the site.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| MCP server / manifest mcp-server | Partial | 5 of 6 | MCP server detected at https://mcp.digitalocean.com/mcp; it requires authentication. Presence is verified (5/6), but Ora could not inspect its tools or verify access scopes without credentials. |
| MCP well-known discovery mcp-well-known-discovery | Partial | 1 of 2 | MCP server at https://mcp.digitalocean.com/mcp - list its server card, hosted on your own domain, in /.well-known/ai-catalog.json so MCP clients can discover it |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | Documented REST API detected; endpoints require authentication (API key / OAuth), which is expected for agent access. Best-of-protocols score: 7/7. |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://docs.digitalocean.com |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at https://docs.digitalocean.com |
| OpenAPI spec published openapi-spec | Pass | 7 of 7 | OpenAPI spec found at https://docs.digitalocean.com/reference/api/reference/openapi.json (version: 3.0.0) |
| API catalog (RFC 9727) api-catalog-rfc9727 | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| A2A / agent-card a2a-agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Agent discovery file agent-discovery-file | Fail | 0 of 2 | No agent discovery file found |
| OAuth 2.0 support oauth-support | Fail | 0 of 5 | No OAuth 2.0 or OpenID Connect support detected |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Pass | 2 of 2 | no detail published |
| auth.md exists auth-md-exists | Fail | 0 of 2 | No /auth.md found at site root |
| WebMCP support webmcp | Fail | 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 45 of 45 same-origin script bundle(s) for modelContext registrations) |
| NLWeb /ask endpoint nlweb-ask | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| CLI tool available cli-tool | Partial | 2 of 3 | CLI tool mentioned at https://docs.digitalocean.com/reference/doctl/ |
| Multi-language SDK packages rest-sdk-packages | Pass | 3 of 3 | SDK packages found across 3 ecosystems: npm, pypi, rubygems |
| Rate limit response headers rate-limit-headers | Partial | 1 of 2 | REST rate-limit headers documented in OpenAPI spec, but not observed on a live response (API requires authentication). |
| Idempotency-Key support idempotency-key-support | Partial | 1 of 3 | Idempotency-Key support documented at https://docs.digitalocean.com/reference/api/reference/openapi.json but not verified on a live response (REST API is auth-gated) |
| JSON error responses json-error-responses | Pass | 4 of 4 | no detail published |
At the door
What the site answers when a request arrives with an agent's user agent, and what robots.txt says to agents.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Not blocked by bot detection bot-detection | Pass | 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| Agent crawler reachability agent-crawler-reachability | Pass | 2 of 2 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |
| robots.txt AI crawler policy robots-ai-policy-quality | Pass | 2 of 2 | AI search crawlers: allowed in 3 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 2 of 2 checks (2 crawlers on 1 page), not scored. |
| robots.txt agent-user policy robots-agent-user-policy | Pass | 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://digitalocean.com/. Declared policy only; |
| Content behind auth docs-auth-gate | Pass | 2 of 2 | All 5 sampled pages are publicly readable (5 with substantive content) |
| Homepage not hidden from search noindex-directives | Pass | 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search. |
| Redirect hygiene redirect-hygiene | Pass | 1 of 1 | no detail published |
| Web Bot Auth directory web-bot-auth-directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |
What an agent can read
Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Content without JavaScript content-no-js | Partial | 2 of 3 | Homepage: 6088 chars with H1, but 4.7% content ratio is below the 5% target. 5 of 5 sampled inner pages have text without JavaScript. |
| Page token budget page-token-budget | Pass | 1 of 1 | All 6 measured pages fit an agent context budget (largest ~2K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://www.digitalocean.com/sitemap.xml with multiple sitemaps entries |
| Sitemap freshness (lastmod) sitemap-lastmod | Partial | 0 of 1 | Sitemap lastmod dates are all stale - the newest is 1363 days old. Update lastmod when content changes or agents will deprioritize the whole site as unmaintained. |
| llms.txt exists llms-txt-exists | Pass | 1 of 1 | Found the llms.txt at https://docs.digitalocean.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Partial | 1 of 2 | The llms.txt is well-formatted with markdown links, but at 72,919 characters it exceeds the 30,000-character recommendation for a navigation index. |
| llms.txt links resolve llms-txt-links-resolve | Pass | 2 of 2 | no detail published |
| Markdown agent docs markdown-negotiation | Fail | 0 of 1 | Missing markdown content negotiation. Homepage returned text/html when probed with Accept: text/markdown (expected text/markdown), and none of the well-known root paths (/llms.md, /auth.md, /agents.md, /developers.md, |
| Markdown URL fallback markdown-url-fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://digitalocean.com/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| Bot-UA markdown serving agent-ua-markdown | Fail | 0 of 1 | No probed bot User-Agent (ChatGPT-User, Claude-User, Perplexity-User) receives markdown when requesting HTML. Optional: detect AI-bot UAs server-side and serve them a markdown representation directly. |
| Agent mode view agent-mode-view | Fail | 0 of 2 | ?mode=agent returns same content as homepage (no dedicated agent view) |
| JSON-LD structured data json-ld | Fail | 0 of 4 | No JSON-LD structured data found on homepage |
| Organization schema completeness org-schema-completeness | Fail | 0 of 2 | No JSON-LD found - Organization schema missing |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Fail | 0 of 2 | No JSON-LD found - no entity linking possible |
| Schema type breadth schema-type-breadth | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity |
| Metadata completeness metadata-completeness | Partial | 1 of 2 | 2/4 metadata signals present - missing: og:image, og:type |
| Agent instruction / when-to-use agent-instruction | Partial | 2 of 3 | When-to-use guidance found at https://docs.digitalocean.com |
Found and recommended
Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Brand name discoverability brand-search-accuracy | Fail | 0 of 3 | digitalocean.com was not in the top 10 for "AI" (searched your brand name alone: no main product term from your homepage qualified) |
| Wikipedia / Wikidata entity presence wikipedia-presence | Pass | 4 of 4 | Wikipedia "DigitalOcean" and Wikidata Q17052116 both verified - domain confirmed on both sources |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| Listed in MCP registries mcp-registry-listed | Pass | 1 of 1 | no detail published |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| ChatGPT app listed chatgpt-app-listed | Pass | 2 of 2 | no detail published |
| Registry branding registry-branding | Fail | 0 of 2 | No registry branding (name, icon, description) found |
| Listed on skills.sh skills-sh-listed | Pass | 1 of 1 | no detail published |
| ARD discovery ard-catalog | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json |
Payments
The agent payment protocols Ora probes for. A site that sells nothing has nothing here, and Ora scores the layer out of zero when none applies. None of the 6 payment checks applied to digitalocean.com.
The fixes worth most points
Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for DigitalOcean, with what Ora observed. The wording of each fix is Ora's; the 28 checks it runs on an MCP server are listed with their layer and tier.
- Brand name discoverability: fail, 0 of 3, about 3.7 points to gain. Ora saw: digitalocean.com was not in the top 10 for "AI" (searched your brand name alone: no main product term from your homepage qualified)
- OAuth 2.0 support: fail, 0 of 5, about 2.9 points to gain. Ora saw: No OAuth 2.0 or OpenID Connect support detected
- WebMCP support: fail, 0 of 5, about 2.9 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 45 of 45 same-origin script bundle(s) for modelContext registrations)
- JSON-LD structured data: fail, 0 of 4, about 2.3 points to gain. Ora saw: No JSON-LD structured data found on homepage
- Scoped permissions: partial, 2 of 5, about 1.7 points to gain. Ora saw: OpenAPI declares security schemes but no named OAuth scopes - agents get all-or-nothing access. Declare per-scope grants (e.g. read:*, write:*) in the spec.
Our read
DigitalOcean has the specification and not the sign-in. An OpenAPI 3.0.0 file is published at docs.digitalocean.com/reference/api/reference/openapi.json, the MCP server at mcp.digitalocean.com/mcp answers and requires authentication, SDKs are in npm, PyPI and rubygems, doctl is documented, docs.digitalocean.com carries an llms.txt and five of five sampled pages read. The OAuth check found no OAuth 2.0 or OpenID Connect discovery, which is the one act-layer gap that costs real points, and the specification declares security schemes without naming scopes. The reading side has two misses that are cheap to fix and one that is not: no JSON-LD on the home page, a text ratio just under the 5 percent target, and a brand search that Ora ran on the word AI, which the domain was never going to win. None of the 45 script bundles registers a WebMCP tool. A discovery document for OAuth would finish the act layer.
Test your own surfaces
The scan above is free and needs no account: enter a domain at ora.ai and read the same four layers for your own site. For an MCP server, Ora scans the server URL itself and runs 28 of its 132 public checks on it, which is why it is the check this directory recommends; the reasons, the limits and the alternatives are on their own page. The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy.
npx ax@0.10 audit https://example.com --min-score 70All 360 checks, one company a day. Corrections to the corrections page.