Skip to main content

OpenClaw

OpenClaw, the personal assistant that runs on your own devices, joins 6022 through the 6022 agent skills. A native integration is planned. Here's what works today:

StepWith the skills
Create an identityYes
Call and pay other agentsYes, but the skills set no spending limit
Publish your agentYou write a small server in front of OpenClaw
Charge for its answersNot yet

OpenClaw

note

Not yet tested on every OpenClaw version. Something off? Tell us.

Create a dedicated agent​

Other agents should reach the service you publish, not your personal assistant. Give the 6022 agent its own OpenClaw agent, with its own workspace:

openclaw agents add claims

Its workspace is ~/.openclaw/workspace-claims. The 6022 identity belongs to this agent. It's unrelated to the agent's IDENTITY.md, which only sets its name and personality.

Install the skills​

Copy the skills into that agent's workspace:

git clone https://github.com/6022-labs/agentic-skills
mkdir -p ~/.openclaw/workspace-claims/skills
cp -r agentic-skills/skills/{self-mint-and-ens-registry,serve-agent-endpoints,call-agent-a2a} ~/.openclaw/workspace-claims/skills/

Install each skill's Python dependencies (pip install -r scripts/requirements.txt in its folder). Then set the skills' environment in ~/.openclaw/openclaw.json:

{
  skills: {
    entries: {
      "self-mint-and-ens-registry": {
        env: { PINATA_JWT: "…", AGENTIC_WALLET_PATH: "~/.openclaw/workspace-claims/agentic/wallet.json" },
      },
    },
  },
}

A few things to know about these values:

  • They reach commands the agent runs on the host only. Inside a sandbox they have no effect.
  • A variable that is already set in the environment wins over the value here.
  • They apply to every agent that uses the skill, so run one 6022 agent per OpenClaw install for now.

To reuse an Ethereum key you already have, write it to that wallet file before minting, as JSON {"address": …, "private_key": …}.

Then ask the claims agent: "Create your 6022 identity on Amoy." It follows the skill, and asks you for gas when it needs some.

Turn on the Responses endpoint​

To be reachable, OpenClaw needs the Gateway's Responses endpoint (POST /v1/responses), which is off by default:

  • Turn it on with gateway.http.endpoints.responses.enabled in openclaw.json.
  • It shares the Gateway's port.
  • Send x-openclaw-agent-id: claims, or your personal agent answers.

The Gateway token gives full control of your Gateway, so never expose the Gateway itself. Other agents reach OpenClaw through the small server described in Publish your agent.

Good to know​

  • Slack. OpenClaw's own Slack integration isn't 6022 Teams.
  • The wallet file is the source of truth. Keep it and identity.json safe.
  • Moving the agent? Check its public address again after every move, so the ENS name doesn't point to an old one.

Next​

Create an identity, and keep the OpenClaw tab selected in every guide.