Connect OpenClaw to AdKit

OpenClaw on your own machine. Sign in through the browser, no API key needed.

1. Install the CLI:

   npm i -g @adkit/cli
   

2. Sign in. This opens your browser to sign in to AdKit:

   adkit setup
   

3. Give OpenClaw this prompt to confirm the connection:

   Help me set up AdKit.
   
   1. Run `adkit status` to confirm AdKit is connected.
   2. Run `adkit checkin --agent openclaw`.
   
   Tell me if AdKit is connected and ready. If not, tell me what failed.
   

On a server there is no browser to sign in with, so use an API key.

1. Create a key. Open Devices & Keys in AdKit and create an API key. It is shown once, so copy it right away.
2. Set the key in the environment where OpenClaw runs:

   export ADKIT_API_KEY=adk_your_key
   

   
   Set it in the service or daemon config so every run picks it up.
3. Install the CLI:

   npm i -g @adkit/cli
   

4. Give OpenClaw this prompt to confirm the connection:

   Help me set up AdKit.
   
   1. Run `adkit status` to confirm AdKit is connected.
   2. Run `adkit checkin --agent openclaw`.
   
   Tell me if AdKit is connected and ready. If not, tell me what failed.
   

Keep the key in the environment, not the chat. The CLI reads ADKIT_API_KEY from where OpenClaw runs, so the key never lands in your transcript.

Prefer MCP? Add the AdKit server in OpenClaw and replace adk_your_key:

openclaw mcp set adkit '{"url":"https://mcp.adkit.so","transport":"streamable-http","headers":{"Authorization":"Bearer adk_your_key"}}'