--- title: "Lockheed Martin: 40 of 100 on Ora's scan | Am I Ready for Agents?" description: "Lockheed Martin scores 40 of 100 on Ora's agent-readiness scan, grade D, read 9 Nov 2026. Two JSON files that will not parse, one of them an MCP manifest." canonical: https://amireadyforagents.com/blog/lockheed-martin-agent-readiness site: "Am I Ready for Agents?" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # Lockheed Martin: 40 of 100 on Ora's scan | Am I Ready for Agents? > Lockheed Martin scores 40 of 100 on Ora's agent-readiness scan, grade D, read 9 Nov 2026. Two JSON files that will not parse, one of them an MCP manifest. Source: https://amireadyforagents.com/blog/lockheed-martin-agent-readiness Site: Am I Ready for Agents? Last reviewed: 2026-11-09 # Lockheed Martin: 40 of 100 on Ora's agent-readiness scan ## In short Lockheed Martin scores 40 of 100 on Ora's agent-readiness scan, grade D, read on 9 November 2026. 43 percent of the 132,085 domains Ora ranks score under 40, and the average score is 44. Two JSON files that will not parse, one of them an MCP manifest. ## The score Lockheed Martin is a defence and aerospace manufacturer based in Bethesda, Maryland. - 40of 100, grade D Ora's agent-readiness scan of lockheedmartin.com, read 9 November 2026. - 3Discovery, of 10 Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues. - 29Access, of 59 Whether they can read it: the door, text without JavaScript, llms.txt, structured data. - 22Usability, of 57 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. 43 percent of the 132,085 domains Ora ranks score under 40, and the average score is 44. ## 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, 1 of 2 | Some agents blocked: GPTBot, ChatGPT-User | | Agent crawler reachability | Partial, 0 of 2 | Some AI crawlers are blocked - ChatGPT-User: blocked, ClaudeBot: reachable, Google-Extended: reachable, ora-agent: reachable, DeepSeekBot: reachable | | robots.txt AI crawler policy | Partial, 1 of 2 | robots.txt allows all crawlers (e.g. User-agent: * + Allow: /) - open by default but declares no AI-crawler tier differentiation | | robots.txt agent-user policy | Pass, 2 of 2 | No robots.txt restriction on user-triggered agents - they can read the site | | Content without JavaScript | Partial, 2 of 3 | 1549 chars with H1, but 4.0% content ratio is below the 5% target | ## 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 | Partial, 0 of 1 | A file is present at https://lockheedmartin.com/.well-known/llms.txt, but it returns an HTML page rather than a plain-text 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 (GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended, ora-agent, DeepSeekBot) receives markdown when requesting HTML. | | JSON-LD structured data | Partial, 1 of 4 | JSON-LD blocks found but contain invalid JSON | | Organization schema completeness | Fail, 0 of 2 | No Organization type found in JSON-LD | | Sitemap exists | Pass, 2 of 2 | Valid sitemap found at https://www.lockheedmartin.com/sitemap-en-us.xml with 2075 entries | | Metadata completeness | Pass, 2 of 2 | All metadata signals present: canonical URL, lang="en", og:image, og:type | | Page token budget | Pass, 1 of 1 | All 6 measured pages fit an agent context budget (largest ~2K tokens) | | Check | Result | What Ora saw | | --- | --- | --- | | MCP server / manifest | Partial, 2 of 6 | MCP endpoint found at /.well-known/mcp/manifest.json but response is not valid JSON | | MCP well-known discovery | Fail, 0 of 2 | No MCP server URL discovered | | Public API with reachable endpoints | Fail, 0 of 7 | No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated) | | Public API/docs linked from homepage | Partial, 1 of 3 | Documentation found at /api but not linked from homepage | | OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found | | Developer portal | Pass, 6 of 6 | Developer portal found at /console | | OAuth 2.0 support | Pass, 5 of 5 | OpenID Connect discovery endpoint found at https://lockheedmartin.com | | Scoped permissions | Fail, 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found | | Multi-language SDK packages | Fail, 0 of 3 | No SDK packages found across language ecosystems | | CLI tool available | Fail, 0 of 3 | No CLI tool found | | WebMCP support | Fail, 0 of 5 | No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found (scanned 2 of 2 same-origin script bundle(s) for modelContext registrations) | | Check | Result | What Ora saw | | --- | --- | --- | | Wikipedia / Wikidata entity presence | Fail, 0 of 4 | No Wikipedia article or Wikidata entity found for "lockheedmartin" - creating a Wikipedia page and a Wikidata item with P856 = lockheedmartin.com is the highest-impact step for AI search citation coverage | | Brand name discoverability | Partial, 1 of 3 | lockheedmartin.com appears once in brand-name search results for "Lockheed Martin" (position #6 out of 6) | | 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 | Partial, 1 of 3 | Agent struggled to find developer resources by name - only 1 result(s) out of 9. Not found in this search sample: API docs, OpenAPI spec, developer portal, auth docs, MCP server, SDK 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. Public API with reachable endpoints, worth about 5.5 points by Ora's estimate: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated). 2. Developer resource discoverability, worth about 4.4 points by Ora's estimate: Agent struggled to find developer resources by name - only 1 result(s) out of 9. Not found in this search sample: API docs, OpenAPI spec, developer portal, auth docs, MCP server, SDK documentation. 3. Brand name discoverability, worth about 4.4 points by Ora's estimate: lockheedmartin.com appears once in brand-name search results for "Lockheed Martin" (position #6 out of 6). ## Our read Lockheed Martin has built more of the act layer than its D shows. ClaudeBot and Google-Extended get in while GPTBot and ChatGPT-User are blocked, robots.txt allows every crawler, the home page gives 1,549 characters with an H1 at a 4 percent text ratio, the sitemap lists 2,075 pages and the metadata is complete, so the Access layer reads 29 of 59; the JSON-LD blocks contain invalid JSON, and the llms.txt at /.well-known/llms.txt returns an HTML page. Behind that sit a portal at /console, documentation at /api, OpenID Connect discovery, and an MCP manifest at /.well-known/mcp/manifest.json that answers in something other than valid JSON; there is no reachable public API and no OpenAPI specification, so the Usability layer reads 22 of 57. The Discovery layer is 3 of 10: the domain appears once, last of six, in a search for its own name, and no Wikipedia article or Wikidata item points at it. Two broken JSON files, the structured data and the MCP manifest, are the cheapest points on this page. ## 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 lockheedmartin.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 lockheedmartin.com](https://ora.ai/score/lockheedmartin.com?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check) (ora.ai/score/lockheedmartin.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.