Appendix F: Implementation Roadmap

MX-Protocols

Tom Cranstoun

January 2026

Appendix F: Implementation Roadmap

A practical guide to making your website work well for both AI agents and human users.

Based on: MX: The Protocols: Designing the Web for AI Agents and Everyone Else

Priority 1: Critical Quick Wins

These changes provide immediate benefit with minimal effort.

Effort Level: A single developer can implement these changes in a focused session. No architectural changes required, minimal risk, immediate deployment. Most changes involve replacing existing patterns with better alternatives rather than building new systems.

Error Messages

Pricing and Information

Basic Structured Data

Example (basic product):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Your Product Name",
  "offers": {
    "@type": "Offer",
    "price": "99.99",
    "priceCurrency": "GBP",
    "availability": "https://schema.org/InStock"
  }
}
</script>

Example (product with delivery and service charges):

This example shows how to represent the complete pricing breakdown mentioned above (Product: £99 + Delivery: £15 + Service: £5 = Total: £119) in Schema.org JSON-LD.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Your Product Name",
  "offers": {
    "@type": "Offer",
    "price": "119.00",
    "priceCurrency": "GBP",
    "availability": "https://schema.org/InStock",
    "priceSpecification": [
      {
        "@type": "UnitPriceSpecification",
        "price": "99.00",
        "priceCurrency": "GBP",
        "name": "Product price"
      },
      {
        "@type": "DeliveryChargeSpecification",
        "price": "15.00",
        "priceCurrency": "GBP",
        "name": "Delivery charge"
      },
      {
        "@type": "PaymentChargeSpecification",
        "price": "5.00",
        "priceCurrency": "GBP",
        "name": "Service charge"
      }
    ],
    "priceValidUntil": "2026-12-31",
    "shippingDetails": {
      "@type": "OfferShippingDetails",
      "shippingRate": {
        "@type": "MonetaryAmount",
        "value": "15.00",
        "currency": "GBP"
      },
      "shippingDestination": {
        "@type": "DefinedRegion",
        "addressCountry": "GB"
      }
    }
  }
}
</script>

Key points:

  • The main price field (£119.00) shows the total cost including all fees
  • priceSpecification array breaks down individual charges (product, delivery, service)
  • shippingDetails provides explicit delivery cost and destination information
  • This structured data allows AI agents to understand complete pricing before initiating purchases

Dynamic Content

Example (animated GIF with description):

<img src="assembly-process.gif"
     alt="Three-step assembly process"
     aria-describedby="assembly-detail">
<div id="assembly-detail" data-agent-visible="true">
  Assembly steps:
  1. Insert tab A into slot B
  2. Rotate clockwise 90 degrees until click
  3. Secure with provided screw
</div>

Example (decorative vs informational video):

<!-- Decorative: purely aesthetic -->
<video data-video-role="decorative"
       aria-hidden="true"
       autoplay muted loop playsinline>
  <source src="ambient-clouds.mp4" type="video/mp4">
</video>

<!-- Informational: needs transcript -->
<video data-video-role="informational"
       controls>
  <source src="product-demo.mp4" type="video/mp4">
  <track kind="captions" src="demo-en.vtt">
</video>
<details>
  <summary>View transcript</summary>
  <ol>
    <li>Step 1 description</li>
    <li>Step 2 description</li>
  </ol>
</details>

Priority 1.5: Protocol Integration Strategy

When to integrate: Protocol integration timing depends on your exposure level and business priorities. This section helps you decide when to integrate commerce protocols (ACP, UCP) versus focusing on universal agent-friendly patterns first.

Critical principle: Universal patterns (semantic HTML, structured data, explicit state management) work for all agents regardless of protocol. Implement these first. Protocol integration comes after your site is fundamentally agent-navigable.

Integration Timeline by Exposure Level

Critical exposure (ad-dependent, agent traffic threatens business model):

  • Protocol integration: Not applicable - focus on business model diversification first
  • Universal patterns: Immediate (helps humans and remaining agent traffic)
  • Rationale: Protocol integration enables transactions, but your problem is that agents bypass ads. Fix economics before enabling more agent traffic.

High exposure (transaction-based, competitive pressure, agent-hostile patterns):

  • Protocol integration: Q1 2026 (immediate if reading this after Q1 2026)
  • Universal patterns: Immediate (Priority 1 from this appendix)
  • Protocol choice: One open protocol (ACP or UCP) based on traffic sources
  • Rationale: Agent-mediated commerce is processing real transactions (Amazon Alexa+, Microsoft Copilot Checkout launched January 2026). Waiting risks competitive disadvantage.

Medium exposure (transaction-based, some agent compatibility):

  • Protocol integration: Q2 2026
  • Universal patterns: Q1 2026 (Priority 1 and Priority 2)
  • Protocol choice: One open protocol initially, evaluate second protocol Q4 2026
  • Rationale: Build foundation first (universal patterns), then add transaction capability once patterns are stable.

Low exposure (relationship-based sales, strong brand loyalty):

  • Protocol integration: Q3-Q4 2026 or later
  • Universal patterns: Q2 2026 (Priority 1 only)
  • Rationale: Monitor industry adoption, wait for protocol convergence or clear winner, focus on fixing obvious usability problems first.

Single Protocol vs. Dual Protocol Decision

Choose one open protocol if:

  • Small-to-medium business (under £10M annual revenue)
  • Limited engineering resources (fewer than 5 developers)
  • Traffic comes primarily from one source (Google Search → UCP; ChatGPT users → ACP)
  • First-time protocol integration (learn one system before adding complexity)

Support both open protocols if:

  • Large enterprise (£50M+ annual revenue)
  • Significant engineering capacity
  • Traffic sources are diversified (both Google and OpenAI users)
  • Agent-mediated commerce expected to exceed 15% of transactions

Avoid Microsoft proprietary integration unless:

  • 80%+ of your business is enterprise B2B commerce
  • Your customer base is exclusively Windows/Office 365 enterprise users
  • You have strategic partnership with Microsoft justifying lock-in

Rationale: Microsoft’s proprietary approach creates isolation (see Chapter 9). Even if you eventually support Microsoft, integrate at least one open protocol first to avoid vendor lock-in.

Small Business Simplified Path

If you’re a small business without dedicated engineering teams:

Step 1: Check automatic integration (Week 1)

  • Shopify merchants: Verify whether ACP is enabled by default (Shopify added ACP support Q4 2024)
  • Etsy sellers: ACP integration automatic for all shops
  • Other platforms: Check your e-commerce provider’s documentation for protocol support

Step 2: Implement universal patterns (Weeks 2-4)

Focus on Priority 1 items from this appendix:

  • Remove toast notifications, add persistent errors
  • Display complete pricing upfront (no “From £99”)
  • Add basic Schema.org JSON-LD for products or services
  • Verify forms have clear error messages

Step 3: Monitor platform provider announcements (Ongoing)

Your e-commerce platform will likely choose protocols for you. Follow their guidance rather than building custom integration.

Step 4: Reassess quarterly (Q2, Q3, Q4 2026)

Check:

  • Has your platform added protocol support?
  • Has one protocol clearly won market share?
  • Have ACP and UCP converged into unified standard?
  • What percentage of your traffic comes from agents?

Timeline: Q2-Q3 2026 for protocol integration (after universal patterns implemented). If your platform doesn’t offer simplified integration by Q4 2026, evaluate custom implementation or professional audit service.

Enterprise Integration Considerations

Large businesses with significant agent exposure should treat protocol integration as strategic infrastructure, not optional enhancement.

Build protocol abstraction layers:

Don’t integrate directly with ACP/UCP in your checkout code. Build an abstraction layer:

Your Checkout Logic
       ↓
Protocol Abstraction Layer (swap ACP ↔ UCP without rewriting checkout)
       ↓
   ACP Implementation    UCP Implementation

This enables:

  • Swapping protocols if one fails or loses market share
  • Adding new protocols without rewriting business logic
  • Testing different protocols for conversion rate optimisation
  • Migrating if protocols converge into unified standard

Include agent testing in QA processes:

Traditional QA tests human interactions (click buttons, fill forms, complete checkout). Agent QA tests different patterns:

  • Can agents extract product data from structured markup?
  • Do validation errors persist long enough for agents to read them?
  • Can agents determine transaction success from DOM state?
  • Do protocol-specific endpoints return correct data formats?

Track agent traffic separately in analytics:

Distinguish between:

  • Human-initiated transactions (user directly browses and buys)
  • Agent-mediated transactions (user delegates task to AI assistant)

This enables measuring protocol-specific conversion rates and ROI.

Implement EAL delegation patterns:

When agents make purchases on users’ behalf, preserve customer relationship data. See Chapter 6 for EAL delegation patterns and security considerations.

Consider protocol convergence timelines:

Over-engineering for permanent dual-protocol support may prove unnecessary if ACP and UCP merge within 6-12 months (Chapter 9 analysis). Balance current needs (support both now) with future flexibility (architect for convergence).

Testing and Validation Requirements

Before deploying protocol integration, verify:

Authentication flow:

  • Users can authenticate through protocol-specific OAuth flow
  • Tokens expire appropriately and refresh without user re-authentication
  • Failed authentication shows clear error message (not generic “Try again”)

Transaction handling:

  • Cart creation succeeds with protocol-formatted data
  • Inventory checks prevent overselling
  • Tax calculation matches your standard checkout process
  • Payment processing completes through protocol infrastructure
  • Order confirmation provides tracking and order ID

Error scenarios:

  • Out-of-stock items handled gracefully
  • Payment failures don’t create orphaned carts
  • Network timeouts trigger retry logic, not silent failures
  • Protocol version mismatches detected and logged

Security validation:

  • Authentication tokens stored securely (not in URL parameters or client-side JavaScript)
  • Transaction data encrypted in transit
  • User permissions verified (users can only access their own transactions)
  • Rate limiting prevents abuse

Platform-Agnostic Patterns Before Protocol-Specific Integration

Critical guidance: Don’t integrate protocols before fixing underlying patterns.

Protocol integration enables secure transactions. But it doesn’t help if agents can’t:

  • Extract product information (requires structured data)
  • Compare options (requires complete pricing upfront)
  • Verify transaction success (requires explicit state attributes)
  • Handle errors (requires persistent, machine-readable feedback)

The correct order:

  1. Universal patterns (Priority 1 from this appendix) - Ensures agents can navigate and understand your site
  2. Protocol integration (this section) - Enables secure, authenticated transactions
  3. Advanced optimisation (Priority 2-4) - Improves agent efficiency and conversion rates

Integrating protocols without fixing patterns is like building a secure payment gateway for a site agents can’t read. Technically correct but practically useless.

When to Evaluate Professional Audit Services

Consider professional audit or implementation services if:

  • You lack internal expertise in protocol integration
  • Your e-commerce platform doesn’t offer simplified integration
  • You need dual-protocol support but lack engineering capacity
  • You’re unsure which protocol best serves your business model
  • You need protocol abstraction architecture guidance

Timeline: Q2-Q3 2026 for most businesses. Earlier if you’re high-exposure enterprise; later if you’re low-exposure small business.

Priority 2: Essential Improvements

Effort Level: Requires coordinated work across multiple developers or sustained focus from a small team. Involves systematic changes to existing code, testing across multiple pages, and potentially updating design patterns. May require stakeholder buy-in for visible changes to user experience. Plan for iterative deployment with rollback capability.

Form Improvements

Example:

<form data-state="incomplete">
  <div class="form-status">
    Completion: <span id="completion">40%</span>
    Errors: <span id="errors">2</span>
  </div>

  <input
    type="email"
    data-validation-state="invalid"
    aria-invalid="true"
    aria-describedby="email-error">
  <div id="email-error" role="alert">
    Email format invalid (expected: name@domain.com)
  </div>

  <button disabled data-disabled-reason="2 validation errors">
    Submit (2 errors remaining)
  </button>
</form>

Content Organization

Dynamic Content Patterns

Example (carousel with static alternative):

<div class="carousel"
     data-total-slides="5"
     data-current-slide="1"
     data-autoplay="false"
     aria-label="Featured products">
  <div class="slide" data-slide-index="1" aria-label="Slide 1 of 5">
    Product 1
  </div>
  <!-- Slides 2-5 -->
</div>

<!-- Static alternative -->
<details>
  <summary>View all 5 products</summary>
  <ul data-agent-visible="true">
    <li>Product 1 - £89.99</li>
    <li>Product 2 - £129.99</li>
    <li>Product 3 - £19.99</li>
    <li>Product 4 - £24.99</li>
    <li>Product 5 - £12.99</li>
  </ul>
</details>

Example (animated text done correctly):

<!-- Complete text in HTML -->
<h1 aria-live="off">
  Welcome to our platform that transforms workflows
</h1>
<script>
  // CSS animation only - content already in DOM
  document.querySelector('h1').classList.add('typewriter-effect');
</script>

Loading States

Example:

<div data-load-state="loading"
     data-started="2025-01-15T10:30:00Z"
     data-expected-duration="3000"
     role="status"
     aria-live="polite">
  Loading product information (estimated 3 seconds)
</div>

Priority 3: Core Infrastructure

Effort Level: Multi-person project requiring planning, architectural decisions, and cross-functional collaboration. Involves changes to core application structure, integration with external systems, and potentially business model adjustments. Requires thorough testing, staged rollout, and ongoing monitoring. Budget for technical debt reduction and refactoring. Expect dependencies on legal, product, and business stakeholders.

Agent Detection

Structured Data Expansion

MX Carrier Tags

HTTP Semantics

Example:

// Successful form submission
app.post('/cart/add', (req, res) => {
  addToCart(req.body);
  res.redirect(303, '/cart/added?product=123');
});

// Validation error
app.post('/checkout', (req, res) => {
  const errors = validate(req.body);
  if (errors.length > 0) {
    res.status(400).json({
      error: 'Validation failed',
      details: errors.map(e => ({
        field: e.field,
        message: e.message,
        code: e.code
      }))
    });
  }
});

Priority 4: Advanced Features

Effort Level: Ongoing programme, not a one-time project. Requires dedicated resources, sustained organizational commitment, and strategic business alignment. Involves building new systems, establishing governance frameworks, and potentially partnering with external platforms. Plan for multi-phase delivery with measurable business outcomes at each stage.

API Development

Site-Wide Agent Guidance

Example llms.txt:

# llms.txt - AI Agent Guidance

> RetailCo sells electronics. AI agents may browse products and
> complete purchases on behalf of customers with valid delegation tokens.

preferred-access: api
api-endpoint: https://api.retailco.com/v1
api-docs: https://developers.retailco.com

allow: /products/*
allow: /categories/*
allow: /reviews/*

auth-required: /cart/*
auth-required: /checkout/*
auth-required: /account/*

rate-limit: 100/minute
rate-limit: 500/minute with-api-key

extraction: product-data-allowed
extraction: pricing-allowed
attribution: appreciated

agent-contact: api-support@retailco.com

Testing Infrastructure

Analytics and Monitoring

Identity and Delegation

Accessibility Alignment

These improvements help both agents and users with disabilities:

Semantic HTML

ARIA Attributes

Keyboard Navigation

Performance and Operations

Rate Limiting

CSS for Agent Mode

Example:

@media (prefers-reduced-motion: reduce) {
  *, *::before, *::after {
    animation-duration: 0.01ms !important;
    transition-duration: 0.01ms !important;
  }
}

body.agent-mode * {
  animation-duration: 0ms !important;
  transition-duration: 0ms !important;
}

body.agent-mode [data-agent-visible] {
  display: block !important;
}

Version Management

Advanced Implementation

Entity Asset Layer (EAL) for E-commerce

If you sell products and want to preserve customer relationships when agents shop:

Security Considerations

Content Creator Protections

If you’re an ad-funded content site:

Testing Your Implementation

Manual Tests

Automated Tests

Validation Tools

Maintenance

Ongoing

Quarterly Review

Success Metrics

Track these to measure progress:

Agent Traffic:

  • % of total traffic from agents
  • Growth rate month-over-month

Agent Success:

  • Task completion rate for agents vs humans
  • Error rate for agents vs humans
  • Average task duration for agents vs humans

Business Impact:

  • Conversion rate for agent sessions
  • Revenue from agent-mediated transactions
  • Customer acquisition cost for agent traffic

Technical Health:

  • Structured data coverage (% of pages)
  • API adoption rate
  • Rate limit violations
  • Agent-specific error volume

Priority by Business Type

E-commerce / Retail

Priority 1: Complete pricing, structured product data, checkout flow clarity Priority 2: Identity layer integration, delegation tokens Priority 3: API development, advanced analytics

Content Publishers

Priority 1: Content extraction policy, attribution requirements Priority 2: Partial content strategy, llms.txt Priority 3: Licensing framework, platform partnerships

SaaS / Applications

Priority 1: API development, OAuth delegation Priority 2: Agent-specific pricing, usage tracking Priority 3: Integration partnerships, agent SDKs

Service Businesses

Priority 1: Structured business data (hours, location, services) Priority 2: Booking/appointment clarity Priority 3: Simple API for availability checks

Small Businesses

Priority 1: Basic structured data, complete pricing Priority 2: Form improvements, clear errors Priority 3: One-page information display

Getting Help

Resources:

Community:

  • Share experiences with other implementers
  • Report common agent failures to help build best practices
  • Contribute to emerging standards like llms.txt

Professional Support:

  • Hire accessibility consultants (benefits overlap with agent compatibility)
  • Consider API development agencies if building formal APIs
  • Engage security consultants for delegation token implementation

Remember: Every improvement helps both agents and humans. Start with quick wins, build momentum, and iterate based on insights from your analytics.

Next steps: Pick three items from Priority 1 and implement them. Track the impact. Build from there.

Home Top