---
title: "Apple: 54 of 100 on Ora's scan | Am I Ready for Agents?"
description: "Apple scores 54 of 100 on Ora's agent-readiness scan, grade C, read 9 Nov 2026. Four agents in, a full developer portal, and no sign-in an agent can use."
canonical: https://amireadyforagents.com/blog/apple-agent-readiness
site: "Am I Ready for Agents?"
last_updated: 2026-11-09
date: 2026-11-09
section: "360 checks"
---

# Apple: 54 of 100 on Ora's scan | Am I Ready for Agents?

> Apple scores 54 of 100 on Ora's agent-readiness scan, grade C, read 9 Nov 2026. Four agents in, a full developer portal, and no sign-in an agent can use.

Source: https://amireadyforagents.com/blog/apple-agent-readiness
Site: Am I Ready for Agents?
Last reviewed: 2026-11-09

# Apple: 54 of 100 on Ora's agent-readiness scan

## In short

Apple scores 54 of 100 on Ora's agent-readiness scan, grade C, read on 9 November 2026. 60 percent of the 132,085 domains Ora ranks score under 50, and the average score is 44. Four agents in, a full developer portal, and no sign-in an agent can use.

## The score

Apple makes the iPhone, the Mac and the services around them from Cupertino, California.

-   54of 100, grade C
    
    Ora's agent-readiness scan of apple.com, read 9 November 2026, listed under Identity & Auth.
    
-   14Discovery, of 15
    
    Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
    
-   32Access, of 56
    
    Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
    
-   18Usability, of 58
    
    Whether they can act through it: an MCP server, an API with a specification, sign-in for agents.
    
-   0Payments, of 0
    
    No check in this layer applied to the site.
    

60 percent of the 132,085 domains Ora ranks score under 50, and the average score is 44.

Ora's one-line summary: The site offers strong developer resource discoverability and an SDK package, but lacks a published OpenAPI specification for machine-readable API access.

## 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 | Pass, 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| 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 | 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 | 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://apple.com/. Declared policy only; |
| Content without JavaScript | Partial, 2 of 3 | Homepage: 1748 chars with H1, but 1.8% content ratio is below the 5% target. 5 of 5 sampled inner pages have text without JavaScript. |
| Homepage not hidden from search | 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. |

## 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 | Partial, 2 of 4 | JSON-LD Organization found - missing description on this entity |
| Organization schema completeness | Partial, 1 of 2 | Organization schema found but missing: address |
| Sitemap exists | Pass, 2 of 2 | Valid sitemap found at https://www.apple.com/shop/sitemap.xml with multiple sitemaps entries |
| Metadata completeness | Pass, 2 of 2 | All metadata signals present: canonical URL, lang="en-US", og:image, og:type |
| Page token budget | Pass, 1 of 1 | All 6 measured pages fit an agent context budget (largest ~5K tokens) |

| Check | Result | What Ora saw |
| --- | --- | --- |
| MCP server / manifest | Fail, 0 of 6 | No MCP server or manifest found |
| MCP well-known discovery | Fail, 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints | Partial, 3 of 7 | API described in documentation at https://developer.apple.com but no machine-verifiable API surface confirmed. Best-of-protocols score: 3/7. |
| Public API/docs linked from homepage | Pass, 3 of 3 | Documentation site found at https://developer.apple.com |
| OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found |
| Developer portal | Pass, 6 of 6 | Developer portal found at /developer |
| 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 |
| Multi-language SDK packages | Partial, 1 of 3 | SDK package found only in npm |
| CLI tool available | Fail, 0 of 3 | No CLI tool found |
| WebMCP support | Fail, 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 15 of 15 same-origin script bundle(s) for modelContext registrations) |

| Check | Result | What Ora saw |
| --- | --- | --- |
| Wikipedia / Wikidata entity presence | Partial, 2 of 4 | Wikidata Q312 (Apple Inc.) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage |
| Brand name discoverability | Pass, 3 of 3 | apple.com ranks #4 for "Apple" (searched your brand name alone: no main product term from your homepage qualified) |
| Category share of voice | Did not apply, 0 of 6 | Category share of voice is in beta. It measures whether agents surface you for capability and use-case searches (not just your name). |
| Developer resource discoverability | Pass, 3 of 3 | In a search for your API docs, your docs came up at #3 (https://developer.apple.com/documentation) |

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.

1.  MCP server / manifest, worth about 4.6 points by Ora's estimate: No MCP server or manifest found.
2.  OpenAPI spec published, worth about 4.2 points by Ora's estimate: No OpenAPI/Swagger specification found.
3.  OAuth 2.0 support, worth about 3.8 points by Ora's estimate: No OAuth 2.0 or OpenID Connect support detected.

## Our read

Apple opens the door and keeps the workshop shut. All four agent user agents reach apple.com, robots.txt allows the search and training crawlers in every check, five of five sampled pages read with substantive text and the home page carries an H1 and a complete set of metadata, though its 1,748 characters are a 1.8 percent text ratio against the 5 percent target; the Organization block lacks only its description, and there is no llms.txt. The Discovery layer is nearly full at 14 of 15. The act layer is where the company that makes the iPhone earns a C: developer.apple.com is a real portal and documentation site and an SDK sits on npm, but Ora found neither an OpenAPI specification nor an MCP server, and no OAuth or OpenID Connect discovery, so the Usability layer reads 18 of 58. Sign in with Apple exists for people; the scan found nothing an agent could use. An MCP server is the fix Ora values most, at about 4.6 points.

## Test your own site

Run the same scan on your own domain at [ora.ai](https://ora.ai/?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check). The score, the layers and the fixes on this page come from its public result for apple.com; a scan of a public site takes a few minutes and needs no account.

-   [Scan your domain on Ora](https://ora.ai/?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check)The same checks, the same scoring, on your own site.
-   [The self-check, 18 questions](https://amireadyforagents.com/self-check)What to ask for, in business terms, before the scan.
-   [All the 360 checks](https://amireadyforagents.com/blog)The other companies in this series, newest first.

## Sources

1.  [Ora report for apple.com](https://ora.ai/score/apple.com?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check) (ora.ai/score/apple.com), read 9 Nov 2026. Vendor claim.

Last reviewed 9 November 2026

Reviewed 9 November 2026. [1 source](#sources), each with the day it was read.
