How the Popover API, Navigation API, Invoker Commands, View Transitions, and other new browser APIs change the game for AI agent interaction — and how to use them to make your site agent-friendly.

Agentic browsers are here. ChatGPT Atlas, Perplexity Comet, Chrome’s Auto Browse, Vercel’s agent-browser — the list grows every month. But while plenty of ink has been spilled on the agent side of the equation, there’s been surprisingly little attention paid to a question that matters just as much: how do modern web platform APIs affect what agents can and can’t do on your site?

In the early days of the web, “cloaking” was a dirty word. It conjured images of black-hat SEOs serving keyword-stuffed gibberish to search engine spiders while presenting a pristine, albeit often irrelevant, page to human users. It was a deception, a slight of hand designed to game the system. Today, as we stand on the precipice of the Agentic Web, the concept of cloaking is being reimagined, rehabilitated, and repurposed. We are moving away from deception and towards Agent Experience Optimization (AXO).