Oracle: 22 of 100 on Ora's agent-readiness scan
In short
Oracle scores 22 of 100 on Ora's agent-readiness scan, grade F, read on 15 November 2026. 9 percent of the 132,085 domains Ora ranks score under 20, and the average score is 44. Every assistant Ora sent was blocked, with a GraphQL endpoint and API docs behind the wall.
The score
Oracle is a database, applications and cloud company based in Austin, Texas.
- 22of 100, grade FOra's agent-readiness scan of oracle.com, read 15 November 2026, listed under Infrastructure.
- 6Discovery, of 9Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 1Access, of 35Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 9Usability, of 68Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
- 0Payments, of 0No check in this layer applied to the site.
9 percent of the 132,085 domains Ora ranks score under 20, and the average score is 44.
Ora's one-line summary: Turns agents away at the door: bot detection blocks ChatGPT-User, OAI-SearchBot, Claude-User and PerplexityBot from the homepage.
What an assistant meets at the door
Before an assistant can read, compare or buy, it has to get in. These rows are the door: whether the bot shield lets the main agents through, what robots.txt tells the search, training and user-triggered agents, and whether the home page has text without running JavaScript.
| Check | Result | What Ora saw |
|---|---|---|
| Not blocked by bot detection | Fail, 0 of 2 | Agents blocked: ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot |
| Agent crawler reachability | Fail, 0 of 1 | No agent we tested can reach the homepage - ChatGPT-User: blocked, OAI-SearchBot: blocked, Claude-User: blocked, PerplexityBot: blocked |
| robots.txt AI crawler policy | Did not apply, 0 of 1 | Cannot verify robots.txt permission for search crawlers: HTTP 403 |
| robots.txt agent-user policy | Did not apply, 0 of 1 | Cannot verify robots.txt permission for user-triggered agents: HTTP 403 |
| Content without JavaScript | Did not apply, 0 of 5 | Can't verify: our request for the homepage got no page back, so there is nothing to read without JavaScript. |
| Homepage not hidden from search | Did not apply, 0 of 1 | Homepage not read - cannot tell whether it is hidden from search |
What it can read, and what it can do
The reading layer is what an assistant takes away from the pages: a text file written for it, markdown on request, structured data about the company, a sitemap. The act layer is whether it can do anything through a published interface rather than by clicking through the site.
| Check | Result | What Ora saw |
|---|---|---|
| llms.txt exists | Fail, 0 of 1 | No llms.txt found at /llms.txt or /.well-known/llms.txt. |
| llms.txt formatting | Fail, 0 of 2 | No llms.txt found to evaluate quality |
| Markdown agent docs | 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). |
| Bot-UA markdown serving | 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. |
| JSON-LD structured data | error, 0 of 2 | Could not fetch homepage |
| Organization schema completeness | error, 0 of 1 | Could not fetch homepage |
| Sitemap exists | Fail, 0 of 1 | No sitemap found |
| Metadata completeness | error, 0 of 1 | Could not fetch homepage |
| Page token budget | Did not apply, 0 of 1 | Nothing sampled to measure |
| Check | Result | What Ora saw |
|---|---|---|
| MCP server / manifest | Fail, 0 of 10 | No MCP server or manifest found |
| MCP well-known discovery | Fail, 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints | Pass, 8 of 8 | GraphQL endpoint at https://oracle.com/graphql is reachable; introspection requires authentication (API key / OAuth), which is expected for agent access. Best-of-protocols score: 7/7. |
| Public API/docs linked from homepage | Fail, 0 of 4 | No public API or documentation page linked from homepage |
| OpenAPI spec published | Fail, 0 of 8 | No OpenAPI/Swagger specification found |
| Developer portal | Fail, 0 of 5 | No developer portal found |
| OAuth 2.0 support | Fail, 0 of 5 | No OAuth 2.0 or OpenID Connect support detected |
| Scoped permissions | Fail, 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found |
| CLI tool available | Fail, 0 of 3 | No CLI tool found |
| WebMCP support | Fail, 0 of 8 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found |
| Check | Result | What Ora saw |
|---|---|---|
| Brand name discoverability | Partial, 1 of 3 | oracle.com ranks #10 for "oracle" (searched your brand name alone: we could not read a product term from your site) |
| Developer resource discoverability | Pass, 4 of 4 | In a search for your API docs, your docs came up at #2 (https://docs.oracle.com/cd/E80480_01/87749.htm). In a search for your MCP server, SDK or CLI. |
The six payment checks did not apply on this read: Ora did not read the site as a shop.
Three fixes to hand to the web team
Ora estimates how many points each open check would return. These are the largest on this read, in Ora's words where it gave them, so a leader can hand the list over without translating it.
- OpenAPI spec published, worth about 7.6 points by Ora's estimate: No OpenAPI/Swagger specification found.
- MCP server / manifest, worth about 6.5 points by Ora's estimate: No MCP server or manifest found.
- WebMCP support, worth about 5.2 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found.
Our read
Oracle's read turns on a shut door. ChatGPT-User, OAI-SearchBot, Claude-User and PerplexityBot were all blocked at the home page, and robots.txt answered with a 403, so the Access layer reads 1 of 35. Ora's own request for the home page got no page back, which leaves content, structured data and metadata unverified rather than failed. For a business leader, the cost is visibility: an assistant asked about Oracle cannot read the company's own account of itself. A GraphQL endpoint answers behind authentication, an NLWeb /ask endpoint answers 403, and a search for the API docs found docs.oracle.com second; Ora found neither an OpenAPI specification nor an MCP server. The brand search ranked oracle.com tenth for the bare word oracle, which says more about the probe than the company. The fix worth most is an OpenAPI specification, about 7.6 points. An F at 22: the database company answers every agent query with a 403.
Test your own site
Run the same scan on your own domain at ora.ai. The score, the layers and the fixes on this page come from its public result for oracle.com; a scan of a public site takes a few minutes and needs no account.
- Scan your domain on OraThe same checks, the same scoring, on your own site.
- The self-check, 18 questionsWhat to ask for, in business terms, before the scan.
- All the 360 checksThe other companies in this series, newest first.
Sources
- Ora report for oracle.com (ora.ai/score/oracle.com), read 15 Nov 2026. Vendor claim.
Last reviewed