Wells Fargo: 61 of 100 on Ora's agent-readiness scan

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.

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.

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. 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 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.