JPMorgan Chase: 35 of 100 on Ora's agent-readiness scan

The score

JPMorgan Chase is the largest bank in the United States by assets, based in New York.

• 35of 100, grade D
  Ora's agent-readiness scan of jpmorganchase.com, read 9 November 2026.
• 4Discovery, of 10
  Whether assistants find the company: search presence, Wikipedia and Wikidata, catalogues.
• 18Access, of 50
  Whether they can read it: the door, text without JavaScript, llms.txt, structured data.
• 16Usability, of 50
  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.

25 percent of the 132,085 domains Ora ranks score under 30, and the average score is 44.

Ora's one-line summary: JPMorgan Chase has a robots.txt AI crawler policy, 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. Developer resource discoverability, worth about 6.7 points by Ora's estimate: Agent searched for "jpmorganchase" developer resources but found nothing relevant.
2. Public API with reachable endpoints, worth about 6.2 points by Ora's estimate: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated).
3. MCP server / manifest, worth about 5.3 points by Ora's estimate: No MCP server or manifest found.

Our read

JPMorgan Chase opens the door and reads well, then hides its own name. Six AI agent user agents get in, robots.txt permits every pair Ora checked, the home page gives 4,561 characters with an H1 and the sitemap lists 2,247 pages; there is no JSON-LD and no llms.txt, so the Access layer reads 18 of 50. The act layer is partly built: documentation sits at /api without a link from the home page, OpenID Connect discovery answers at identity.jpmorganchase.com and an SDK sits on npm, but there is no publicly reachable API, no developer portal, and neither an OpenAPI specification nor an MCP server, so the Usability layer reads 16 of 50. The Discovery layer is 4 of 10: the domain appears once, fifth of nine, in a search for JPMorganChase, and no Wikipedia article or Wikidata item points at it. The largest bank in the United States is, to the knowledge graph, a domain without an entity; an Organization block with a sameAs link is the 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 jpmorganchase.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.