--- title: "Cencora: 43 of 100 on Ora's scan | Am I Ready for Agents?" description: "Cencora scores 43 of 100 on Ora's agent-readiness scan, grade D, read 9 Nov 2026. Three fixes for the web team and the editors' read." canonical: https://amireadyforagents.com/blog/cencora-agent-readiness site: "Am I Ready for Agents?" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # Cencora: 43 of 100 on Ora's scan | Am I Ready for Agents? > Cencora scores 43 of 100 on Ora's agent-readiness scan, grade D, read 9 Nov 2026. Three fixes for the web team and the editors' read. Source: https://amireadyforagents.com/blog/cencora-agent-readiness Site: Am I Ready for Agents? Last reviewed: 2026-11-09 # Cencora: 43 of 100 on Ora's agent-readiness scan ## In short Cencora scores 43 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. A well-built reading layer in front of an API that has no documentation at all. ## The score Cencora is a pharmaceutical distributor based in Pennsylvania, formerly AmerisourceBergen. - 43of 100, grade D Ora's agent-readiness scan of cencora.com, read 9 November 2026. - 8Discovery, of 14 Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues. - 26Access, of 48 Whether they can read it: the door, text without JavaScript, llms.txt, structured data. - 18Usability, of 64 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 | 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://cencora.com/. Declared policy only; | | Content without JavaScript | Pass, 3 of 3 | Homepage: 4638 chars, semantic headings (1 H1 + 9 H2s + 4 H3s), 10.0% content ratio. 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 | Pass, 1 of 1 | Found the llms.txt at https://cencora.com/llms.txt. | | llms.txt formatting | Partial, 1 of 2 | The llms.txt starts with a heading and has 97 lines, but it contains no markdown links. | | 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: contactPoint, address | | Sitemap exists | Pass, 2 of 2 | Valid sitemap found at https://www.cencora.com/sitemap.xml with 1192 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 | 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://api.cencora.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 3 | No public API or documentation page linked from homepage | | OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found | | Developer portal | Did not apply, 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 | 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 (scanned 4 of 4 same-origin script bundle(s) for modelContext registrations) | | Check | Result | What Ora saw | | --- | --- | --- | | Wikipedia / Wikidata entity presence | Pass, 4 of 4 | Wikipedia "Cencora" and Wikidata Q470156 both verified - domain confirmed on both sources | | Brand name discoverability | Partial, 1 of 3 | cencora.com ranks #9 for "Cencora, Inc." (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 | Fail, 0 of 3 | In a search for your API docs, none of the 10 results is your official docs | 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. OpenAPI spec published, worth about 4.9 points by Ora's estimate: No OpenAPI/Swagger specification found. 2. Developer resource discoverability, worth about 4.8 points by Ora's estimate: In a search for your API docs, none of the 10 results is your official docs. 3. MCP server / manifest, worth about 4.2 points by Ora's estimate: No MCP server or manifest found. ## Our read Cencora reads better than its D suggests. All four agent user agents get in, robots.txt allows the search and training crawlers, the home page gives 4,638 characters at a 10 percent text ratio under one H1 and nine H2s, five of five sampled pages read, the sitemap lists 1,192 pages, an llms.txt sits at cencora.com/llms.txt and the Organization block lacks only its description, so the Access layer reads 26 of 48. The grade is earned on the act layer: a GraphQL endpoint at api.cencora.com answers and gates introspection behind a key, which is normal, but there is neither a documentation page nor a developer portal, no OpenAPI specification, and no MCP server or OAuth discovery, so the Usability layer reads 18 of 64. The domain ranks ninth for its own corporate name, and a search for its API documentation returned none of its pages in ten results. A distributor that moves a large share of America's medicines has an API with no front door; an OpenAPI specification, about 4.9 points, would be it. ## 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 cencora.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 cencora.com](https://ora.ai/score/cencora.com?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check) (ora.ai/score/cencora.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.