Two acts, in U.S. Bank blue. Act 1: an assistant answers a card question with cited, structured data, never an invented rate. Act 2: an environmental-finance dollar becomes a settled, proof-verified receipt on Base. Both run on patterns your own arms already touch.
the problem, from Finding 2 The credit-cards page renders 0 ld+json, so today an assistant has no structured terms to read: it guesses, or hands the customer a number that isn't U.S. Bank's. Here's the same question once a consumer llms.txt + FinancialProduct schema exists (the pattern Elavon already runs):
usbank.com/llms.txt → FinancialProduct#cash-plus. Every figure links back to U.S. Bank's own terms page: the assistant never invents a rate.The difference: the answer is U.S. Bank's, cited to U.S. Bank, so the customer who came asking for U.S. Bank gets U.S. Bank's real terms, instead of a hallucinated number or someone else's feed. Same products; now legible.
the opportunity, from Finding 1 & 4 The $50B environmental-finance commitment lives in a PDF the ESG page can't even expose as structured data. EcoWealth's protocol turns one funded dollar into a proof-of-outcome receipt: photo + GPS + method-backed tCO₂e, settled on Base, the same substrate your custody business already touches.
Why it lands now: with the SEC climate rule receding to a voluntary regime, an independently-checkable outcome is worth more than a self-reported one. U.S. Bank was selected to provide custody for payment-stablecoin reserves (Anchorage Digital, 2025), the same on-chain substrate, here pointed at proof-of-outcome. A layer added to what you already run.
noindex.