aCommerce: The Fourth Platform Shift.

I needed a name for what I saw coming, so I made one. I call it aCommerce. The “a” is for agent. eCommerce digitized the store but kept a human shopper. In aCommerce the buyer is an agent acting under a person’s mandate. It searches, negotiates, pays and settles, often with another agent on the other side.

Two shifts arrive together. AI gives software judgment. Blockchain gives software proof. Combined, they make a decision that can be verified. I have built inside three platform shifts. I believe this fourth one can become as large as eCommerce, or larger.

Plain versus trusted

Everybody is talking about agentic commerce now. My focus is trusted agentic commerce. The difference is identity. In trusted aCommerce, an agent has an identity tied back to a real person or business.

Plain aCommerce

The agent can pay. The merchant cannot tell whose agent it is or whether the purchase is allowed. So it refuses, or a human gets pulled back in to vouch, and the point of the agent disappears.

Trusted aCommerce

The agent carries proof of its owner, its limits and its payment. The merchant learns what the sale requires and nothing more.

The rails are being laid

The largest players have started building. Visa and Mastercard announced agent payment programs in April 2025. In September 2025 Google introduced the Agent Payments Protocol, AP2, which uses cryptographically signed mandates as proof of a user’s instructions: an intent mandate that sets the rules of engagement, such as price limits and timing, and a cart mandate that records the exact items and price. These are the signals of an infrastructure phase.

Payment protocols for agents already exist. Trust does not. This isn’t a crypto problem. It is a commerce problem. Every earlier shift changed how we transact. None changed the price of trust itself. This one can. That is a belief, not a forecast. The pace is uncertain. The direction is not.

Get ready for agent buyers

1. Draw the lineList the purchases you would let an agent make for you today and the ones you would not. For each no, write the proof, limit or oversight that would change it.
2. Ask who stands behind the buyerIf you sell, decide what you need to verify about an agent before you accept its order: an owner, a policy, good funds.
3. Build in the four requirementsEvery agent you deploy gets an owner, limits, an audit trail and a kill switch from day one.
4. Start nowThese requirements are design work, not reasons to delay. Every quarter you wait goes to someone who did not.