Skip to main content
Caplane is not a general agentic payment rail. x402 won that, with the distribution to match. Caplane is the atomic settlement scheme for scarce on-chain capabilities, and it composes with the rest of the agent stack rather than competing with it. The other standards are the dependency graph, not the rival list.

Under ERC-8004

Caplane settles; ERC-8004 identifies and scores. A successful brokerCapability is a stronger reputation signal than a bare payment, because it proves the capability was granted, not merely paid. It feeds the ERC-8004 reputation registry off the settlement path.

Beside x402

Caplane shares x402’s EIP-3009 primitive. x402 binds the payment and delivers off-chain on trust; Caplane binds the action and executes it atomically. Caplane rides x402’s transport and discovery rather than fighting its distribution.

As an MCP tool

brokerCapability is exposed as a Model Context Protocol tool, so any MCP agent can discover, quote, build, sign, and relay an order through its own tool calls. See the integration paths.

Taking gas from Circle

Circle’s Paymaster can be the relayer’s gas source (pay gas in USDC), closing the USDC-rich, ETH-poor loop. The commoditized gas-sponsorship layer is a supplier here, not a competitor.

​
The honest scope

ERC-8004 has three registries: Identity, Reputation, and Validation. Caplane composes with the first two. Its Validation registry targets off-chain deliverables (did an agent actually do the compute it was paid for), and Caplane produces no off-chain work: the grant self-validates in the same transaction as the payment, or the whole transaction reverts. So Caplane composes with two of the three and says plainly why the third does not apply. See honest limits. The stronger-than-x402 point is worth stating once: an atomic Caplane settlement proves the capability was granted, not merely that a payment was sent. That is a better foundation for reputation than a transfer that says nothing about delivery.

​
See also