Human Site | AXP Agent Representation
Human buyerExisting human experienceAI agentAXP optimized representationEdge/middleware layer
Primary-source positioning describes a parallel agent representation while the human website remains unchanged.
ARCHITECTURE COMPARISON
Eli vs Scrunch: two approaches to the agent-ready website
Both products respond to a web that increasingly serves humans and software agents. Their architectural response is different.
01 / SHARED PREMISE
Machines need to understand a website; humans still need it to work for them.
AI agents are becoming intermediaries between brands and buyers. An agent-ready site therefore needs machine-readable business facts and a useful human journey.
02 / FLAGSHIP ARCHITECTURE
Separate agent representation or integrated adaptive infrastructure.
Published product positioningCurrent Eli productDirection / where supported
Adaptive Website Infrastructure
Human buyerAdaptive proof, content, journey and CTAAuthorized AI agentStructured information and supported actions where supportedOutcome → learning loop
Eli’s intended install-once snippet plus API/MCP infrastructure model is a direction; action capability remains bounded by authorization and support.
03 / CORE TRADE-OFF
Neither architecture is universally superior.
Separate specialized agent experience
A dedicated agent representation sits alongside the current human site.
Integrated adaptive site infrastructure
The same operating layer connects human experience, agent-readable surfaces, supported actions and outcome learning.
04 / PERMISSIONED ACTION
Readability is not actionability.
An agent can understand business facts.
An agent can perform a defined, permissioned action.
Actions require authorization, clear schemas or contracts, and the business rules that protect the buyer and company.
05 / HUMAN CONVERSION
Eli’s human conversion thesis remains central.
Eli is being built to adapt approved proof, content, journey and CTA to buyer intent. This page does not claim Scrunch lacks personalization; it says personalization is not the center of the AXP public description used here.
06 / INSTALLATION MODEL
Two ways to prepare for agents.
- Scrunch
- Edge/middleware serving an agent-optimized site representation.
- Eli
- Intended install-once snippet plus API/MCP infrastructure model, with current and future boundaries clearly qualified.
07 / WHICH SHOULD YOU CHOOSE?
Choose by the website architecture you want to operate.
Choose Scrunch architecture if…
You want a dedicated parallel agent experience layered onto the existing human site.
Evaluate Eli if…
You want discovery, human personalization, agent-readable/actionable interfaces and outcome evidence in one website loop.
Use both or another stack if…
Different teams own intelligence and web infrastructure separately. This page does not claim integration between the products.
BUYER QUESTIONS
Questions worth asking before you choose.
What is an agent-ready website?
It is a website whose business information can be understood by agents and whose supported actions are explicit, authorized and bounded.
How is AXP different from website personalization?
AXP is described as a parallel agent representation; personalization concerns the human website journey and relevant approved proof or action.
Does Eli serve a separate agent website?
Eli’s thesis is integrated adaptive website infrastructure rather than a claimed separate agent website.
What can AI agents actually do on a website?
Only defined, authorized actions supported by clear interfaces and business rules should be available to an agent.
Does MCP make a site agent-ready by itself?
No. It is only one potential interface; readable facts, permissions, contracts and supported actions still matter.
Can Eli and Scrunch coexist?
Conceptually, teams could combine different layers. This page does not claim an existing integration.
SOURCES AND METHOD
Sources checked for this comparison.
These links support the external product and platform references on this page. Eli publishes this comparison; verify critical requirements directly with each provider.
- PrimaryAgent Experience Platform (AXP)Scrunch AI · Checked September 2026
- PrimaryHow AXP serves content to AI agentsScrunch AI · Checked September 2026
- PrimaryAgent Experience Platform announcementScrunch AI · Checked September 2026
CONNECT YOUR WEBSITE
See the Eli infrastructure model.
Review the evidence, buyer journey and permitted action layer a website needs to serve both people and agents.
See the Eli infrastructure model