Elevance Health: 56 of 100 on Ora's agent-readiness scan
In short
Elevance Health scores 56 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. A full home page whose canonical tag still points at a staging host.
The score
Elevance Health is a health insurer based in Indianapolis, formerly Anthem, operating Blue Cross Blue Shield plans in fourteen states.
- 56of 100, grade COra's agent-readiness scan of elevancehealth.com, read 9 November 2026.
- 11Discovery, of 12Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 31Access, of 49Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 8Usability, of 24Whether 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.
60 percent of the 132,085 domains Ora ranks score under 50, and the average score is 44.
Ora's one-line summary: Elevance Health offers strong brand and developer-resource discoverability, but lacks a published OpenAPI specification and a publicly reachable API surface for agents.
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://elevancehealth.com/. Declared policy only; |
| Content without JavaScript | Pass, 3 of 3 | Homepage: 4814 chars, semantic headings (2 H1 + 4 H2s + 1 H3s), 12.3% 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 | 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 | Pass, 2 of 2 | Organization schema complete with contactPoint and address |
| Sitemap exists | Pass, 2 of 2 | Valid sitemap found at https://www.elevancehealth.com/sitemap.xml with 775 entries |
| Metadata completeness | Partial, 1 of 2 | 3/4 metadata signals present - missing: canonical URL (the canonical names anthem-prod1.adobecqms.net, but the site redirects to www.elevancehealth.com) |
| 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 | Did not apply, 0 of 6 | Can't verify: a bot shield answered our request to elevancehealth.com/.well-known/mcp (HTTP 403); elevancehealth.com/mcp (HTTP 403); elevancehealth.com/mcp.json (HTTP 403) instead of the site. |
| 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 /developers 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 /developers |
| OAuth 2.0 support | Did not apply, 0 of 5 | No OAuth 2.0 or OpenID Connect support detected |
| Scoped permissions | Did not apply, 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 | Did not apply, 0 of 5 | Can't verify: a bot shield answered our request to elevancehealth.com/api-reference (HTTP 403) instead of the site. That is not counted against the site. |
| Check | Result | What Ora saw |
|---|---|---|
| Wikipedia / Wikidata entity presence | Partial, 2 of 4 | Wikidata Q677488 (Elevance Health, Inc.) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage |
| Brand name discoverability | Pass, 3 of 3 | elevancehealth.com ranks #4 for "anthem-prod1.adobecqms.net" (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 #4 (https://totalview.healthos.elevancehealth.com/fhir/documentation/supported-resources?value=allergyintolerance) |
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.
- Public API with reachable endpoints, worth about 13 points by Ora's estimate: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated).
- JSON error responses, worth about 7.4 points by Ora's estimate: API does not return JSON error responses (or no API detected).
- OpenAPI spec published, worth about 4.8 points by Ora's estimate: No OpenAPI/Swagger specification found.
Our read
Elevance Health has the best home page of the insurers read so far and little act layer behind it. All four agent user agents get in, robots.txt allows the crawlers, the home page gives 4,814 characters at a 12.3 percent text ratio, five of five sampled pages read, the sitemap lists 775 pages and the Organization block is complete with contact point and address, lacking only its description. There is no llms.txt, and the canonical tag names an Adobe staging host rather than the site, which is what the brand search then ran on. The Access layer reads 31 of 49. The act layer is a portal at /developers that the home page does not link to, with no publicly reachable API, neither an OpenAPI specification nor OAuth discovery, and an MCP probe answered by a bot shield, so the Usability layer reads 8 of 24. A canonical tag naming the real domain is a one-line fix; the public API Ora values at 13 points is the long one.
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 elevancehealth.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 elevancehealth.com (ora.ai/score/elevancehealth.com), read 9 Nov 2026. Vendor claim.
Last reviewed