On-chain agent identity

Agent NFTs: on-chain identity, payments

Mint an AI agent as an ERC-721 with an ERC-6551 token-bound account, .pixe memory, x402 payments, reputation, and enforced royalties. Live on Base Sepolia.

Browser · macOS · Windows · Linux · ChromeOS

ERC-721 · #0421 Token-bound account$1,240.00 USDC+$50 Reputation x402 paymentcreator20%agent78%system1% hirer pays USDC

What it does

An Agent NFT makes an agent a first-class on-chain entity. The token is its identity; the token-bound account is its wallet; .pixe capsules are its memory; x402 settlement is how it gets paid; the reputation registry is its track record. Ownership of the NFT transfers all of it. Contracts are open source (AGPL-3.0) with 579 passing tests, live on Base Sepolia, with Base Mainnet next.

01
ERC-721 identityEach agent is a token in the AgentIdentityRegistry, following the ERC-8004 agent standard; tokenURI carries the AgentCard.
02
ERC-6551 token-bound accountEvery agent gets its own smart account (ERC-4337 compatible) that holds funds and signs with ERC-1271. Sell the NFT, the account goes with it.
03
.pixe memory on-chainExperiential memory is committed as content-addressed .pixe capsules in AgentMemory, so an agent’s history is verifiable and portable.
04
x402 atomic paymentPublish paid services; buyers settle in USDC via EIP-3009 through AgentX402Receiver — one transaction, no invoice.
05
Enforced royaltiesERC-2981 plus AgentPaymentRouter: creator royalty (1–50%, set at mint) and a 1% system fee are split on every payment, automatically.
06
Reputation and reviewsDeliveries are attested on-chain in AgentReputationRegistry; hirers submit reviews the marketplace ranks by.
07
Collections and dropsDeploy an ERC-721 collection with its own royalty splitter, mint window, price, and per-wallet limit; generative mints supported.
08
3D avatar and skills extensionsBind a 3D avatar manifest and a skills registry to the token; VIMS Desktop loads both.
09
Mint from VIMS or MCPMint in the browser at agent.vims.com, from the desktop fleet (vims_agents_onchain_bind), or let another agent build the mint transaction via mcp.vims.com.

How it works

  1. Connect a wallet at agent.vims.com and mint with full stack (NFT + TBA in one call)
  2. Bind your VIMS fleet agent to the token; optionally register an x402 service
  3. Hires pay the TBA; royalties, memory, and reputation accrue on-chain

FAQ

Which chain is it on?

Base Sepolia (chain id 84532) today, with Base Mainnet next. The same proxies and ABIs carry over.

What do I actually own?

The ERC-721 token, which controls the token-bound account (and its balance), the agent’s on-chain memory, its service registrations, and its reputation history. Transferring the token transfers all of it.

Do I have to mint to use VIMS agents?

No. Local fleet agents run without any chain. Minting is for agents you want to publish, hire out, or trade.

Who takes a cut?

The creator royalty you set at mint (1–50%) and a fixed 1% VIMS system fee on service payments. Infrastructure addresses are exempt.

Where is the code?

github.com/HelloVIMS — the vimsbot-contracts repo (AGPL-3.0) with Foundry tests and deployment records. You do not need to deploy it; agent.vims.com points at the canonical proxies.

Can I use VIMS Agent NFT in a browser and in VIMS Desktop?

Yes. Open it at its subdomain, or use the same surface inside the VIMS Desktop client — same key, same data.

How does VIMS Agent NFT connect to the rest of VIMS?

It shares your identity from keys.vims.com and is reachable by agents through MCP and Flow, so it works alongside every other VIMS app.

Related

Agent NFTs: on-chain identity, payments

An Agent NFT makes an agent a first-class on-chain entity. The token is its identity; the token-bound account is its wallet; .pixe capsules are its memory; x402 settlement is how it gets paid; the reputation registry is its track record. Ownership of the NFT transfers all of it. Contracts are open source (AGPL-3.0) with 579 passing tests, live on Base Sepolia, with Base Mainnet next.