The Shift
The Model Context Protocol (MCP), OpenAI's function calling, and tool-use patterns across all major AI platforms are reshaping how AI interacts with the web. Instead of scraping pages, AI agents call structured APIs. Instead of parsing HTML, they invoke functions with typed parameters.
This isn't a future prediction — it's happening now. AI agents book flights, query databases, manage calendars, and process transactions through structured API calls. The web page is becoming a human fallback, not the primary interface.
What This Means for Frameworks
Frameworks built around API-first architecture — FastAPI, Next.js API routes, SvelteKit endpoints — are naturally positioned for this shift. They produce structured responses by default. Adding an MCP server or tool definition to an API-first framework is straightforward.
Frameworks built around HTML page rendering — WordPress, Drupal, Joomla — require significant retrofitting. Their architecture assumes a human reading a browser. Making them callable by AI agents means building an API layer on top of a system that was never designed for one.
The API-Readiness Spectrum
The Competitive Implication
Organizations whose services are callable by AI agents will be discovered, recommended, and transacted with by AI. Organizations whose services require human browser interaction will be bypassed.
This isn't about AI replacing websites. It's about AI becoming another — increasingly important — channel through which services are accessed. Frameworks that support both human and machine interfaces serve both channels. Frameworks that only support human interfaces serve a shrinking share of interactions.
