AI is becoming the front door to banking. This is where legible, proof-backed data plugs into Chase.

One agent-legibility layer → you win the AI's first pass at “which Chase card fits me?” instead of losing the shopper to a vague answer

A rising share of “which card,” “help me open an account,” and “is Chase's climate claim real” gets a first look from an assistant before a human — and today it reads four separately-built stacks with no machine profile; one legible layer (the pattern your Payments org already runs) means the customer already asking gets an accurate answer and reaches you.

A verifiable receipt under the $2.5T commitment → a number an AI can check, not a PDF it can't

Your climate substance is real but arrives as PDFs nothing can independently verify; a settled, proof-backed outcome receipt turns the headline into citable ground truth — worth more to a skeptical regulator, customer, or their AI than a figure they can only take on faith.

Prune the legacy crawl rules → the first thing an AI indexer reads on your consumer domain is clean

The consumer robots file still mixes modern sitemaps with a decade of BlackBerry-era, Flash-era cruft; a quick cleanup is cheap discovery hygiene that shapes how every machine — search or AI — first sees Chase.

1The consumer surface is spread across four independently-built stacks301 chain + CSP

The single brand "chase.com" fans out to at least four separate properties. Credit cards live on creditcards.chase.com, a Capgemini-operated build (its live CSP allowlists creditcards_capgemini_com and capgeminijpmc.tt.omtrdc.net). Checking lives on personal.chase.com. Corporate + ESG lives on jpmorganchase.com. Each has its own chrome, nav, and blue.

# curl -IL (redirect chains, normal browsing)
www.chase.com/personal/credit-cards  301 →  creditcards.chase.com/        (Capgemini stack)
www.chase.com/personal/checking      301 →  personal.chase.com/personal/checking
creditcards.chase.com CSP includes:  creditcards_capgemini_com, capgeminijpmc.tt.omtrdc.net
creditcards.chase.com CSP img-src allowlists ~40 third-party ad/analytics origins

Passive visit, 2× DPI: creditcards.chase.com renders as its own branded property: different masthead, brighter blue, separate nav, confirming the split stack.

Why it costs: a customer (or an AI) moving from "cards" to "checking" crosses independently-built systems: consistency, analytics, and machine-legibility all get harder. This is normal at Chase's scale; it's exactly the seam a single agent-legibility layer smooths over.

2Modern sitemaps, layered over a decade of legacy sedimentrobots.txt

www.chase.com/robots.txt layers dozens of accreted Disallow rules pointing at /online/… and /ccpmweb/… paths, including a BlackBerry-phone article, Flash .swf rules, and malformed trailing-dot typos, beneath 4 modern Sitemap: directives: current discovery hygiene sitting atop a decade of never-pruned legacy sediment. (jpmorganchase.com/robots.txt is leaner: targeted, no legacy cruft.)

# www.chase.com/robots.txt — excerpt (HTTP 200, 147 lines)
Disallow: /online/services/article/blackberry-phone.htm.   # trailing-dot typo, BlackBerry era
Disallow: /*swf*                                     # Flash
Disallow: /ccpmweb/shared/ …                              # dozens more legacy paths
Sitemap: https://www.chase.com/sitemap.xml              # + 3 more sitemaps present

# jpmorganchase.com/robots.txt — leaner, no legacy cruft
Sitemap: https://www.jpmorganchase.com/sitemap.xml

Why it costs: the first thing any crawler, including an AI indexer, reads on the consumer domain mixes valid modern sitemaps with a decade of never-pruned legacy cruft. Discovery hygiene, not a security issue, but it's the layer that shapes how machines see Chase.

3The consumer & corporate surfaces aren't AI-legible yet, but your Payments org already is200 vs 404

Every standard agent-discovery path 404s on the consumer and corporate domains: no llms.txt, no A2A agent card, no plugin manifest to tell an assistant how to represent Chase's products or claims. But this isn't an unproven idea at JPMorganChase: developer.payments.jpmorgan.com/llms.txt is live (200, 198 KB, 1,212 lines), backed by an LLM-markdown API and a "Build with AI" track. The pattern is validated in-house; it just hasn't reached the consumer product or sustainability front door.

# agent-discovery probes (public well-knowns), 2026-07-10
developer.payments.jpmorgan.com/llms.txt   200   # 198 KB · 1,212 lines — already live
www.chase.com/llms.txt                     404
jpmorganchase.com/llms.txt                 404
chase.com/.well-known/agent-card.json      404

Why it costs: "which card is best for me," "help me open an account," "is Chase's climate claim real": a rising share of these get a first pass from an AI before a human looks. Legible data wins that pass; a PDF doesn't get read. Extending the llms.txt pattern your Payments org already runs to the consumer and sustainability surfaces is low-risk first-mover, not an unproven bet.

4Real sustainable-finance substance, delivered as PDFs, with no outcome-proof layerfetch + probe

JPMorganChase's climate commitments are genuinely strong: a target to finance and facilitate $2.5 trillion in sustainable development through 2030 (with $1 trillion for green), the Center for Carbon Transition, the Carbon Compass® methodology, sector 2030 emission-intensity targets (Oil & Gas / Power / Auto from 2021; Iron & Steel / Cement / Aviation from 2022; Shipping / Aluminum from 2023), and a net-zero-aligned-by-2050 pathway. But it lives in the annual Sustainability Report PDF: no structured, project-level, agent-readable export, and no funded, proof-verified outcome layer beneath the financing number.

# jpmorganchase.com/impact/environmental-sustainability (HTTP 200)
commitments present:  $2.5T sustainable-dev · $1T green · net-zero 2050 · Carbon Compass®
delivery format:      PDF report links only, no API, no structured project-level data
outcome proof:        none machine-readable, financing figure, not verified ground-truth

Why it matters, and where EcoWealth fits: a $2.5T commitment is a number an AI can't verify and a PDF can't prove. EcoWealth's Work Protocol is the last mile: funded ecological/community work packets, each settled with photo + GPS + method proof and an on-chain tCO2e receipt an assistant can cite.