Humana: 33 of 100 on Ora's agent-readiness scan
In short
Humana scores 33 of 100 on Ora's agent-readiness scan, grade D, read on 9 November 2026. 25 percent of the 132,085 domains Ora ranks score under 30, and the average score is 44. A front door that did not open, over a developer portal with live OAuth.
The score
Humana is a health insurer based in Louisville, Kentucky, focused on Medicare Advantage.
- 33of 100, grade DOra's agent-readiness scan of humana.com, read 9 November 2026.
- 10Discovery, of 12Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 10Access, of 48Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 8Usability, of 46Whether 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.
25 percent of the 132,085 domains Ora ranks score under 30, and the average score is 44.
Ora's one-line summary: Humana offers developer portal and OAuth 2.0 support, but lacks an OpenAPI specification.
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 | error, 0 of 2 | Could not test bot user agents |
| Agent crawler reachability | Did not apply, 0 of 2 | Can't verify crawler reachability. A bot shield, rate limit, or timeout stopped our test request. Real crawlers come from their own networks and may get through. |
| robots.txt AI crawler policy | Did not apply, 0 of 2 | Cannot verify robots.txt permission for search crawlers: fetch unavailable |
| robots.txt agent-user policy | Did not apply, 0 of 2 | Cannot verify robots.txt permission for user-triggered agents: fetch unavailable |
| Content without JavaScript | error, 0 of 3 | Could not fetch homepage |
| Homepage not hidden from search | Did not apply, 0 of 1 | Homepage not read - cannot tell whether it is hidden 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://developers.humana.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 | error, 0 of 1 | Could not fetch with Accept: text/markdown |
| 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 | 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 | Partial, 1 of 2 | Only 1/4 metadata signals present - missing: canonical URL, og:image, og:type |
| 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 | Partial, 3 of 7 | API described in documentation at https://developers.humana.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://developers.humana.com |
| OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found |
| Developer portal | Pass, 6 of 6 | Developer portal found at https://developers.humana.com |
| OAuth 2.0 support | Pass, 5 of 5 | OAuth endpoint found at https://auth.humana.com/oauth/authorize |
| 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 |
| Check | Result | What Ora saw |
|---|---|---|
| Wikipedia / Wikidata entity presence | Pass, 4 of 4 | Wikipedia "Humana" and Wikidata Q910866 both verified - domain confirmed on both sources |
| Brand name discoverability | Pass, 3 of 3 | humana.com ranks #1 for "humana" (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 (developer portal) 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.
- MCP server / manifest, worth about 5.8 points by Ora's estimate: No MCP server or manifest found.
- OpenAPI spec published, worth about 4.9 points by Ora's estimate: No OpenAPI/Swagger specification found.
- Scoped permissions, worth about 4.8 points by Ora's estimate: No declared OAuth scopes, security schemes, or scoped-permission documentation found.
Our read
Humana's home page did not come back to the scan at all. A bot shield, rate limit or timeout stopped the test request, so the bot test could not run and the door, content, structured-data and metadata rows are unverified rather than failed; there is no sitemap, and the llms.txt at developers.humana.com/.well-known/llms.txt returns an HTML page, so the Access layer reads 10 of 48. The act layer is the better half: developers.humana.com is a real portal with documentation, and an OAuth endpoint answers at auth.humana.com/oauth/authorize, which puts the insurer ahead of most of this series on sign-in; the API has no verifiable surface, and Ora found neither an OpenAPI specification nor an MCP server, and no declared scopes, so the Usability layer reads 8 of 46. The Discovery layer is 10 of 12, with humana.com first for humana and Wikipedia and Wikidata confirmed. An insurer whose members ask assistants about their plans has a portal with sign-in and a front door that did not open; the front door is the row to fix.
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 humana.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 humana.com (ora.ai/score/humana.com), read 9 Nov 2026. Vendor claim.
Last reviewed