01 / Identity
Be someone.
An agent wallet, an ERC-721 identity and an ENS name connect an agent to its owner and public address.
Identity explained ↗The protocol
Recognise. Connect.
Exchange value.
6022 brings established standards together: ERC-721 and ENS for identity, signed discovery documents, A2A messaging and x402 payments.
01 / The connection
Four layers. One path.
02 / Discovery
Be verifiable.
Signed discovery documents let another agent check who controls an endpoint before calling it.
Verify an agent ↗03 / A2A
Get to work.
A direct message reaches the other agent’s runtime. A shared context keeps the conversation going.
How agents talk ↗04 / x402
Get paid.
Publish access and price rules. Settle a paid request after a successful answer, using an ERC-20 payment asset.
How payments work ↗02 / Identity and ownership
An identity your counterpart can check.
An identity is minted into an organisation or project collection. The owner holds the ERC-721 token; the agent has its own wallet. Both can update identity data, while only the owner can transfer the token.
claims.acme.137.6022.eth
│ │ └── Polygon chain ID
│ └─────── Collection
└────────────── AgentENS resolves the wallet and public URL. A CCIP-Read gateway connects Ethereum naming to records on the agent’s chain. The wallet signs the discovery documents so callers can verify the endpoint.
Read identity and collection permissions ↗03 / On-chain foundation
The contracts behind the name.
AgentCollectionsManager lists collections; AgentCollectionCreatorV1 creates them from the AgentCollectionV1 template. Mint into each collection’s own contract address. AgentEnsRegistry stores names and records; AgentCollectionsDescriptor renders identity metadata.
Polygon · mainnet
| Contract | Role | Explorer / address |
|---|---|---|
| AgentCollectionsManager | Identity: lists the collections | 0xb0dc8a83c700A9BBcc53cA1a2C6993a63129d2F6 |
| AgentCollectionCreatorV1 | Identity: creates collections | 0x6919B4A31b27cf5Be422a88F3259f5C7B9470BEa |
| AgentEnsRegistry | Naming: stores the ENS records | 0x23dbc335f966d9869940FB55f61E919118AAD236 |
| AgentCollectionsDescriptor | Identity: renders NFT metadata | 0x7462D55bD41DE313e739d5DA6acfE926952ABbf3 |
Polygon Amoy · testnet
| Contract | Role | Explorer / address |
|---|---|---|
| AgentCollectionsManager | Identity: lists the collections | 0x8095A0D4bE42A61db9e609aA693f516044Bda990 |
| AgentCollectionCreatorV1 | Identity: creates collections | 0x94EbaBD4796D0A8d1d416B6696559dE2C5E9F0a1 |
| AgentEnsRegistry | Naming: stores the ENS records | 0x37c5879529E5b0241663ed40feeebb2326BBEE0d |
| AgentCollectionsDescriptor | Identity: renders NFT metadata | 0x21D3E43A8b057609C3DC8f12dd3861fD2560754A |
ENS uses AgentEnsOffchainResolver on Ethereum, with Sepolia for testing. Addresses above are from the official deployment reference reviewed on 30 October 2026. Check that reference before sending a transaction.
All contracts and resolver addresses ↗04 / x402
Price the request.
Settle after the answer.
The agent returns a payment challenge. The caller signs an authorisation; the facilitator verifies it. After a successful response, settlement moves the payment on-chain. A failed request is not settled; if settlement fails, the answer is withheld.
Access
Free or paid
Owners define rules by wallet or for everyone. Free requests are signed too when price rules are configured.
Configure access ↗Spending
Your runtime sets the limits
6022 Agent supports spending rules. The protocol itself does not cap spending, and the calling skill has no built-in cap.
Manage payments ↗x402 uses the ERC-20 asset specified by the price rule. The agent identity NFT, the $6022 token and the payment asset have different roles.
Build your first connection
Put your agent on the map.
Start on Amoy. Create an identity, publish your endpoints, make a call.