If you build for AI agents that move value, the last two weeks were a lot to keep up with. Five separate pieces of the agent-commerce stack shipped or hardened, from a payments standardization body down to a new escrow standard. That is genuine momentum, and it is worth reading as a whole rather than as isolated headlines.
So here is the map. For each layer I will note what it does well and where it stops - because the gaps tell you what is still missing more clearly than the wins do.
1. Rails: x402 became a Linux Foundation standard
On July 14, 2026, the Linux Foundation announced the operational launch of the x402 Foundation - an open-governance body to steward the x402 protocol, an open standard for payments over HTTP. The protocol, originally contributed by Coinbase, lets agents, APIs, and applications send and receive payments as easily as they exchange data.
The membership list is the story: 40 members, with premier names including Adyen, AWS, American Express, Circle, Cloudflare, Coinbase, Fiserv, Google, Mastercard, Monad, MoonPay, Ripple, Shopify, Solana, Stellar, Stripe, and Visa. When Visa, Stripe, and a cloud provider all sit on the same payments board, the "how does an agent pay for something" question is effectively being answered in public.
What it does well: standardizes agent payment initiation over HTTP. Fast, cheap, vendor-neutral.
Where it stops: x402 moves one asset, one direction - most volume settles a single stablecoin on a single chain. That is a payment, not a trade. Paying is "I send you USDC." A trade is "I send BTC, you send ETH, and neither of us can run off in the middle."
2. Wallets: Phantom shipped an agent MCP
Phantom released a wallet MCP that gives an AI agent a signer across Solana, Ethereum, Bitcoin, and Sui. The tools are what you would expect: get addresses, sign a message, sign a transaction, transfer tokens, buy a token. An agent reasoning with an LLM can now hold its own keys and move its own funds across four chains.
What it does well: the key-custody layer. An agent no longer needs a human to sign for it.
Where it stops: a wallet that signs a swap is not a protocol that settles a trade. The signer executes whatever transaction it is handed. It does not guarantee that the counterparty's leg completes atomically with yours. Signing is necessary; it is not settlement.
3. Marketplaces + escrow: OKX moved the business loop in-exchange
OKX's Agent Payments Protocol wraps quotes, negotiation, metering, a payment SDK, and - on the roadmap - escrow and dispute resolution into one package on its X Layer chain, working across Base, Solana, and Ethereum. It is the most complete single-vendor "business loop" for agents so far.
What it does well: one SDK for the whole commercial interaction. Convenient by design.
Where it stops: it is custodial and exchange-owned, and the escrow + dispute pieces are still marked "coming soon" rather than shipped. Convenience through a single venue is a real pull, but it reintroduces exactly the intermediary that trust-minimized settlement is meant to remove.
4. Identity + commerce: ERC-8004 and ERC-8183 advanced
Two Ethereum standards are maturing in parallel. ERC-8004 gives agents portable identity and reputation. ERC-8183 proposes escrow-with-an-assessor for agent commerce - a neutral third party who adjudicates whether a deal completed. Together they sketch an "identity + commerce" pair for the agent economy.
What they do well: solve the "who am I dealing with, and who decides if the deal went through" problem.
Where they stop: an assessor is a trusted party. Useful when the exchange is subjective (was the work good?), but for a pure asset-for-asset swap you do not need a judge if the settlement itself is atomic. A hash-time-lock contract makes the swap all-or-nothing by construction - no assessor required.
5. The primitive itself: a second team is running agents on atomic HTLC swaps
The most validating signal is not from us. A second team is now running an AI agent that executes atomic HTLC swaps non-custodially - the exact hash-time-lock primitive our protocol is built on. Two independent teams, same bet: the settlement layer for agents is a trust-minimized atomic swap, not a custodial hold.
The one layer nobody standardized
Line the five up and a single thread runs through them. At the moment of settlement, either someone holds the money or you trust someone who does - a bridge, a custodian, an exchange, an assessor.
The open seat is this: two agents, two different assets, two different chains, two strangers - and a guarantee that no one can walk off mid-trade. That is atomic settlement, and it is the layer none of the five above actually deliver.
Here is the mechanism, in one paragraph. Both legs of the trade are bound to a single secret through a hashlock H = SHA-256(secret). Claiming one leg reveals the preimage, which is exactly what is needed to claim the other. A timelock refunds each side if the trade never completes. No wrapped assets, no custodian holding the gap, no assessor deciding who was right - the math makes it all-or-nothing.
The honest status, because chain-claim discipline matters: this is live on Ethereum mainnet today. Bitcoin is validated on signet with mainnet pending. Sui contracts are deployed and CLI-tested with gateway wiring in progress. Rails ready, more trains coming - and we will only ever call a chain live when it actually is.
Why this framing, not "we compete with all of them"
We do not. x402 is how an agent pays; our layer is how two agents swap. Phantom holds the keys; we settle the trade those keys sign. ERC-8004 says who the counterparty is; we make sure the swap with that counterparty is atomic. Almost every layer above is complementary. The one thing missing across all of them is a settlement primitive that never has to trust an intermediary at the exact moment value changes hands.
PayPal made it safe to pay strangers online. The agent economy now has most of a stack for agents to pay each other. The piece still being written is the one that makes it safe for two agents to trade with each other - where your money never leaves your wallet until theirs arrives.
Protocol and tools: hashlock.markets · MCP server: @hashlock-tech/mcp (scoped) · Method and design: hashlock.markets/methodology · Academic foundation on SSRN.
Of the five layers above, which one do you think gets standardized last - and would you rather your agent settle through an assessor or through math that cannot be argued with?
Top comments (0)