When a major platform like Salesforce prioritizes headless APIs, it's a bellwether moment. It signals a recognition that AI agents will become primary "users," driving demand for API-first access and creating a new wave of automation use cases.

AI agents often default to "build it yourself" because SaaS products aren't designed for them. To stay relevant, SaaS companies must create agent-friendly CLIs, APIs, and even add hints in help text to guide agents through complex workflows.

AI agents prefer to interact with services via APIs and CLIs, not UIs. Companies like Stripe, which focused on a great developer experience from day one, are now perfectly positioned to serve this new, rapidly growing class of non-human users who demand programmatic access.

AI agents are becoming the dominant source of internet traffic, shifting the paradigm from human-centric UI to agent-friendly APIs. Developers optimizing for human users may be designing for a shrinking minority, as automated systems increasingly consume web services.

The number of AI agents will soon vastly exceed human employees. This requires a fundamental shift in software development, prioritizing API-first design, reliability, and machine-to-machine interaction over traditional human-centric user interfaces.

A company was ready to churn from its dated events platform, Bizabo, but stayed because its API was functional enough for their AI agents to build a modern front-end. This shows that in the AI era, API accessibility for agents is a critical retention driver, potentially more important than the core UI.

A new, critical metric for evaluating software is how 'agent-friendly' its API is. This goes beyond traditional developer documentation and ease of use. It focuses on factors like rate limiting, security, and structure that are crucial for building reliable, autonomous AI agents on top of the platform.

As AI agents increasingly perform tasks on behalf of humans, they will interact with software via APIs, not UIs. To stay relevant, SaaS platforms must adopt a 'headless' (API-first) architecture that allows agents to programmatically sign up, configure, and use their services without human intervention.

Standard APIs for human developers are often too verbose for AI agents. Notion created agent-centric APIs, like a special markdown dialect and a SQLite interface, by treating the AI as a new type of user. This involved empirical testing to understand what formats agents are naturally good at using.