Why sites need agent‑ready APIs now

In a recent interview, Google CEO Sundar Pichai explained that AI agents will reach website content in two distinct ways. The first mirrors how a human browses – agents fetch pages using a user‑agent string called “Google‑Agent”. The second relies on specialised protocols, with the Universal Commerce Protocol (UCP) highlighted as the emerging standard. Pichai noted that while both methods will coexist, protocols are expected to scale more efficiently over time.

Preparing an agent‑friendly API now positions you to capture that future demand.

Understanding the two access methods

• Browser‑style fetches: agents use the “Google‑Agent” user‑agent string and generally ignore robots.txt, meaning page‑level SEO remains relevant.
• Protocol‑style fetches: Google is backing the Universal Commerce Protocol (UCP) as an open standard that lets agents perform commerce‑related actions such as direct buying and cart transfer.

In the interim, both approaches will be active, creating a “chaotic evolution” toward interoperable standards.

Key considerations for an agent‑friendly API

• Align with open standards: UCP is described as an open standard for agent commerce. Designing your API to match its data structures and actions improves compatibility.
• Expose commerce‑relevant endpoints: Provide clear, machine‑readable endpoints for product data, inventory status, and checkout‑related actions that agents can call.
• Make the API discoverable: Publish endpoint URLs and usage guidelines in a developer portal or within your Merchant Centre settings so agents can locate them easily.
• Document request and response formats: Include schema details, example payloads, and any required headers so agents can interact without ambiguity.

Practical steps to get started

• Audit current endpoints: List any product, inventory, or checkout APIs you already expose and note gaps relative to UCP‑style actions.
• Map to UCP capabilities: Identify which of your existing endpoints can support the actions UCP enables, such as cart transfer from Google to your site.
• Create a dedicated agent endpoint: Build a simple, well‑structured API that returns product SKU, price, and availability in a format consistent with UCP documentation.
• Publish and test access: Add the endpoint URL to your Merchant Centre (if you sell through Google) and monitor request logs for successful agent calls.
• Monitor and iterate: Track usage patterns, error rates, and data quality. Refine the API based on what agents request and how they respond.

When you test, pay attention to response consistency and error handling. Agents expect reliable, machine‑readable data; any deviation can cause them to skip your site.

What to do now

Start with a pilot project. Choose a high‑traffic product feed and expose it via a new endpoint that aligns with UCP‑style actions. Run the endpoint in a sandbox environment, monitor request logs, and iterate on data format and security settings. Once the pilot is stable, expand the API to cover the full catalogue and, if you sell through Google, enable the cart‑transfer option in Merchant Centre.

At the same time, keep your site’s SEO healthy. Since browser‑style fetches will remain important while protocols mature, good on‑page optimisation ensures you don’t lose the traffic that still arrives via traditional crawling.

Sources

• Search Engine Journal — Google CEO Says Agents Will Hit Sites Two Ways, Pages And APIs