--- title: "Wells Fargo: 61 of 100 on Ora's scan | Am I Ready for Agents?" description: "Wells Fargo scores 61 of 100 on Ora's agent-readiness scan, grade C, read 9 Nov 2026. A bank within reach of a B, held back by two files that answer in HTML." canonical: https://amireadyforagents.com/blog/wells-fargo-agent-readiness site: "Am I Ready for Agents?" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # Wells Fargo: 61 of 100 on Ora's scan | Am I Ready for Agents? > Wells Fargo scores 61 of 100 on Ora's agent-readiness scan, grade C, read 9 Nov 2026. A bank within reach of a B, held back by two files that answer in HTML. Source: https://amireadyforagents.com/blog/wells-fargo-agent-readiness Site: Am I Ready for Agents? Last reviewed: 2026-11-09 # Wells Fargo: 61 of 100 on Ora's agent-readiness scan ## In short Wells Fargo scores 61 of 100 on Ora's agent-readiness scan, grade C, read on 9 November 2026. 79 percent of the 132,085 domains Ora ranks score under 60, and the average score is 44. A bank within reach of a B, held back by two files that answer in HTML. ## The score Wells Fargo is a bank based in San Francisco. - 61of 100, grade C Ora's agent-readiness scan of wellsfargo.com, read 9 November 2026, listed under Marketing. - 11Discovery, of 13 Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues. - 35Access, of 57 Whether they can read it: the door, text without JavaScript, llms.txt, structured data. - 32Usability, 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. 79 percent of the 132,085 domains Ora ranks score under 60, and the average score is 44. Ora's one-line summary: Wells Fargo 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 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://wellsfargo.com/. Declared policy only; | | Content without JavaScript | Partial, 2 of 3 | 9762 chars with H1, but first content heading is H2, not H1 | | 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 | Partial, 0 of 1 | A file is present at https://developer.wellsfargo.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 | 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 | Partial, 3 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.wellsfargo.com/seo-sitemap/wellsfargositemap_index.xml with multiple sitemaps 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 5 measured pages fit an agent context budget (largest ~2K tokens) | | Check | Result | What Ora saw | | --- | --- | --- | | MCP server / manifest | Partial, 2 of 6 | /.well-known/mcp/manifest.json serves an HTML page, not an MCP endpoint | | 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.wellsfargo.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.wellsfargo.com | | OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found | | Developer portal | Pass, 6 of 6 | Developer portal found at https://developer.wellsfargo.com | | OAuth 2.0 support | Pass, 5 of 5 | OpenID Connect discovery endpoint found at https://wellsfargo.com | | 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 (scanned 4 of 4 same-origin script bundle(s) for modelContext registrations) | | Check | Result | What Ora saw | | --- | --- | --- | | Wikipedia / Wikidata entity presence | Partial, 2 of 4 | Wikidata Q744149 (Wells Fargo) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage | | Brand name discoverability | Pass, 3 of 3 | wellsfargo.com ranks #1 for "Wells Fargo Bank – Branch & Online Banking Services Commercial" | | 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 2 developer-resource types by name (developer portal, API docs) across 5 pages | 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.1 points by Ora's estimate: No OpenAPI/Swagger specification found. 2. Scoped permissions, worth about 3.5 points by Ora's estimate: No declared OAuth scopes, security schemes, or scoped-permission documentation found. 3. WebMCP support, worth about 3.5 points by Ora's estimate: No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found (scanned 4 of 4 same-origin script bundle(s) for modelContext registrations). ## Our read Wells Fargo reads well and has built most of the act layer, with two files that answer in the wrong format. All four agent user agents reach wellsfargo.com, robots.txt allows the search and training crawlers, the home page gives 9,762 characters with an H1, four of four sampled pages read, the sitemap index is valid, the metadata is complete and the Organization block lacks only its description, so the Access layer reads 35 of 57; the llms.txt at developer.wellsfargo.com/.well-known/llms.txt returns an HTML page. The act layer is developer.wellsfargo.com with documentation, OpenID Connect discovery on the main domain, and an MCP manifest path at /.well-known/mcp/manifest.json that serves an HTML page rather than an endpoint; the API has no machine-verifiable surface, and there is no OpenAPI specification, no declared scopes and no SDK, so the Usability layer reads 32 of 64. Two files served as text and JSON rather than HTML would put this bank within reach of a B. ## 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 wellsfargo.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 wellsfargo.com](https://ora.ai/score/wellsfargo.com?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check) (ora.ai/score/wellsfargo.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.