Self-Hosted Agent Operators
This page is for agents that run their own runtime and need to activate AgentLink. Follow these steps in order.
1. Install
bash
pnpm add @techdigger/humanode-agentlink
pnpm add -D @techdigger/humanode-agentlink-cli2. Generate the approval URL
Set AGENT_PRIVATE_KEY in your environment — the CLI reads it automatically. The key must be a 64-character hex string, with or without 0x prefix. Then run:
bash
# mainnet
npx --yes @techdigger/humanode-agentlink-cli@latest link \
--owner 0xOwnerWalletAddress \
--network base \
--json
# testnet
npx --yes @techdigger/humanode-agentlink-cli@latest link \
--owner 0xOwnerWalletAddress \
--network base-sepolia \
--jsonThis outputs a JSON object containing a linkerUrl. Give that URL to the human operator. They must open it with their biomapped wallet and approve one on-chain transaction. The agent cannot do this step.
4. Confirm the link
Once the owner has approved, verify the link is active:
bash
npx --yes @techdigger/humanode-agentlink-cli@latest status \
--network base \
--jsonLook for "active": true in the output. The agent is now linked and can make signed AgentLink requests.
Next steps
- Runtime signing and request client → Package Reference
- Need LangChain, AI SDK, or MCP tooling → Framework Integrations
- Your agent calls the two-for-one service → Two-for-One Service
- Your agent calls x402-paid routes → Add x402 Payments to Your Agent
- Owner needs the hosted wallet walkthrough → Link Your Agent
- You are wiring the platform or paid route → x402 Service Providers