The user identifies a gap in x402 for transactions that involve time between payment and delivery, requiring escrow, state machines, dispute windows, and delivery proofs. They built ACTP to address this, suggesting x402 could benefit from or integrate with such 'commerce protocols' for more complex agent-to-agent work.
x402 is one of the most elegant things to come out of the Base ecosystem - a missing internet primitive that lets agents pay for access using HTTP 402 + USDC. Clean, stateless, composable. But it's designed to stop at access. And that's a feature, not a limitation. I've been building agent infrastructure on Base and realized the full agent commerce landscape actually breaks into four distinct layers. x402 is the foundation, but there's a lot more above it. **Layer 0 - Payment triggers (x402):** Agent hits endpoint → gets 402 → pays USDC → retries → gets response. Stateless, no new token, HTTP-native. Perfect for API access, data, bounded compute. This is where Base already leads. **Layer 1 - Payment wires:** Agent-to-agent direct transfers. One agent pays another for a discrete service. Minimal coordination. Skyfire and Nevermined are building here - Nevermined already has an x402 smart-account extension. **Layer 2 - Commerce protocols:** This is where we're building (AGIRAILS, live on Base mainnet). When an agent hires another agent for work that takes hours, not milliseconds, you need more than a transfer: * USDC escrow locked in a vault contract * State machine: INITIATED → COMMITTED → IN\_PROGRESS → DELIVERED → SETTLED * Delivery proofs via EAS attestations * Dispute windows before settlement finalizes * Replay protection (nonce-based transaction IDs) The moment you add escrow, you introduce time. Time introduces states. States introduce invariants. And once you have invariants, you've crossed from "payments" into "protocolized commerce." **Layer 3 - Orchestration:** The AI reasoning layer that decides what to buy and from whom. It consumes L0-L2. The beauty of Base for this stack: x402 gives you L0 natively. USDC is the settlement asset across all layers. Smart Wallets (ERC-4337) batch the escrow flow into single transactions. And Base fees are low enough that the commerce layer overhead stays under a cent per state transition. I wrote a full essay mapping these layers, the design boundaries between them, and why there won't be one protocol to rule them all. Link is in the first comment. What layer are you building at?