Tesla: 25 of 100 on Ora's agent-readiness scan
In short
Tesla scores 25 of 100 on Ora's agent-readiness scan, grade F, read on 9 November 2026. 9 percent of the 132,085 domains Ora ranks score under 20, and the average score is 44. A 403 for every agent at the carmaker that sells software over the air.
The score
Tesla is an electric carmaker and energy storage company based in Austin, Texas.
- 25of 100, grade FOra's agent-readiness scan of tesla.com, read 9 November 2026.
- 10Discovery, of 12Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 0Access, of 50Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 8Usability, of 58Whether 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: Tesla blocks agents at the homepage with security challenges and provides no OpenAPI spec, developer portal, or OAuth 2.0 support.
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 | Partial, 0 of 2 | Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot. A challenge is an identity check that verified crawlers pass. |
| Agent crawler reachability | Partial, 0 of 2 | Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot - a challenge is an identity check verified crawlers pass, so reachability is undetermined rather than blocked (ChatGPT-User: challenged). |
| robots.txt AI crawler policy | Did not apply, 0 of 2 | Cannot verify robots.txt permission for search crawlers: WAF/bot challenge (HTTP 403) |
| robots.txt agent-user policy | Did not apply, 0 of 2 | Cannot verify robots.txt permission for user-triggered agents: WAF/bot challenge (HTTP 403) |
| Content without JavaScript | Partial, 0 of 3 | Homepage blocked by WAF/security challenge - content not accessible to agents |
| Homepage not hidden from search | Did not apply, 0 of 1 | Homepage blocked by WAF - cannot read its indexing directives |
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 | Did not apply, 0 of 1 | Site is behind a WAF/bot wall - cannot probe bot-UA serving |
| JSON-LD structured data | Partial, 0 of 4 | Homepage blocked by WAF - cannot check structured data |
| Organization schema completeness | Partial, 0 of 2 | Homepage blocked by WAF - cannot check Organization schema |
| Sitemap exists | Fail, 0 of 2 | No sitemap found |
| Metadata completeness | Partial, 0 of 2 | Homepage blocked by WAF - cannot check metadata |
| Page token budget | Did not apply, 0 of 1 | Nothing sampled to measure |
| 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 | Pass, 7 of 7 | GraphQL endpoint at https://tesla.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 | Partial, 0 of 3 | Homepage blocked by WAF - cannot check for docs links |
| OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found |
| Developer portal | Fail, 0 of 6 | 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 |
| Multi-language SDK packages | Partial, 1 of 3 | SDK package found only in rubygems |
| 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 |
| Check | Result | What Ora saw |
|---|---|---|
| Wikipedia / Wikidata entity presence | Pass, 4 of 4 | Wikipedia "Tesla Cybertruck" and Wikidata Q478214 both verified - domain confirmed on both sources |
| Brand name discoverability | Pass, 3 of 3 | tesla.com ranks #3 for "tesla" (searched your brand name alone: we could not read a product term from your site) |
| 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 | Agent discovered 1 developer-resource type by name (auth docs) across 1 page |
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 4.7 points by Ora's estimate: No OpenAPI/Swagger specification found.
- MCP server / manifest, worth about 4.6 points by Ora's estimate: No MCP server or manifest found.
- Developer portal, worth about 4 points by Ora's estimate: No developer portal found.
Our read
Tesla challenges every agent and publishes almost nothing for the ones that get past. Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User and PerplexityBot, robots.txt answered with a 403 challenge and the home page came back as a security page, so the door, content, policy, structured-data and metadata rows are unverified rather than failed, and the Access layer reads 0 of 50; there is no sitemap and no llms.txt. The act layer is a GraphQL endpoint at tesla.com/graphql with introspection gated and an SDK on RubyGems, and nothing else: no developer portal, no OpenAPI specification, and neither an MCP server nor OAuth discovery, so the Usability layer reads 8 of 58. The Discovery layer is 10 of 12, with tesla.com third for tesla and Wikipedia confirming the company by way of the Cybertruck article. A carmaker that sells software updates over the air has a web site that treats an assistant as an intruder; the F is the challenge, and the challenge is a setting.
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 tesla.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 tesla.com (ora.ai/score/tesla.com), read 9 Nov 2026. Vendor claim.
Last reviewed