Fannie Mae: 26 of 100 on Ora's agent-readiness scan
In short
Fannie Mae scores 26 of 100 on Ora's agent-readiness scan, grade F, read on 9 November 2026. 9 percent of the 132,085 domains Ora ranks score under 20, and the average score is 44. A challenge at the door and a Usability layer of 3 of 44 behind it.
The score
Fannie Mae is a government-sponsored mortgage company based in Washington, D.C.
- 26of 100, grade FOra's agent-readiness scan of fanniemae.com, read 9 November 2026.
- 8Discovery, of 12Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
- 12Access, of 49Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
- 3Usability, of 44Whether 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.
9 percent of the 132,085 domains Ora ranks score under 20, and the average score is 44.
Ora's one-line summary: Turns agents away at the door: bot protection blocks them and the homepage shows no content without JavaScript.
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 | Partial, 0 of 2 | Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot. A challenge is an identity check that verified crawlers pass. |
| Agent crawler reachability | Partial, 0 of 2 | Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot - a challenge is an identity check verified crawlers pass, so reachability is undetermined rather than blocked (ChatGPT-User: challenged). |
| 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://fanniemae.com/. Declared policy only; |
| Content without JavaScript | Partial, 0 of 3 | Homepage blocked by WAF/security challenge - content not accessible to agents |
| Homepage not hidden from search | Did not apply, 0 of 1 | Homepage blocked by WAF - cannot read its indexing directives |
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 | Did not apply, 0 of 1 | Site is behind a WAF/bot wall - cannot probe bot-UA serving |
| 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://developer.fanniemae.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.fanniemae.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.fanniemae.com |
| 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 | 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 document.modelContext / navigator.modelContext usage found |
| Check | Result | What Ora saw |
|---|---|---|
| Wikipedia / Wikidata entity presence | Partial, 2 of 4 | Wikidata Q621096 (Fannie Mae) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage |
| Brand name discoverability | Partial, 1 of 3 | fanniemae.com ranks #7 for "fanniemae" (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 | In a search for your API docs, your docs came up at #9 (https://developer.fanniemae.com) |
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 6.1 points by Ora's estimate: No MCP server or manifest found.
- OAuth 2.0 support, worth about 5.1 points by Ora's estimate: No OAuth 2.0 or OpenID Connect support detected.
- Scoped permissions, worth about 5.1 points by Ora's estimate: No declared OAuth scopes, security schemes, or scoped-permission documentation found.
Our read
Fannie Mae's door is a challenge and its reading layer is behind it. Bot management challenged ChatGPT-User, OAI-SearchBot, Claude-User and PerplexityBot and the home page came back as a security page, so the content, structured-data and metadata rows are unverified rather than failed; robots.txt itself did answer, and allows the search and training crawlers in every check. There is no sitemap and no llms.txt, and the Access layer reads 12 of 49. The act layer is a portal and little else: developer.fanniemae.com documents an API with no machine-verifiable surface, and Ora found neither an OpenAPI specification nor an MCP server, and no OAuth discovery, so the Usability layer reads 3 of 44, the lowest Usability score in this series. The domain ranks seventh for fanniemae, a search run on the bare name, and the API documentation came up ninth. A mortgage company whose data half the market depends on has a developer portal no agent can reach from the front; the shield is the first row.
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 fanniemae.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 fanniemae.com (ora.ai/score/fanniemae.com), read 9 Nov 2026. Vendor claim.
Last reviewed