--- title: "FedEx: 42 of 100 on Ora's scan | Am I Ready for Agents?" description: "FedEx scores 42 of 100 on Ora's agent-readiness scan, grade D, read 9 Nov 2026. Every agent in, 314 characters of home page, and a portal the shield hides." canonical: https://amireadyforagents.com/blog/fedex-agent-readiness site: "Am I Ready for Agents?" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # FedEx: 42 of 100 on Ora's scan | Am I Ready for Agents? > FedEx scores 42 of 100 on Ora's agent-readiness scan, grade D, read 9 Nov 2026. Every agent in, 314 characters of home page, and a portal the shield hides. Source: https://amireadyforagents.com/blog/fedex-agent-readiness Site: Am I Ready for Agents? Last reviewed: 2026-11-09 # FedEx: 42 of 100 on Ora's agent-readiness scan ## In short FedEx scores 42 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. Every agent in, 314 characters of home page, and a portal the shield hides. ## The score FedEx is an express delivery and logistics company based in Memphis. - 42of 100, grade D Ora's agent-readiness scan of fedex.com, read 9 November 2026. - 13Discovery, of 14 Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues. - 19Access, of 48 Whether they can read it: the door, text without JavaScript, llms.txt, structured data. - 7Usability, of 37 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. Ora's one-line summary: Gives agents almost nothing to work with: no MCP server, no scoped permissions and no WebMCP 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 | 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://fedex.com/. Declared policy only; | | Content without JavaScript | Partial, 1 of 3 | Homepage: Only 314 chars of text content, no H1 tag - agents see limited content. No inner pages checked: the scan found none to sample. | | 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 | Partial, 0 of 1 | A file is present at https://fedex.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 (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 | Fail, 0 of 4 | No JSON-LD structured data found on homepage | | Organization schema completeness | Fail, 0 of 2 | No JSON-LD found - Organization schema missing | | Sitemap exists | Fail, 0 of 2 | No sitemap found | | Metadata completeness | Fail, 0 of 2 | No metadata signals found - missing: canonical URL, HTML lang attribute, og:image, og:type | | Page token budget | Pass, 1 of 1 | All 1 measured page fit an agent context budget (largest ~1K 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.fedex.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.fedex.com | | OpenAPI spec published | Did not apply, 0 of 7 | Can't verify: a bot shield answered our request to developer.fedex.com/openapi (HTTP 403) instead of the site. That is not counted against the site. | | Developer portal | Pass, 6 of 6 | Developer documentation portal found at https://developer.fedex.com | | OAuth 2.0 support | Did not apply, 0 of 5 | Can't verify: a bot shield answered our request to auth.fedex.com/.well-known/openid-configuration (HTTP 403); auth.fedex.com/.well-known/oauth-authorization-server (HTTP 403) instead of the site. | | Scoped permissions | Fail, 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found | | Multi-language SDK packages | Did not apply, 0 of 3 | No SDK packages found across language ecosystems | | CLI tool available | Did not apply, 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 "FedEx" and Wikidata Q459477 both verified - domain confirmed on both sources | | Brand name discoverability | Pass, 3 of 3 | fedex.com ranks #4 for "FedEx" (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 #2 (https://developer.fedex.com/api/en-hn/guides/best-practices.html) | 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 7.2 points by Ora's estimate: No MCP server or manifest found. 2. Scoped permissions, worth about 6 points by Ora's estimate: No declared OAuth scopes, security schemes, or scoped-permission documentation found. 3. WebMCP support, worth about 6 points by Ora's estimate: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found. ## Our read FedEx lets every agent in and shows it 314 characters. All four agent user agents reach fedex.com and robots.txt allows the search and training crawlers, and there the good news ends: the home page renders 314 characters without an H1, the scan found no inner page to sample, there is no JSON-LD and no sitemap, the metadata carries none of its four signals, and the llms.txt at /.well-known/llms.txt returns an HTML page, so the Access layer reads 19 of 48. The Discovery layer is nearly full at 13 of 14. The act layer is developer.fedex.com, a real portal whose API has no machine-verifiable surface; a bot shield answered the OpenAPI and OpenID Connect probes with 403, not counted against the site, and Ora found no MCP server and no declared scopes, so the Usability layer reads 7 of 37. A company that tracks every parcel has a home page that tells an agent almost nothing; an MCP server is the fix Ora values most, at 7.2 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 fedex.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 fedex.com](https://ora.ai/score/fedex.com?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check) (ora.ai/score/fedex.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.