XAgent is the open execution market for Agentic Commerce. It turns merchant products, pricing, inventory, order logic, settlement, and fulfillment capability into commerce interfaces that AI agents can read, call, and purchase from. Agents quote, authorize, settle, fulfill, and prove the purchase — machine-to-machine.

What is agentic commerce?

Agentic commerce is a model where AI agents — not humans clicking through web pages — discover services, place orders, and settle payments autonomously. XAgent makes this real through five execution pillars: Quotable, Authorizable, Settleable, Fulfillable, Provable.

How is XAgent different from Stripe or Coinbase Commerce?

Stripe was built for humans clicking checkout buttons. Coinbase Commerce is a crypto payment gateway. XAgent is the protocol-native execution market where AI agents transact: protocols standardize the request, XAgent operationalizes the transaction. The moat is merchant operations — catalog, quote, authorization, order, settlement, delivery, receipt, refund, reconciliation, fraud signal, jurisdiction metadata.

How do AI agents pay merchants on XAgent?

Agents pay using the x402 protocol — an HTTP 402 challenge/response standard. The agent receives a signed payment instruction, authorizes a stablecoin transfer (USDG or USDT) via EIP-3009, and the merchant is paid in seconds with zero gas fee to the buyer (OKX facilitator covers it).

Do I need to write code to list my store?

No. One-click OAuth in your Shopify or WooCommerce admin turns your store into a merchant capability that AI agents can quote, order, pay, settle against, and prove — zero code, zero contracts.

Why agentic commerce needs an open execution market

AI agents can decide what to buy. They cannot yet execute the purchase end-to-end: discover the merchant, get a real quote, authorize against policy, settle on a stable rail, fulfill, and produce a receipt that audits. XAgent is the operations layer for that gap.

By XAgent Team · 2026-06-03

The protocol layer is forming fast

There is now a serious stack of standards around agentic commerce. Four speak directly to buying: UCP (Google and Shopify, with a 20+ company coalition), ACP (OpenAI and Stripe), AP2 (Google), and x402 (the Linux Foundation's HTTP-402 payment standard). Two more — MCP and A2A — are general agent-interop layers that the commerce protocols compose against rather than commerce standards in their own right. None of them, on their own, is enough to actually execute a purchase.

What protocols specify

Protocols specify the interaction:

how an agent asks for a quote
how a merchant offers terms
how a payment is signed
how the receipt is shaped
and, in UCP's case, how order status, shipment tracking and returns are reported back

What they do not do is run any of it. They do not onboard the merchant. They do not check compliance. They do not move money. They do not independently verify that a reported shipment actually left the warehouse. That is operations work — and it is not glamorous, but it is what makes a market real.

The execution gap

XAgent operates that layer. We match each scenario to the right protocol path, normalize quotes across rails (X Layer mainnet for USDG and USDT0, Circle's Arc testnet for USDC), and close the loop with verifiable fulfillment proof.

The brand stance is straightforward: protocol-native, not protocol-limited.

Where this goes

As more agents go live and more merchants list, the operations layer becomes the moat. Anyone can implement a protocol spec. Few teams can operate one across rails, currencies, and compliance regimes — and even fewer can do it for AI agents that expect millisecond-scale quotes and end-to-end provability.

That is the work we are choosing to do.

Correction (2026-08-05): this post originally listed MCP and A2A alongside UCP, ACP, AP2 and x402 as standards that each "describe part of what it means for an agent to make a purchase". Neither specifies anything about purchases, quotes, payments or receipts — MCP is a tool/data connection standard and A2A is an agent-discovery and task-delegation protocol; the commerce protocols compose against them. We also noted that UCP does standardise order status, shipment tracking and returns, and corrected the token name on X Layer (USDT0).