Skip to main content
“Pairing” means the agent gets an API key and knows how to use it. There are three paths.

​
Path A: Manual pairing

The builder copies the API key from the dashboard and configures the agent directly.
  1. Create an agent in the dashboard → copy API key
  2. Configure the agent:
    • Terminal: npx @xwell/cli pair --key well_ak_...
    • OpenClaw: openclaw xwell configure well_ak_...
    • MCP: Add to config file with XWELL_API_KEY env var
Best for: getting started quickly, single agents.

​
Path B: CLI-assisted pairing

The agent initiates pairing. The builder approves in the dashboard.
1

Agent requests pairing

npx @xwell/cli pair --name "research-agent"
Returns a pair token and approval URL.
2

Builder approves

Opens the approval URL in their browser. Selects wallet, sets spending limits, approves.
3

Agent polls for approval

npx @xwell/cli pair --poll --token TOKEN
Once approved, the API key is saved automatically.
Best for: when the agent is already running and the builder wants to approve with full control over limits.

​
Path C: Pre-provisioned pairing

For teams deploying multiple agents. Create agents in bulk via the dashboard, distribute keys through environment variables or secret managers. 
Builder creates agents in dashboard:
  → Agent 1: well_ak_aaa... (5 USDC/day, EVM only)
  → Agent 2: well_ak_bbb... (50 USDC/day, both chains)
  → Agent 3: well_ak_ccc... (1 USDC/day, marketplace only)

Distributed via:
  → Environment variables
  → Secret manager (Vault, AWS Secrets)
  → .env files in deploy configs
Best for: teams, CI/CD pipelines, multi-agent deployments.