--- title: "JPMorgan Chase: 35 of 100 on Ora's scan | Am I Ready for Agents?" description: "JPMorgan Chase scores 35 of 100 on Ora's agent-readiness scan, grade D, read 9 Nov 2026. Three fixes for the web team and the editors' read." canonical: https://amireadyforagents.com/blog/jpmorgan-chase-agent-readiness site: "Am I Ready for Agents?" last_updated: 2026-11-09 date: 2026-11-09 section: "360 checks" --- # JPMorgan Chase: 35 of 100 on Ora's scan | Am I Ready for Agents? > JPMorgan Chase scores 35 of 100 on Ora's agent-readiness scan, grade D, read 9 Nov 2026. Three fixes for the web team and the editors' read. Source: https://amireadyforagents.com/blog/jpmorgan-chase-agent-readiness Site: Am I Ready for Agents? Last reviewed: 2026-11-09 # JPMorgan Chase: 35 of 100 on Ora's agent-readiness scan ## In short JPMorgan Chase scores 35 of 100 on Ora's agent-readiness scan, grade D, read on 9 November 2026. 25 percent of the 132,085 domains Ora ranks score under 30, and the average score is 44. Readable and open, with no Wikipedia or Wikidata entry pointing at its own domain. ## 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. | 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, 2 of 2 | Training: 2/2. Search: 3/3 page/crawler pairs permitted. No applicable crawl or usage restriction found for 5 training and search crawlers (gptbot, claudebot, oai-searchbot, claude-searchbot). | | 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://jpmorganchase.com/. Declared policy only; | | Content without JavaScript | Partial, 2 of 3 | 4561 chars with H1, but first content heading is H2, not H1 | ## 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 | 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.jpmorganchase.com/sitemap.xml with 2247 entries | | Metadata completeness | Partial, 1 of 2 | 3/4 metadata signals present - missing: og:image | | Page token budget | Pass, 1 of 1 | All 6 measured pages fit an agent context budget (largest ~2K tokens) | | 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 | Fail, 0 of 7 | No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated) | | Public API/docs linked from homepage | Partial, 1 of 3 | Documentation found at /api but not linked from homepage | | OpenAPI spec published | Fail, 0 of 7 | No OpenAPI/Swagger specification found | | Developer portal | Did not apply, 0 of 6 | No developer portal found | | OAuth 2.0 support | Pass, 5 of 5 | OpenID Connect discovery endpoint found at https://identity.jpmorganchase.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 | SDK package found only in npm | | CLI tool available | Did not apply, 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 3 of 3 same-origin script bundle(s) for modelContext registrations) | | Check | Result | What Ora saw | | --- | --- | --- | | Wikipedia / Wikidata entity presence | Fail, 0 of 4 | No Wikipedia article or Wikidata entity found for "jpmorganchase" - creating a Wikipedia page and a Wikidata item with P856 = jpmorganchase.com is the highest-impact step for AI search citation coverage | | Brand name discoverability | Partial, 1 of 3 | jpmorganchase.com appears once in brand-name search results for "JPMorganChase" (position #5 out of 9) | | 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 | Fail, 0 of 3 | Agent searched for "jpmorganchase" developer resources but found nothing relevant | 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](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 jpmorganchase.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 jpmorganchase.com](https://ora.ai/score/jpmorganchase.com?utm_source=amireadyforagents.com&utm_medium=referral&utm_campaign=check) (ora.ai/score/jpmorganchase.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.