What Is Agentic Commerce? Foundations & Protocols

What Is Agentic Commerce — A Definition

In traditional e-commerce, a human actor makes the purchase decision: they search, compare, select, and confirm the transaction. In agentic commerce, an AI agent takes over these steps fully or partially. The agent operates within defined parameters — budget, delivery requirements, quality criteria, compliance specifications — and acts autonomously within those boundaries.

Relevant use cases include:

• B2B Procurement: Agents research suppliers, evaluate terms, and trigger ordering processes — based on real-time data from machine-readable supplier sources.
• Payment Processing: PayPal, Visa, Mastercard, and Stripe each announced agentic commerce initiatives in 2025. Agents select payment routes, negotiate terms, and execute transactions.
• Inventory Management: Autonomous systems monitor stock levels, forecast demand, and trigger reorders with pre-qualified suppliers.
• Supplier Qualification: Agents evaluate potential vendors based on structured data, compliance documentation, and pricing structures — without prior human research.

The common denominator: agents make decisions based on structured, machine-readable data. The quality of that data directly determines the quality of the decisions.

How Autonomous Commerce Systems Work Technically

A procurement agent runs through several processing steps before making a decision. Understanding these steps is a prerequisite for building suitable enterprise system architecture.

Step 2 — validation — is the critical point for understanding agentic commerce. Agents do not assess whether a supplier makes a good first impression. They check whether the underlying data is consistent, complete, and machine-readable. Inconsistent or missing structured data leads to exclusion — not a downgrade that can be offset by other signals.

This mechanism is technologically deterministic: a dataset is either valid or it is not. Intermediate states do not exist in the automated processing path.

Enterprise System Architecture in the Context of Agentic Commerce

Most enterprise systems were built in an era when human actors were the recipients of digital information. Web presences were optimized for readability, visual hierarchy, and persuasiveness. These requirements are irrelevant to autonomous agents.

What autonomous agents require instead is a consistent, machine-readable data architecture. This places concrete demands on enterprise system architecture:

• Consistent Entity Definitions: Every product, service, and the company itself must share the same machine-readable definition across all systems. Conflicting descriptions across ERP, CMS, and web presence produce inconsistent agent outcomes.
• Structured Markup by Standard: JSON-LD implementations following schema.org form the basis for machine processing. Proprietary data formats without public schemas cannot be utilized by external agents.
• Clean Data Topology: The hierarchical relationships between the company, products, pricing structures, and compliance documents must be explicitly modeled. Agents that cannot derive this structure from the data construct it from available fragments — with correspondingly unreliable results.
• Minimization of Processing Noise: Outdated JavaScript libraries, inconsistent HTML markup, and unreferenced data fragments increase processing complexity for machine systems. A lean, structured codebase improves processing quality.

The core problem with many enterprise systems is not technical failure but historically accumulated heterogeneity: different systems were introduced at different times with different standards and were never aligned to a common data semantic. For human users, this was tolerable. For autonomous agents, it is a structural obstacle.

A detailed analysis of these architecture patterns can be found in the article on the Frankenstein Stack in enterprise architecture.

Protocol Standards for Agentic Commerce

The infrastructure of agentic commerce is still evolving. Several actors are establishing protocol standards that define how agents interact with suppliers and how supplier identities are verified.

Vendor-Specific Protocols

PayPal, Visa, Mastercard, and Stripe have each announced their own agentic commerce initiatives. These include API standards for agentic payment authorization, delegated transaction permissions, and protocol-based merchant verification. The specific technical specifications of these initiatives are still partially in development.

Open Protocol Standards

Alongside vendor-specific solutions, open protocol standards are emerging. The Sovereign Validation Protocol (SOVP), documented in protocol documentation and public audit archives, defines a cryptographic mechanism for verifying digital corporate identities.

The technical core of SOVP is cryptographic integrity verification:

Psi_core = Verify(K_pub, sigma, H(JCS(M)))

K_pub  — public Ed25519 key, published via DNS TXT record
         (_sovp.yourdomain.tld)
sigma  — digital signature in the sovp-identity.json object
H(M)   — SHA-512 hash of the canonicalized identity metadata
         (canonicalization per RFC 8785 / JSON Canonicalization Scheme)

Result:
  Psi_core = 1  →  entity verified, data ingestion approved
  Psi_core = 0  →  integrity failure, connection terminated at ingress

The protocol allows companies to cryptographically sign their digital identity and publish it via the existing DNS system. Autonomous systems can independently verify this signature without relying on central intermediaries.

The technical specification, full protocol text, and reference implementation are available in the SOVP protocol document.

Practical Requirements: What Companies Should Audit

For companies looking to assess their infrastructure for agentic commerce compatibility, the following areas are relevant:

• Schema.org Implementation: Is the company represented as an Organization entity with consistent attributes (name, address, products, contact) in JSON-LD? Do these match the data in other channels?
• Product Data Consistency: Are products and services described in a machine-readable format with unique identifiers, valid pricing structures, and verifiable technical specifications?
• DNS Configuration: Are technical DNS records correctly configured, including fields usable by protocol-based verification systems?
• System Consistency: Do ERP, CMS, and web presence use the same product names, categories, and pricing models — or do diverging datasets exist across different systems?
• Technical Overhead: Does the codebase contain unreferenced scripts, outdated tracking implementations, or inconsistent markup that complicates machine processing?

These checkpoints can be systematically captured with a structured technical audit. The results identify which areas of the infrastructure already support agentic processing and where action is required.

For further detail on implementing deterministic signal architecture, see the article Understanding Deterministic Signal Architecture in Agentic Commerce.

Summary

Agentic commerce is not a future concept but an ongoing development. PayPal, Visa, Mastercard, and Stripe are actively implementing agent-driven commerce processes. The technical requirements of these systems differ fundamentally from those of classical search engines or human procurement workflows.

For enterprise companies, this translates into a concrete audit task: is the existing system architecture structured so that autonomous agents can reliably find, read, and validate the relevant data? The answer does not depend on marketing measures but on the structural quality of the underlying infrastructure.