x402commit/a note on agent tokenization

We bind an agent's x402 route into its on-chain identity at launch, route revenue through a splitbox into the vault that owns the agent, and let holders accrue from real cashflow.

Architecture: x402 payment routes from buyer through splitbox into the ERC-4626 vault that owns the agent NFT, with shares flowing to holders. Per-settlement attestations are written to the ERC-8004 ReputationRegistry. Buyer agent x402 payment Splitbox holder share Vault (ERC-4626) ERC-8004 agent NFT owned by vault, metadata locked shares holders

Today's agent tokens are not bound to revenue.

Most agent token launches are narrative-first. Token price moves, but agent revenue does not flow to holders by any cryptographic guarantee.

Operators can rotate wallets, swap endpoints, or run a shadow billing path off-chain. Marketplaces inherit the credibility risk of every launch they host.

The mechanism.

Tokenization only means something if the agent's revenue flow is enforced in code, observable on-chain, and gated by governance. The five mechanisms below do that.

  1. Endpoint pinned At launch, the agent's canonical gateway URL and payTo are written into protected ERC-8004 metadata. Buyer clients and marketplace resolvers check those fields before accepting a route.
  2. Vault owns the agent An ERC-4626 vault is the registered owner of the agent NFT. The vault exposes no operator-callable setter for protected metadata, and no NFT transfer function. The agent cannot leave the vault.
  3. Splitbox to vault The x402 payTo points to the splitbox. The splitbox pays the merchant, x402 facilitator, and marketplace shares to their recipients atomically, and routes the holder share to the vault that owns the agent. Revenue reaches the holder-backed vault before the operator can redirect it.
  4. Governance, not lock-in Endpoint, facilitator, and wallet rotations require stakeholder approval and a delay. The setup can adapt when it needs to, no party can change it alone, and the delay gives holders a window to exit before any change lands.
  5. Clients enforce The buyer client and the facilitator both read the protected metadata fields from chain and refuse to participate on any mismatch. The lock is enforced by both writer and reader.
Proof, per settlement

On each settlement the facilitator writes one ERC-8004 ReputationRegistry row tied to the agent NFT. Holders and marketplaces can audit revenue history from chain events and attestations.

What this gives marketplaces.

We are infrastructure, not a launchpad. Marketplaces keep their distribution, their ranking, their UX, their brand. We provide the tokenization track underneath, and the marketplace remains the canonical place where buyers discover and evaluate the agent.

Governance seat.

Marketplaces hold one of three multisig signers, alongside x402commit and the service provider. Endpoint and operator rotations cannot happen without you.

Standard launch flow.

One contract template for the vault, one metadata schema for the agent. Tokenized agents launch through the same path with no custom contract engineering.

Verifiable holder accrual.

Vault NAV per share moves with x402 revenue, and the on-chain attestation count is auditable per agent. Holders see real economic linkage from chain data, not narrated revenue.

Canonical discovery.

Marketplace ranking and reputation point buyers at the verified route, making the marketplace's distribution part of the economic lock.

For pilot inquiries, write to [email protected]·GitHub