AgntBase
Agent-ready web

Google's UCP is a glimpse of the agent-ready web

UCP is about commerce today. The architecture points further: AI agents need capability, policy, state, identity and trust layers, not just pages they can read.

The shift

The important part is not ecommerce

For years, websites were designed primarily for humans: pages, buttons, forms, navigation and checkout flows. Search engines learned how to crawl and index that world. Large language models learned how to read and summarize it.

AI agents are different. They do not just read websites. They need to understand capabilities, permissions, actions, state, identity and trust.

In January 2026, Google announced the Universal Commerce Protocol, an open standard for agentic commerce across discovery, buying, checkout and post-purchase support. On May 19, Search Engine Journal framed the same move as a broader lesson for agent-ready websites.

Websites need a machine-readable interaction layer for AI agents.

Not just HTML. Not just SEO. Not just schema markup. A protocol surface.

From readable to actionable

AI visibility was only the first turn

Traditional SEO focused on visibility. AI visibility added a new question: can AI systems correctly identify and understand your business?

Agentic systems add another question: can AI safely interact with your business?

  • Can the agent understand products, services, policies and constraints?
  • Can it verify which claims are official?
  • Can it discover available actions?
  • Can it understand permissions and state?
  • Can it complete or prepare a task without crossing a safety boundary?

That is a different problem from ranking a page. It is an interoperability problem.

What UCP reveals

Agents need infrastructure designed for machines

The official UCP site describes the protocol as a common language for platforms, agents and businesses, with building blocks across discovery, checkout and post-purchase workflows. It also points to compatibility with REST, JSON-RPC, AP2, A2A and MCP-style transports.

Capabilities

What can this business do?

Catalog search, checkout, booking, support, identity linking or order management.

Policies

What is allowed?

Agent permissions, required confirmation, payment mandates and action boundaries.

State

What is happening now?

Cart state, session state, order state, availability, status and next valid step.

Commerce is the first obvious battlefield because money creates urgency. But the pattern is not limited to retail.

Beyond shopping

Every vertical will need some version of this layer

Today the visible example is shopping. Tomorrow the same pressure appears in healthcare, legal, travel, logistics, real estate, SaaS operations, customer support and agent-to-agent workflows.

Not every business needs a full UCP implementation. A local salon, clinic or law office does not need the same checkout protocol as Walmart. But it still needs machine-readable answers to practical questions:

  • Who is the official business?
  • Which services are actually offered?
  • Which sources are canonical?
  • What can an assistant safely prepare?
  • What requires human confirmation?
  • Where should an agent stop?
Entry points

The rise of agent entry points

One signal in this transition is the growth of machine-readable endpoints and manifests: /.well-known/ routes, agent manifests, agent cards, structured business profiles, capability declarations and protocol endpoints.

These layers help AI systems understand who a business is, what it offers, what actions are available, what information is canonical, what sources are trusted and how agents are allowed to interact.

The website remains important. But the website alone is no longer the whole interface.

AgntBase position

Where AgntBase fits

At AgntBase, we believe businesses will increasingly need a canonical machine-readable identity layer for the agentic web.

Not to game AI rankings. Not to guarantee citations. Not to pretend that one file solves discovery.

The practical job is to reduce ambiguity for AI systems and help agents identify, understand, verify and safely interact with businesses.

Citation gets you into the answer. Actions get you into the revenue.

That line is not a promise. It is a useful product distinction. Visibility is one layer. Safe action is another.

Reality check

The standards are still early

This ecosystem is moving fast: UCP, A2A, MCP, AP2, agent manifests, trust layers, business agents and new AI commerce surfaces are all evolving. No single standard has fully won.

But the direction is becoming clearer. The next generation of websites will not only be human-readable. They will need to become agent-ready.

Sources

References