Syndicate Links

Agentic Commerce Infrastructure

Agentic commerce is the economic activity conducted by autonomous AI agents on behalf of humans. It encompasses discovery, evaluation, recommendation, payment, and settlement—all executed by software without requiring human interaction at each step. The infrastructure enabling this new commercial paradigm consists of four interdependent layers: payments, identity, attribution, and settlement. Syndicate Links provides the attribution layer that connects agent activity to economic outcomes.

The Agent Commerce Stack

The traditional e-commerce stack was designed around a human sitting at a browser. Product pages are rendered as HTML. Tracking relies on cookies. Payments require checkout flows with CAPTCHA, 3D Secure prompts, and confirmation screens. Every layer assumes a human is present.

The agent commerce stack replaces each of these assumptions with machine-native equivalents:

LayerHuman CommerceAgent Commerce
DiscoveryGoogle Search, social media, adsAPI queries, MCP servers, tool use
EvaluationReading reviews, comparing pagesStructured data analysis, multi-source reasoning
IdentityBrowser cookies, login sessionsCryptographic agent keys (aff_agent_ credentials)
AttributionCookie-based publisher trackingSigned attribution tokens (slat_v1 / SLAT)
PaymentCheckout pages, card formsx402 protocol (HTTP-native payments)
SettlementMonthly publisher payouts via wire/PayPalProgrammatic settlement (on-chain or fiat rails)

Each layer in the agent commerce stack is designed to be stateless, cryptographically verifiable, and executable without browser rendering. This is not an incremental improvement on the existing e-commerce stack. It is a parallel architecture built for a different class of economic actor.

Payments: The x402 Protocol

The payment layer of agentic commerce is built on the x402 protocol, an open standard under the Linux Foundation with backing from Coinbase, Stripe, Google, Visa, and Mastercard. x402 activates the long-reserved HTTP 402 status code to enable protocol-native payments.

When an agent requests a paid resource, the server returns 402 Payment Required with a structured payment request. The agent evaluates the cost, executes payment via the appropriate rail (crypto or fiat), and retries the request with a payment proof. The entire flow is HTTP request-response—no redirects, no JavaScript, no checkout pages.

x402 is payment-rail agnostic. It supports on-chain settlement via stablecoins (USDC on Base is the most common), traditional card network tokens via Stripe, and other payment methods as they are added to the specification. This agnosticism is critical because agent commerce needs to work across the full spectrum of merchants, from crypto-native API providers to traditional retailers.

The significance of x402 is not just technical. It represents a consensus among the largest payment companies in the world that machine-to-machine payments need a dedicated protocol. The era of wrapping human checkout flows in automation scripts is ending. Protocol-native payments are the replacement.

Identity: Agent Credentials and Keys

Every participant in the agent commerce stack needs a verifiable identity. For AI agents acting as publishers—recommending products, comparing services, routing users to merchants—this identity is established through cryptographic credentials rather than browser sessions.

Syndicate Links issues aff_agent_ keys to publisher agents. These keys serve as the agent's persistent identity across all interactions with the attribution system. Unlike browser cookies, agent keys are:

  • Deterministic: The same agent always presents the same key, regardless of which server it connects to or which network path it takes.
  • Verifiable: Merchants and the attribution system can cryptographically verify that a key belongs to a registered publisher agent.
  • Stateless: No session needs to be maintained. The key is presented with each request and verified independently.

Agent identity is the prerequisite for attribution. Without a verifiable way to identify which agent drove a transaction, there is no way to distribute commissions. The aff_agent_ key system provides this identity layer without depending on any browser-based mechanism.

Attribution is the layer that answers the question: which agent caused this transaction to happen? In human commerce, this question is answered by cookies, redirect chains, and pixel tracking. In agent commerce, it is answered by signed attribution tokens.

When a publisher agent generates a recommendation—whether through a conversational response, an API call, or a structured data output—it creates a slat_v1 token. SLAT stands for Syndicate Links Attribution Token. The token is generated using HMAC-SHA256 and contains:

  • The publisher agent's aff_agent_ key
  • The merchant identifier
  • The product or service identifier
  • A timestamp
  • A cryptographic signature that proves the token was generated by a legitimate publisher agent

This token accompanies the recommendation through whatever path the transaction takes. If payment occurs via x402, the SLAT token is embedded as an atxp_reference in the payment proof. If payment occurs through a traditional flow, the SLAT token can be passed as a query parameter or header.

The critical difference between SLAT-based attribution and cookie-based attribution is verifiability. A SLAT token is a cryptographic proof. It cannot be forged, it cannot be replayed (timestamps prevent this), and it does not depend on client-side state that users can clear or block. It works identically whether the transaction is executed by an AI agent, a browser, or an API client.

Settlement: Closing the Loop

Settlement is the final layer—the actual movement of money from merchant to publisher agent. In traditional publisher networks, settlement happens on a monthly or bi-monthly cycle. Merchants report conversions, the network validates them (often with a 30-90 day attribution window), and funds are distributed via wire transfer or PayPal.

In agent commerce, settlement can be significantly faster. Because attribution is cryptographic rather than probabilistic, there is no ambiguity about which agent drove which transaction. The SLAT token embedded in the x402 payment proof provides a deterministic record. This enables:

  • Real-time commission calculation: The merchant knows at the moment of payment exactly what commission is owed and to whom.
  • Programmatic settlement: Commissions can be distributed automatically via the same payment rails used for the primary transaction—on-chain stablecoin transfers or automated fiat payouts.
  • Transparent audit trails: Every attribution claim is backed by a cryptographic proof that both parties can independently verify.

Settlement in the agent commerce stack is not a separate reconciliation process. It is an extension of the payment flow itself. The same transaction that pays the merchant can simultaneously distribute the publisher commission, because attribution data is embedded in the payment rather than tracked in a separate system.

How the Pieces Fit Together

A complete agent commerce transaction flows through all four layers in sequence:

  1. A user asks their AI agent to find the best project management tool for their team.
  2. The agent queries multiple sources, evaluates options, and selects a recommendation. The recommending agent is a publisher—it creates value through curation and analysis.
  3. The agent generates a slat_v1 attribution token encoding its aff_agent_ key and the merchant details.
  4. The agent initiates a purchase or trial signup via the merchant's API. If the merchant supports x402, the SLAT token is embedded in the atxp_reference field of the payment proof.
  5. The merchant's server validates both the payment and the attribution in a single step.
  6. The publisher agent's commission is calculated and queued for settlement—either instantly via on-chain transfer or on a standard payout cycle.

No browser was opened. No cookie was set. No redirect chain was followed. No pixel fired. The entire transaction—from discovery to settlement—was executed by software, verified by cryptography, and settled programmatically.

This is the agentic commerce infrastructure stack. It is not a future concept. It is the infrastructure being built and deployed now, as AI agents become the primary interface between consumers and the commercial internet.