13 Apr 2026

AI coding agents are already hitting your developer documentation, and most of it is failing them silently. The agent fetches your page, strips the HTML, counts the tokens, decides the context window cost is too high, and discards it. No error. No warning. The agent just hallucinates a solution instead, or gives up.

For consumer finance technology teams, this matters right now. If you run a lending API, an open banking integration layer, or any developer-facing product, the people building against your platform are increasingly using agentic coding tools. Claude Code, Cursor, GitHub Copilot in agent mode. They are not reading your docs. Their AI is trying to.

The specific problem worth fixing

The failure modes are not exotic. They come down to a few concrete things:

• Token-bloated pages where the actual API reference is buried under marketing copy and navigation chrome
• robots.txt files that block crawlers indiscriminately, including the agents your partners are using to build integrations
• Capability signalling that was designed for humans skimming headers, not machines trying to infer what an endpoint actually does

Financial services documentation tends to be particularly bad here. Compliance requirements push teams toward verbose, heavily caveated prose. Legal reviews add disclaimers that obscure the technical signal. The result is documentation that reads fine to a human but looks like noise to an agent trying to extract a data model.

The deeper question is whether your integration experience is going to degrade quietly as agentic development becomes the default. The teams who will notice first are not yours. They are the fintechs and brokers building on top of your infrastructure, suddenly finding that their AI tools produce worse results against your API than against a competitor's. That is a distribution problem, not just a developer experience problem.

Bolt's decision to cut 30% of its workforce and rebrand the move as an 'AI-first pivot' deserves more scepticism than it's getting in the press coverage.

When a company drops from an $11 billion valuation to $300 million, the narrative shifts fast. Suddenly the layoffs aren't about a failed growth strategy or overextended hiring — they're a bold, forward-thinking transformation. The AI framing does a lot of heavy lifting here. It repackages financial distress as technological vision, which is a more comfortable story for investors, remaining employees, and the trade press.

This matters for UK consumer finance leaders because we're going to see more of this pattern. As credit markets tighten and fintech funding stays cautious, 'AI transformation' becomes the respectable way to announce you hired too many people at peak valuation and now you can't afford them.

The harder question is whether the underlying product actually benefits from the restructure. AI can genuinely reduce operational headcount in areas like document processing, customer communications, and decisioning support. We've seen real gains in those areas ourselves. But you can't automate your way out of a broken proposition. If Bolt's checkout and payments product wasn't winning market share with 1,000 people, it's not obvious why it will with 700 and a sharper AI story.

For anyone building loan origination or payments infrastructure in the UK, the honest version of this lesson is straightforward:

• AI reduces the cost of execution, not the need for a clear strategy
• Headcount cuts fund the runway but don't fix product-market fit

The FCA's increasing scrutiny of automated decisioning in consumer credit adds another layer here. Going 'AI-first' in a regulated environment isn't just a technology choice — it's a compliance commitment. Explainability, fairness testing, ongoing model monitoring. That work requires skilled people, often more of them than the pre-AI process did.

The real test for Bolt, and for any fintech taking this path, is whether the AI investment shows up in product quality eighteen months from now — or whether this is just the most credible story available when the numbers stop working.