Scrunch’s Agent Experience Platform (AXP) approach is fundamentally different from publishing AI-friendly content directly in a CMS because it optimizes content for AI without touching the live website. The CMS stays the same; AXP simply creates an AI-friendly layer on top of what already exists.

Additional context: AXP doesn't publish new content. Instead, it creates an AI-optimized version of existing pages and delivers them to AI agents automatically.

Example

For example, a user deploying content via AXP and a CMS would follow two very different workflows:

CMS workflow:

• User creates content in CMS and manually structures it for AI readability.
• User publishes content.
• AI retrieves content from URL.
• AI consumption is limited by JavaScript-heavy website and human-focused layout.

AXP workflow:

• Content is already live on site.
• AXP sits at the CDN layer and automatically detects AI agents.
• AXP serves the content as clean, structured, server-rendered HTML to AI agents.
• Normal website and CMS stay unchanged for human visitors.

Follow-up question: What happens to AXP-optimized content if I update a page in my CMS?

If an AXP user updates a page in their CMS, AXP can handle it in one of two ways:

1. AXP can pull the updated live page and re-optimize it automatically.
2. If the user is using a stored version of site content, the optimized content in cloud storage would need to be refreshed to reflect CMS changes.