API teams lack common tooling and guidance to deliver MCP servers alongside their existing APIs for copilot integration.

Traditional filter-based catalog search doesn't match how developers think about their problems, leading to duplicate API development.

API documentation and metadata quality must improve so that both developers and AI agents can effectively discover and use internal APIs.

Governance rules need to be available directly in developers' coding assistants and AI agents, not just in standalone tools and pipelines.

Enterprise security restrictions prevent using standard distribution mechanisms to deliver governance rules to all API designers.

Riley has an accurate central API inventory but cannot account for APIs on teams' own AWS API Gateways.

Riley has a clean API inventory but needs to understand how APIs map to products and business capabilities.

Riley realizes reuse isn't just about whole APIs—it's about reusing schemas, data elements, headers, and parameters.

Riley was asked by leadership to answer how well they are reusing APIs and how they are incentivizing improvement.

Developers perceive governance as friction and avoid it unless compliance is the easiest path.

Organizations can enforce coding standards and CI gates but cannot enforce equivalent governance for the Markdown files that shape AI agent behavior.

Beyond MCP, protocols like A2A, ACP, AP2, and x402 are proliferating — enterprises need unified governance across all agent communication protocols, not just one.

Agentic browsers and AI-native workspaces are becoming the primary interface for discovering and consuming services — APIs need to be optimized for Generative Engine Optimization (GEO), not just traditional developer portals.