The Death of Brand Loyalty: How to Win When Machines Do the Shopping

In a nutshell (TL;DR)...

As AI buyer agents increasingly handle consumer purchasing, traditional brand loyalty built on marketing and visuals is being replaced by "operational excellence." To succeed, brands must move from emotional storytelling to machine-readable data (GXO), focusing on transparent product attributes, API-integrated loyalty programs, and superior post-purchase reliability. Future growth depends on seamlessly fitting into the decision logic of the machines making the purchase.

I decided to dive back into the world of Agentic Commerce this week and it made me wonder how this new concept might alter the way in which we sell, or are sold products. For the last twenty years, digital brand loyalty was built on visual friction and psychological hooks. E-commerce teams spent billions optimizing digital storefronts: high-resolution photography, emotional storytelling, banner ads, exit-intent popups, and strategically placed "You Might Also Like" recommendations.

Now imagine a world where your end customer never visits your website, never sees your homepage, and never interacts with your marketing copy.

As agentic commerce accelerates, consumer purchasing decisions are increasingly delegated to AI models embedded in tools like ChatGPT, Google Gemini, or native shopping super-agents. These AI buyer agents aren't swayed by slick web design, brand nostalgia, or clever marketing copy. They evaluate structured parameters: price, delivery promises, return flexibility, and micro-review sentiment.

When the storefront disappears, traditional brand loyalty dissolves with it. Here is how the retail landscape is shifting and how forward-looking brands are rebuilding loyalty for an AI-first world.

1. The Cold Rationality of the Machine Buyer

When a human shops for coffee beans, they might buy a specific brand because of a colorful bag design, an inspiring origin story on the landing page, or habit.

When an AI agent shops for coffee beans, it executes a parameter-based search:

• Medium roast, single-origin, roasted within 7 days.

• Delivered to doorstep by Thursday at 9 AM.

• Maximum price: $18.00 per 12oz bag.

• Sentiment threshold: Minimum 90% positive sentiment across recent reviews regarding freshness.

If a brand fails any single parameter, the agent bypasses it instantly. No second chances, no emotional leeway. This shifts market dynamics from emotional affinity to operational excellence.

2. Fighting Back with Native "Super-Agents"

Retail giants aren't surrendering the customer relationship to third-party chatbots without a fight. Rather than watching consumers shop through external tools, major retailers are deploying their own AI super-agents natively inside their ecosystems.

A prime example is Walmart’s Sparky, an agentic shopping assistant designed to transform search into a goal-driven, conversational journey.

 TRADITIONAL JOURNEY           AGENTIC RETAIL JOURNEY
 
  [ Keyword Search ]            [ Goal Statement ]
          │                            │
          ▼                            │    

 [ Scroll 50 Listings ]       [ Native AI Super-Agent ]
          │                            │
          ▼                   (Sparky / Native Agent)
[ Compare Prices/Specs ]                │
          │                  ┌─────────┴─────────┐
          ▼                  ▼                   ▼
  [ Manual Checkout ]    [ Multi-Step      [ Cart & Instant
                          Planning ]          Execution ]

Instead of forcing shoppers to type keywords and scroll through hundreds of sponsored items, Sparky handles multi-step goals such as "Plan a backyard BBQ for 10 people under $150 with gluten-free options" and constructs a complete, execution-ready cart directly within Walmart's ecosystem.

By deploying proprietary brand agents, retailers keep the consumer inside their own branded touchpoints while offering the effortless speed of AI automation.

3. Post-Purchase Experience is the New Brand Loyalty

When AI agents evaluate products, past purchase history and customer satisfaction signals heavily influence future recommendations. This means loyalty is no longer won at discovery; it is earned post-purchase.

If an AI agent orders a product for a user and the order arrives late, damaged, or creates return friction, the agent's memory updates. The next time the user asks for a similar item, the agent deprioritizes that brand.

            THE POST-PURCHASE LOYALTY LOOP
               
      +----------------------------------+
      |      AI Agent Executes Order     |
      +----------------------------------+
                      │
                      ▼
      +----------------------------------+
      |  Post-Purchase Delivery & Support|
      +----------------------------------+
                      │
        ┌─────────────┴─────────────┐ 

         ▼                           ▼
[ Smooth Experience ]       [ High Friction ]
        │                           │
        ▼                           ▼

Agent Flags Brand as      Agent Deprioritizes Brand 

   High-Trust Preference        in Future Queries

Brands winning in the agentic era are shifting focus to post-purchase automation:

• Instant WhatsApp/SMS Support: Automated agents resolving exchanges or tracking updates in real time.

• Hassle-Free Returns: One-click return labels generated directly via machine-readable APIs.

• Proactive Replenishment: Post-purchase agents tracking usage cycles and prompting automated re-orders right before a product runs out.

4. Micro-Reviews & Machine-Readable Trust

In the human-centric web, a product with a 4.8-star rating and 10,000 generic reviews like "Great product!" performed well.

AI agents look deeper. They analyze micro-reviews—extracting specific entity sentiment to verify if a product meets granular, real-world constraints:

• "Runs small in the shoulders."

• "Battery lasts 8 hours on high brightness."

• "Waterproofing holds up in heavy rain."

If an agent is tasked with finding a jacket for high-altitude trekking in wet conditions, it reads these unstructured review fragments to calculate a confidence score. Brands that encourage detailed, attribute-rich customer feedback give AI agents the empirical proof needed to select their products over a competitor's.

The New Playbook for Brands

To remain resilient as shopping agents take over the discovery funnel, brands must adopt three fundamental rules:

1. Optimize for Machine Readability (GXO): Move from standard SEO to Generative Experience Optimization (GXO). Ensure product attributes, stock status, delivery promises, and margin rules are accessible via real-time APIs.

2. Elevate Operational Integrity: In an agentic economy, a missed delivery window or an out-of-stock cancellation is not just a lost order, it damages your score in the agent's decision logic.

3. API-ify Your Loyalty Program: Make your reward tiers, points balances, and exclusive perks queryable by external agents so machine buyers can factor member discounts into checkout decisions.

The brands that thrive won't be those with the loudest ad campaigns; they will be the ones that seamlessly fit into the decision logic of the software making the purchase.

The Model Context Protocol (MCP): Bridging AI and Actionable Data

 My day job has recently introduced a new concept for me to understand in my daily life (like I need more new concepts to understand). The Model Context Protocol (MCP)...

What is MCP?

MCP is an open standard designed to unify how AI assistants and large language models (LLMs) connect with external data sources, tools, and environments. An MCP Server acts as a secure gateway or bridge between the AI application (the client) and external systems, such as databases, file systems, or APIs. It is frequently compared to a "USB-C port for AI," as it provides a universal, standardized interface for plugging external capabilities into AI systems.

For example this is incredibly useful if you are building a chatbot for your organisation and want your AI Assistant to have access to your internal customer support database to use as a knowledge base for resolving common issues and answer questions based on your company (i.e. it’s providing context to your AI service). Without it you would somehow have to expose all that information to the larger LLM which is just not gonna happen.

An MCP server exposes three core primitives to AI applications:

• Tools: Executable functions that the AI can actively call to perform actions, such as writing to a database, executing a web search, or modifying a file.

• Resources: Passive, read-only data sources that provide the AI with context, such as database schemas, API documentation, or your customer support database.

• Prompts: Reusable instruction templates that help structure interactions and guide the AI through specific workflows. Prompts that are refined by the architect of the MCP server to provide you with more meaningful responses - saving you time in generating and testing these from scratch.

Why You Would Need an MCP Server?

• To Eliminate Fragmented Integrations: Before MCP, developers had to write custom API integrations for every single external tool or system an AI needed to access. By implementing an MCP server, developers can build an integration once and grant the AI access to a vast, standardized ecosystem of resources without maintaining dozens of custom codebases.

• To Enable Safe Action and Execution: LLMs are limited to the data they were trained on and lack built-in environments to safely execute code or make network requests on their own. An MCP server acts as a controlled execution layer. It keeps sensitive elements like API keys hidden from the model while the server handles the actual safe execution of tasks.

• For Dynamic Tool Discovery: Unlike static API specifications (like OpenAPI) that must be pre-loaded into an LLM, MCP allows AI applications to query servers at runtime to dynamically discover what tools and resources are currently available.

• To Ensure Security and Access Control: MCP servers are designed with enterprise security in mind, utilizing OAuth 2.1 for authentication and centralizing permissions management. This ensures that AI applications only interact with authorized data and that user-specific contexts are strictly respected so data does not leak between users.

• For Portability Across Applications: Because MCP is vendor-agnostic and model-agnostic, you can build a toolset once via an MCP server and plug it into any compatible AI application or IDE—such as Claude Desktop, Cursor, Windsurf, or LangChain—without needing to rewrite the integration.

• To Support Agentic Workflows: MCP facilitates conversational, multi-turn interactions through real-time updates and streaming (using Server-Sent Events). This allows AI agents to dynamically interact with multiple data sources, handle intermediate steps, and maintain persistent context over complex, multi-step tasks.

Why use MCP rather than an API?

While both APIs and MCPs aid in communication between systems, their core audiences, mechanisms, and philosophies differ significantly. A helpful way to frame the difference is that APIs connect machines, whereas MCP connects intelligence to machines.

Here are the primary differences between the two:

Target Audience and Optimization

• APIs are built for human developers to write code against, optimizing software-to-software communication.

• MCP is built specifically for AI models to streamline agentic interactions where an AI needs to reason about the data it receives.

Static vs. Dynamic Discovery

• APIs rely on static contracts that must be pre-loaded, read, and manually interpreted to formulate requests.

• MCP features dynamic discovery. An AI agent can query an MCP server at runtime to ask, "What tools can you offer?", and the server will automatically respond with a structured list of available tools, their descriptions, and parameter schemas. This means the AI always has an up-to-date view of its capabilities without needing manually updated documentation.

Security and Execution

• APIs are exposed over the network and assume the caller can securely manage tokens, headers, and request formatting. However, AI models do not have built-in execution environments and cannot safely hold secrets like API keys.

• MCP introduces a secure intermediary layer. The AI model never sees API keys or sensitive URLs. Instead, the AI asks the MCP server to use a specific tool, and the MCP server validates the input, securely executes the API call using its own hidden credentials, and returns only the safe results. MCP also standardizes security governance, utilizing protocols like OAuth 2.1 to ensure the AI only accesses data the user has explicitly authorized.

Granularity and Abstraction

• APIs typically expose granular, entity-based endpoints (e.g., /users or /weather).

• MCPs are less granular and focus on driving broader use cases. An MCP server exposes high-level capabilities (e.g., get_weather or get_open_supportIssues). A single MCP tool might execute several underlying REST API calls to gather all the necessary context for the AI.

LLM-Native Features

• APIs are generally stateless request-response mechanisms.

• MCP supports multi-turn, long-lived sessions (often using Server-Sent Events) that allow an AI agent to have back-and-forth interactions with a tool. Furthermore, MCP includes AI-specific features like sampling, which allows the MCP server to leverage the LLM's reasoning abilities. For example, an MCP server could fetch open issues and then use sampling to ask the LLM to filter them by "highest security impact"—a subjective analysis that a traditional REST API cannot natively perform.

Output Formatting

• APIs return machine-readable data, such as raw JSON payloads and database entity IDs.

• MCP is designed to return data optimized for an LLM's context window, often formatting responses as human-readable Markdown with fully hydrated entity names instead of raw IDs.

How secure is my data behind an MCP Server?

Because the Model Context Protocol (MCP) acts as a bridge between untrusted, model-generated inputs and sensitive external systems, a single weak point can turn that bridge into a pathway for exploitation. Securing an MCP deployment requires a "shared responsibility" model, where the server stands as a fortified wall protecting resources, and the client acts as a vigilant gatekeeper ensuring the AI does not overstep its bounds.

Academic research breaks down MCP threats into four main categories: malicious developers, external attackers, malicious users, and security flaws. In practice, these manifest as prompt injection, command execution, token theft, excessive permissions, and unverified endpoints.

To protect yourself, you must implement strict safeguards across both MCP servers and MCP clients and quite honestly 99.9% of it goes straight over my head. It can be “dead secure” is what I’ll say on the matter.

How does MCP make my life easier?

So let’s list out a few scenarios where an MCP Server would make sense. At the end of the day it sits in the background and makes interaction with AI more meaningful as it has access to more capabilities and context of the organisation you are talking to.

Software Development and Debugging

The AI coding assistant is greatly enhanced by using MCP to connect directly to local filesystems and version control systems like Git or GitHub. Instead of manually pasting code snippets into a chat, the AI can securely browse your local files, read repository code, search codebases, review pull requests, and even commit changes directly within environments like Cursor or Claude Desktop.

Automated Travel Planning

The true power of multi-server MCP architecture shines here by combining multiple disparate services into one workflow. By connecting a Travel Server, a Weather Server, and a Calendar Server, an AI agent can autonomously read your calendar to find available dates, check destination weather forecasts, search and book flights, and automatically add the itinerary to your schedule while emailing you a confirmation.

Workflow and Communication Automation

AI can connect seamlessly to platforms like Slack, Gmail, or Google Drive. An AI assistant can search through your team's Slack history to pull project context, summarize past decisions, and automatically draft and send emails based on a simple natural language request, all without you needing to switch tabs.

Data Analysis and Visualization

MCP allows AI models to connect directly to SQL databases, Google Sheets, or financial APIs. The AI can read raw data like customer feedback or stock market history, execute complex queries, and instantly generate interactive charts or analytical dashboards. For instance, an AI can use the Alpha Vantage MCP server to fetch 10 years of historical coffee prices and immediately plot an interactive visual graph for you.

Enterprise Knowledge Management

A multi-agent MCP setup can be entirely automated for a Training Management System that can use specialized MCP agents to automatically ingest uploaded PDF documents, extract key learning objectives, generate structured course modules, and create custom multiple-choice assessments without manual human intervention.

Ultimately, the core benefit of MCP in these scenarios is that it transforms AI from a passive text generator into an active, context-aware participant. By utilizing standardized tools, resources, and prompts, you gain a modular, secure way to grant AI access to your personal and business data without needing to write custom integrations for every single application.

That was a big chunk of stuff I learned this week… What next?

A Tale of Two Commerce Protocols

In previous posts I discussed the advent of Agentic Commerce and how that is primed to become the new way to shop for products online.

In order to enable the AI platforms to be aware of your brand presence and product information there are a number of strategies and techniques, specifically GEO (Generic Engine Optimization) and AEO (Answer Engine Optimization), that can attract the AI bots to prefer your brand and recommend your products within the many conversations that customers are now having with AI applications.

GEO is a broad strategy that involves a number of techniques that involve changes in how you write product content and optimize your websites so that AI will pick you first as the authoritative source for the answers within the Agentic Commerce experience.

Very recently a couple of new developments have emerged that both sound like it’s attempting to answer a similar question. Namely OpenAI’s Agentic Commerce Protocol (or ACP) and Google’s Universal Commerce Protocol (or UCP).

OpenAI’s ACP is an open, cross-platform protocol designed to enable shopping and payments directly within AI assistants, independent of any single platform or user interface. It allows AI agents to discover products via merchant-provided feeds, surface accurate pricing and availability, and autonomously initiate checkouts on the user's behalf without redirecting them to an external website.

The checkout process uses secure, delegated payment tokens (which are single-use, time-bound, and amount-restricted), while ensuring that the merchant retains full control over settlement, refunds, chargebacks, and compliance. The first implementation of this protocol is the Instant Checkout experience within ChatGPT.

Google’s UCP is a new open standard designed to establish a common language that allows AI agents, businesses, and payment providers to work together across the entire shopping journey from product discovery to post-purchase support. They also have massive Industry Endorsement collaborating with the likes of Etsy, Shopify, Best Buy and Walmart (US) who are either implementing, or have gone live with AI Agents.

While it is designed to be compatible with other agentic protocols, UCP is initially rolling out exclusively on Google-owned surfaces, such as Search AI Mode, Google Shopping, and the Gemini App. It enables shoppers to buy from eligible retailers directly during product discovery without leaving Google, utilizing Google Pay for seamless transactions while the retailer remains the seller of record.

Why ACP/UCP are More Helpful Than AIO/GEO

While Artificial Intelligence Optimization (AIO) and Generative Engine Optimization (GEO) are critical strategies, they are fundamentally focused on top-of-funnel visibility. AIO and GEO ensure that an AI model correctly parses, embeds, and cites your brand as the "source material" when answering a user's question. However, simply getting found is only the first step of the commerce journey.

ACP and UCP are arguably more helpful because they bridge the gap between discovery and execution, transforming the entire commercial funnel:

• Moving from Recommendation to Action: AIO/GEO might prompt an AI to recommend your product, but the user still has to navigate to your site, browse, add to cart, and manually checkout. ACP and UCP grant the AI "agency" to act on the user's intent and execute the purchase directly within the conversational interface.

• Frictionless Shopping: Traditional e-commerce is linear and rigid (search → browse → filter → product page → cart → checkout). ACP and UCP collapse these steps into a natural dialogue, drastically reducing friction and lowering cart abandonment.

• Capturing Immediate Revenue: By allowing shoppers to move from intent to purchase without breaking context or leaving the app, these protocols turn high-intent discovery moments directly into revenue.

In short, AIO and GEO help AI talk about your product, but ACP and UCP allow AI to buy your product on the customer's behalf.

Which one to choose?

Both OpenAI's Agentic Commerce Protocol (ACP) and Google's Universal Commerce Protocol (UCP) share the same overarching goal: to reduce friction in the shopping journey by allowing AI agents to handle product discovery and checkout seamlessly, without redirecting the user to an external website.

However, they differ significantly in their execution environments, how they handle payments, and their initial scope.

OpenAI’s Agentic Commerce Protocol (ACP)

• Design & Environment: ACP is an open, cross-platform protocol built to enable shopping and payments directly within AI assistants. It is designed to be independent of any single platform, user interface, or distribution surface. Currently, its primary implementation is the "Instant Checkout" experience inside ChatGPT.

• Payment Mechanism: ACP initiates checkout on the user's behalf using delegated payment tokens. These tokens are highly secure because they are single-use, time-bound, and amount-restricted.

• Merchant Role: In this model, merchants maintain complete control over the transactional backend, retaining responsibility for settlement, refunds, chargebacks, and compliance.

Google’s Universal Commerce Protocol (UCP)

• Design & Environment: UCP is pitched as a new open standard designed to support the entire shopping lifecycle, from product discovery and buying to post-purchase support. However, unlike ACP's cross-platform focus, UCP is initially being rolled out exclusively across Google-owned surfaces, including Search AI Mode, Google Shopping, and the Gemini App.

• Payment Mechanism: Instead of delegated tokens, UCP leverages Google Pay to complete transactions natively during product discovery, with PayPal support planned for the future.

• Additional Features: Alongside UCP, Google launched a feature called "Business Agent," which allows retailers to engage shoppers conversationally and enable direct purchases right within Google Search.

The Core Differences

• Where the Shopping Happens: ACP enables agent-led commerce primarily across the OpenAI ecosystem as a standalone destination, while UCP currently focuses on reducing checkout friction specifically within Google's massive search and discovery surfaces.

• Coexistence Over Competition: Google designed UCP to be compatible with other agent-to-agent standards and protocols. This means the two protocols are not necessarily meant to replace one another, but rather to coexist. UCP helps convert high-intent shoppers who are actively searching on Google, while ACP opens the door to new demand where AI chat assistants act as the shopping destination.

So it’s not like the old VHS/Beta video wars of the 80s. The question isn't which protocol "wins" it's whether your product data (and infrastructure) is ready to feed both. The reality is that you may need to support a multi-protocol ecosystem, just like supporting Apple Pay, Google Pay, and PayPal today. We are entering a multi-agent, multi-protocol world where structured product data is the "source code" of commerce.