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?

The web architectural landscape is shifting beneath our feet. As we transition from an internet browsed primarily by human-operated clients (like Chrome, Firefox, or Safari) to one traversed by autonomous, intelligent agents, the ability to discern who or what is requesting our content has never been more critical. In this new era, Agentic SEO is not just about keyword optimization or semantic HTML; it is fundamentally about context awareness. We need to know who is looking at our static HTML pages to provide the most optimized, relevant, or perhaps cloaked, experience.

The XML sitemap was invented in 2005. It lists URLs. But as we move towards Agentic AI, the concept of a “page” (URL) helps human navigation, but constrains agent navigation. Agents want actions.

The API Sitemap

We propose a new standard: the API Sitemap. Instead of listing URLs for human consumption, this file lists API endpoints available for agent interaction.

<url>
  <loc>https://api.mcp-seo.com/v1/check-rank</loc>
  <lastmod>2026-01-01</lastmod>
  <changefreq>daily</changefreq>
  <rel>action</rel>
  <openapi_spec>https://mcp-seo.com/openapi.yaml</openapi_spec>
</url>

This allows an agent to discover capabilities rather than just content.