Klasker Academy

FOUNDATIONS

The Agentic Web

The web was built primarily for people to read and interact with. The next web must also be understandable and usable by software agents acting on behalf of people and organisations.

From pages to capabilities

The traditional web is organised around pages, links, forms and interfaces. Humans interpret those pages, make decisions and perform actions.

An AI agent works differently. An agent may need to discover a product, understand its properties, compare alternatives, check availability, calculate delivery, follow a return policy and eventually complete an authorised transaction.

This changes the fundamental question from:

Can a person use this website?

to:

Can an authorised agent understand and use this website reliably?

Three stages of web readiness

1. Human-readable

Information is presented primarily for people. Navigation, visual layout, forms and conventional interfaces are the main interaction mechanisms.

2. Machine-legible

Important information is exposed in structured, predictable and machine-readable forms such as JSON-LD, APIs, feeds and well-known resources.

3. Agent-ready

An authorised agent can discover capabilities, understand current information, interact with the business and complete useful tasks under defined rules.

What is an AI agent?

An AI agent is software that can interpret a goal, obtain information, use tools or services and take actions within defined permissions.

A conventional chatbot may answer a question. An agent can go further: it may search, compare, calculate, request information from another system or perform an authorised action.

The distinction matters because a website that is excellent for conversation is not necessarily ready for autonomous or semi-autonomous interaction.

Machine legibility

Machine legibility is the ability of software to discover, interpret and consistently use information published by a website.

Useful signals can include:

  • JSON-LD and Schema.org structured data
  • Product, Offer, price and availability information
  • APIs and structured feeds
  • robots.txt and XML sitemaps
  • security.txt
  • llms.txt and related machine-readable resources
  • .well-known resources
  • clear canonical URLs
  • consistent policies and terms
  • documented machine-facing capabilities

Machine legibility does not automatically make a website agent-ready. It is the foundation on which agentic interaction can be built.

Protocols change the relationship

The Agentic Web is not simply a collection of better HTML pages. New protocols are being developed to allow agents, services, businesses and payment systems to communicate using defined structures and trust mechanisms.

Agent ↔ Agent

Protocols such as A2A enable agents and agentic systems to communicate with one another.

Agent ↔ Tool

MCP provides a standard way for AI applications to interact with external tools, resources and prompts.

Agent ↔ Commerce

Emerging commerce protocols provide structured ways for agents to discover and interact with merchants.

Agent ↔ Payment

Agentic payment protocols introduce mechanisms for authorisation, mandates, identity and transaction control.

Klasker Academy examines these layers separately because protocol support is one of the measurable foundations of Agentic AI readiness.

Static Readiness is not Agentic Readiness

A website can publish excellent metadata and still be difficult for an agent to use.

Static Readiness

Can machines discover, access and interpret the information published by the website?

  • Security
  • Machine legibility
  • Structured data
  • Discoverability
  • Protocol declarations

Agentic Readiness

Can an authorised agent actually perform useful tasks reliably?

  • Product discovery
  • Questions and answers
  • Price and availability
  • Shipping and returns
  • Commerce interaction

These are related but different measurements. A website may therefore have strong Static Readiness while still requiring substantial work before it becomes genuinely agent-ready.

Truth matters

Agents make decisions from information. If different parts of a website provide conflicting information, the problem is greater than an ordinary content inconsistency.

Consider a product published with:

  • JSON-LD price: €49.99
  • Visible page price: €59.99
  • Structured availability: InStock
  • Actual store status: Out of stock

A human may notice the discrepancy. An automated agent may interpret one of these representations as authoritative and act on incorrect information.

Agent readiness therefore requires not only machine-readable information, but trustworthy and consistent information.

Klasker calls significant inconsistencies between published representations Promise Drift.

Trust and authorisation

An agent should not be trusted simply because it claims to be an AI agent.

Agentic systems introduce questions about identity, authorisation, intent, transaction limits and accountability.

Depending on the task, a trustworthy interaction may require mechanisms such as:

  • verified agent identity
  • cryptographically protected intent
  • explicit user mandates
  • spending limits
  • transaction policies
  • refund and cancellation rules
  • human override
  • auditable transaction records

This is why Agentic AI readiness extends beyond SEO, AEO and structured data.

How Klasker sees the Agentic Web

Klasker approaches Agentic AI readiness as a layered system:

Security

Can the system provide a reasonably secure foundation for machine interaction?

Machine Legibility

Can software discover and understand the published information?

Protocol Coverage

Which relevant agentic protocols and machine-facing interfaces can be detected?

Agentic Interaction

Can an agent actually complete meaningful tasks?

Trust

Can an agent determine what it may safely trust and what it is authorised to do?

Commerce

Can an authorised agent discover, negotiate and transact within defined boundaries?

Continue learning

The foundations lead to the technologies and measurements that make the Agentic Web possible.

Agentic Commerce Protocols

Explore ACP, UCP, AP2, MPP, Visa TAP, Mastercard Agent Pay and related standards.

Explore protocols

Machine Legibility

Learn how structured information, APIs, well-known resources and machine-facing documentation affect agent discovery.

Learn about legibility

Agent Trust

Examine identity, authorisation, intent, reputation and the emerging KYA model.

Explore agent trust