ChatGPT's personal finance launch is not a consumer product story. For the IBM i operator, it is an infrastructure alert. The agentic traffic is coming. The question is whether your system is in a condition to receive it.
On May 15, 2026, OpenAI launched a personal finance experience inside ChatGPT. Pro users in the U.S. can now connect their bank accounts, credit cards, investment portfolios, and loan accounts to the chatbot via Plaid. More than 12,000 financial institutions are in scope — including the lending institutions, servicers, and specialty finance companies that run their core operations on IBM i.
Most IBM i practitioners will read that news as something happening to the consumer side of their organization. A product story. A fintech story. A ChatGPT story.
OpenAI inserted a conversational agent between consumers and their financial institutions. That agent now holds a unified view of a consumer's financial life across every connected account.
Right now it responds with information. Within quarters, not years, it will respond with action — credit applications, payment arrangements, account servicing — all executed inside ChatGPT.
When that happens, the agent doesn't call a human at your institution. It calls your system. Your IBM i system.
The question for every IBM i practitioner is not whether this traffic is coming. It is coming. The question is whether your system is in a condition to receive it, respond to it, and make that response defensible.
Perplexity added Plaid integration one day before OpenAI's announcement. The race for the consumer finance relationship layer has already begun. Every participant in that race will eventually need to query the systems underneath. On IBM i, that means your DB2 tables. Your RPG business logic. Your core decisioning rules.
Field Note v4 introduced the KD Wall — the point at which an organization's infrastructure physically prevents it from responding at agentic speed. For IBM i operators, the wall has a specific shape. Not a technology failure. An architecture and governance gap.
Silver Lake Installment 2 calls it the layer that doesn't commoditize. This is that layer, made concrete. The organizations building this infrastructure now are the ones agents will reach first — not because they're the largest, but because they're reachable.
Opens IBM i DB2 to modern API consumers over a clean REST/WebSocket interface. An agent that reaches Mapepire reaches your data in real time — not a batch file from yesterday. The state of the account, right now, in milliseconds.
Model Context Protocol provides the standard that lets an AI agent discover, call, and interpret tools from an IBM i system as part of a reasoning chain. Your RPG programs — decades of decisioning logic — become callable tools in the agent's workflow.
Surfaces business logic embedded in your production codebase and makes it interpretable. The institutional knowledge encoded in RPG isn't locked or untouchable. It is documentation-ready and agent-accessible with the right tooling applied systematically.
Together, these three form the bridge. Mapepire surfaces the data. MCP exposes the logic. Project Bob makes the knowledge readable. The IBM i becomes what the Silver Lake Series has been arguing it already is: the orchestration layer the agentic stack runs on top of.
The ChatGPT personal finance launch is the most visible marker yet that agentic traffic in consumer finance is no longer theoretical. These three questions are worth answering before Installment 3 arrives — because I3 maps the technical path assuming your shop has at least started asking them.
Field Note v5 is the alert. Installment 3 is the map. The KD Reduction Engine arrives in June — tracing the full technical path from orchestration layer to knowledge distance reduction at enterprise scale. The IBM Cyber Fraud case from IBM Think 2026 provides the validation: 90% reduction in investigation time, driven by the same architecture the Silver Lake Series has been documenting. The organizations that reduce the distance before the agentic traffic arrives will handle it. The ones that don't will see the traffic route around them.
Follow the Silver Lake Series → signal4i.aiField Note v5 names the wall. The reference page maps what's behind it — five layers every IBM i shop and consumer finance operator needs to build through before agentic traffic can flow without breaking. Discovery, Comprehension, Access, Action, Governance. llms.txt, MCP, Schema.org, SR 11-7. The practitioner checklist before I3 arrives.
Open the Five-Layer Reference → agent-ready.htmlKlarna's AI retreat from credit-adjacent conversations wasn't an operational setback. In regulated U.S. consumer lending, it is a compliance and fair lending event. The companion piece applies the orchestration layer argument to the sector where the wall carries regulatory consequences — ECOA, FCRA, UDAAP, model risk governance — and maps what agent-ready actually looks like for a regulated lender.
Read the Companion → consumerfinance.ai