Centene: 50 of 100 on Ora's agent-readiness scan
In short
Centene scores 50 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. Six agents in and a developer portal with sign-in, on a home page without JSON-LD.
The score
Centene is a managed care company based in St. Louis, focused on Medicaid and marketplace plans.
- 50of 100, grade COra's agent-readiness scan of centene.com, read 9 November 2026.
- 10Discovery, of 16Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 28Access, of 57Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 22Usability, of 49Whether 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: Centene.com offers developer resource discoverability, 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 | Pass, 2 of 2 | Site accessible to 6 AI agent user-agents |
| Agent crawler reachability | Pass, 2 of 2 | Reachable to all major AI crawlers - ChatGPT-User: reachable, ClaudeBot: reachable, Google-Extended: reachable, ora-agent: reachable, DeepSeekBot: reachable |
| robots.txt AI crawler policy | Pass, 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 | Pass, 2 of 3 | 2861 chars with H1 but flat heading structure |
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 | The llms.txt is only 43 characters of content. |
| 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 | 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 | Pass, 2 of 2 | Valid sitemap found at https://www.centene.com/.sitemap.xml with 212 entries |
| Metadata completeness | Pass, 2 of 2 | All metadata signals present: canonical URL, lang="en-US", og:image, og:type |
| Page token budget | Pass, 1 of 1 | All 6 measured pages 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 | Partial, 1 of 2 | MCP server at https://docs.centene.com/mcp - consider adding /.well-known/mcp for standard discovery |
| Public API with reachable endpoints | Partial, 3 of 7 | API described in documentation at https://developer.centene.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.centene.com |
| OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found |
| Developer portal | Pass, 6 of 6 | Developer documentation portal found at https://developer.centene.com |
| OAuth 2.0 support | Pass, 5 of 5 | OpenID Connect discovery endpoint found at https://sso.centene.com |
| 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 2 | No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found (scanned 8 of 8 same-origin script bundle(s) for modelContext registrations) |
| Check | Result | What Ora saw |
|---|---|---|
| Wikipedia / Wikidata entity presence | Pass, 4 of 4 | Wikipedia "Centene Corporation" and Wikidata Q5059102 both verified - domain confirmed on both sources |
| Brand name discoverability | Partial, 1 of 3 | centene.com appears once in brand-name search results for "Centene Corporation" (position #4 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 | Pass, 4 of 6 | Agent found developer resources by name including developer portal (2 relevant pages). Not searchable: MCP server. Not found via search: API docs, OpenAPI spec, auth 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.
- MCP server / manifest, worth about 5.4 points by Ora's estimate: No MCP server or manifest found.
- Scoped permissions, worth about 4.5 points by Ora's estimate: No declared OAuth scopes, security schemes, or scoped-permission documentation found.
- OpenAPI spec published, worth about 4.1 points by Ora's estimate: No OpenAPI/Swagger specification found.
Our read
Centene's site is open to six AI agent user agents, with a robots.txt that allows every crawler and states no tier for the AI ones, and a home page that gives 2,861 characters under an H1 in a flat heading structure; the sitemap lists 212 pages and the metadata is complete, but there is no JSON-LD and no llms.txt, so the Access layer reads 28 of 57. The act layer is half built, which for a Medicaid insurer is half more than most: developer.centene.com is a real portal with documentation and OpenID Connect discovery sits at sso.centene.com, though the API it describes has no machine-verifiable surface and Ora found neither an OpenAPI specification nor an MCP server, and no declared scopes, so the Usability layer reads 22 of 49. The domain appears once, in fourth place, in a search for Centene Corporation, while Wikipedia and Wikidata both confirm it. An MCP server is the fix Ora values most, at about 5.4 points; an Organization block is the cheaper 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 centene.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 centene.com (ora.ai/score/centene.com), read 9 Nov 2026. Vendor claim.
Last reviewed