1
Sign-In
2
Mode
3
ENS Name
4
Capabilities
5
Generate Key
6
ENS Records
7
SDK + Card
8
Summary
Step 1 of 8
Connect wallet
Connect an Ethereum wallet to authenticate the activation request. Your wallet signs the login message. Your Ed25519 key signs agent receipts later.
Supported browser wallets include MetaMask, Rabby, Coinbase Wallet, and other EIP-1193 wallets.
Status: Not connected
CommandLayer only checks ENS identity data for namespace activation. It does not scan token balances or unrelated wallet assets.
Owned does not mean record-writing control has been verified. Control verification happens during activation.
Step 2 of 8
Choose activation mode
How should your capability agents be structured? All three modes produce verifiable agents with signed receipts — the difference is where the namespace lives.
CommandLayer namespace
Activate under CommandLayer's canonical capability classes. Protocol-native, standardized routing, no additional ENS required.
commandlayer.approveagent.eth
Your ENS namespace
Generate verb sub-agents under your own ENS name. Best for enterprises and teams wanting sovereign identity.
approve.commandlayer.eth
Single agent
Attach all capabilities directly to your ENS name. Simplest setup, best for solo agents with one primary capability.
commandlayer.eth
Agent names that will be generated
Step 3 of 8
Namespace setup
This is your organization or agent identity used for namespace generation.
Use 3-32 lowercase letters, numbers, or hyphens; no .eth; cannot start/end with hyphen.
Used for subnames under CommandLayer canonical parents.
Select up to 10 canonical parents.
CommandLayer namespace mode creates subnames under CommandLayer-controlled canonical parents, such as commandlayer.approveagent.eth. It does not grant ownership of approveagent.eth.
Step 4 of 8
Generate your signing key
One Ed25519 keypair signs receipts across all your capability agents. Generated in your browser — never sent to any server.
Browser-side key generation
Your private signing key is generated locally and is never sent to CommandLayer. Download it immediately — it cannot be recovered after you leave this page.
Ed25519 browser support varies. If generation fails, CommandLayer will not substitute another algorithm.
kid—
pub—
⚠️
Download your private key now. This is the only time it will be shown. Store it as CL_PRIVATE_KEY_PEM in your environment — never in source control, never upload it to CommandLayer.
Step 5 of 8
ENS records
Add these records to your ENS name in ENS Manager.
Agent namespaces generated
| Agent name | Capability verb | Runtime path |
|---|
ENS TXT Records
—
Activation record instructions:
Publish the four records with your ENS owner wallet, then verify records.
Private-key safety:
Your private signing key is generated locally and is never sent to CommandLayer.
Managed namespace:
Managed ENS publication automation is pending activation infrastructure. This PR stores the public TXT package for operator review but does not perform onchain ENS writes.
Publish the four records with your ENS owner wallet, then verify records.
Private-key safety:
Your private signing key is generated locally and is never sent to CommandLayer.
Managed namespace:
Managed ENS publication automation is pending activation infrastructure. This PR stores the public TXT package for operator review but does not perform onchain ENS writes.
1. Manual
Download records and add them yourself in ENS Manager.
2. Assisted
Connect wallet and let CommandLayer prepare the subname + TXT record transactions. User signs. Coming next.
3. CommandLayer-native
Activate under CommandLayer capability namespaces like commandlayer.approveagent.eth. CommandLayer provisions after payment. Coming next.
No wallet connection is required to generate this package.
Wallet connection is required to write records under your ENS name.
Payment/provisioning is required for CommandLayer-native namespace activation.
Wallet connection is required to write records under your ENS name.
Payment/provisioning is required for CommandLayer-native namespace activation.
Step 6 of 8
SDK configuration
Copy this into your agent codebase. One keypair, one SDK config, works across all your capability agents.
Install
npm install @commandlayer/agent-sdk
SDK Config
—
Wrap an action
—
Step 7 of 8
Agent card preview
Preview of the first agent card in your namespace. When paid provisioning is live, all cards will be hosted automatically at commandlayer.org.
—
activation preview
—
Step 8 of 8
Activation package ready.
Your package is generated. Complete the checklist below to go live.
Keypair generatedEd25519 private key downloaded · Public key ready for ENS
Agent namespaces generatedSub-agent names ready
ENS records generatedCopy into ENS Manager to bind keys and capabilities on-chain
SDK config generatedDrop into your codebase with CL_PRIVATE_KEY_PEM in env
Agent card generatedMachine-readable identity record ready to host or submit
Add ENS TXT recordsCreate subnames and paste records into ENS Manager
Payment & provisioningComing next — ERC-8004 registration on Base, hosted agent cards, and verified live receipts
Starter
Free
Generate activation records and prepare for review.
Builder
$99/mo
Activation support, metadata, and verification routing.
Protocol Partner
$499/mo
10-agent pack, expanded capabilities, integration support.
Enterprise
Custom
Custom namespaces, compliance, and registry support.
Checkout is not enabled in Session 1. Pricing covers activation, metadata, verification routing, and integration support — not ENS ownership transfer.
Activation pipeline
Submit a claim to load persisted payment, ENS, IPFS, genesis, and tenant proof status.
Returning to an existing claim? Import your private Claim Recovery Key file to restore access in this browser session.