HomeConnect your first agent

Golden path

Connect your first agent

This page gets a real Node or Python agent reporting live actions to your DashClaw deployment.

Your agent only needs DASHCLAW_BASE_URL and DASHCLAW_API_KEY. It never needs DATABASE_URL.

1

Choose your SDK

Use the Node path below. This page keeps the first-action flow short and only switches the parts that differ by language.

Selected SDK

Node

Install command:

Node install

npm install dashclaw
Use the URL of your own deployed DashClaw app, not https://dashclaw.io.
Example deployment: https://your-dashclaw-instance.example.com
Local development: http://localhost:3000

What the agent needs

Base URL: https://your-dashclaw-instance.example.com
Workspace API key
No direct database access
Never use https://dashclaw.io as the agent base URL
2

Set environment variables

Set the minimum connection values in the agent runtime. The agent only talks to the DashClaw HTTP API.

Node environment

DASHCLAW_BASE_URL=https://your-dashclaw-instance.example.com
DASHCLAW_API_KEY=<your-workspace-api-key>

Do not use the marketing site URL. DASHCLAW_BASE_URL must point to your deployed DashClaw app.

3

Copy the minimal starter snippet

This is the smallest real example that creates a live action in DashClaw.

Node starter

import { DashClaw } from 'dashclaw';

const claw = new DashClaw({
  baseUrl: process.env.DASHCLAW_BASE_URL,
  apiKey: process.env.DASHCLAW_API_KEY,
  agentId: 'my-agent',
  agentName: 'My Agent',
});

await claw.createAction({
  action_type: 'test',
  declared_goal: 'Verify DashClaw connection',
  risk_score: 10,
});
4

Optional: enable verified agents

Basic mode works with an API key only. Verified mode adds signed actions and pairing, but it is not required for your first successful connection.

Node pairing

const privateJwk = JSON.parse(process.env.AGENT_PRIVATE_KEY_JWK);

const { pairing, pairing_url } = await claw.createPairingFromPrivateJwk(privateJwk, {
  agentName: 'My Agent',
});

console.log('Approve pairing at:', pairing_url);
await claw.waitForPairing(pairing.id);
5

Validate the connection

This confirms your instance can accept real authenticated SDK traffic and can attach proof back to /setup.

Node validator

node ./dashclaw-platform-intelligence/scripts/validate-integration.mjs \
  --base-url https://your-dashclaw-instance.example.com \
  --api-key <api-key> \
  --full \
  --capture-setup-proof

This command assumes you downloaded and extracted dashclaw-platform-intelligence.zip so the validator lives in ./dashclaw-platform-intelligence/scripts/. If you installed it elsewhere, adjust the path.

Successful validation can feed proof back into /setup so the verification surface shows that a live SDK integration worked.

6

What success looks like

After the snippet and validator run cleanly, DashClaw should start showing live evidence of the connection.

Your first action appears in the dashboard and recent activity.
The agent shows up in live DashClaw traffic once it starts sending actions.
If you enable verified mode, the pairing shows as approved.
If policies are active, future risky actions can route into guard and approvals.

Common mistakes

Do not use https://dashclaw.io as DASHCLAW_BASE_URL. Use your own DashClaw deployment URL.
Use your DashClaw instance URL, not an API route or localhost from a different machine.
Set DASHCLAW_API_KEY in the agent runtime before running the snippet or validator.
Keep DATABASE_URL on the DashClaw server only. The agent should never need it.

Next steps

Open dashboard Go to /setupRead full SDK docsEnable verified agents Review policies