Getting started · ~5 min
Quickstart
In this guide you'll install the SDK, talk to your Admin agent, add a Markdown skill, and
connect a channel so your agent can reply for you. By the end you'll have a working
foundation to build on.
This page is for calling the ClawAgen API. You'll need a tenant API key
(from the dashboard or via self-hosted admin console) plus Node 18+ or Python 3.11+ for
the SDK. If you're running the platform yourself, see{' '}
What do you need? on the homepage for
the full backend stack.
1. Install the SDK
Pick your language. Both SDKs are thin wrappers over the REST API.
$ bun add @clawagen/node` },
{ label: 'npm', raw: 'npm install @clawagen/node',
code: `$ npm install @clawagen/node` },
{ label: 'pnpm', raw: 'pnpm add @clawagen/node',
code: `$ pnpm add @clawagen/node` },
{ label: 'pip', raw: 'pip install clawagen',
code: `$ pip install clawagen` },
]}
/>
2. Get your API key
From the Dashboard → API keys, create a new key. Keys
are tenant-scoped — a key identifies both you and{' '}
your agent. Keys begin with ck_live_.
Never commit them to source control.
CLAWAGEN_KEY=ck_live_•••••••••••••••
CLAWAGEN_BASE_URL=https://api.clawagen.com` }]} />
Preview tenants are capped at 200 requests/hour and 100 MB of memory storage.
Production limits unlock once general availability ships.
3. Say hello to your agent
The /api/admin endpoint streams a reply from your owner-facing agent. It
speaks in your voice, has access to all your skills and memory, and can run bash{' '}
and load_skill under the hood.
import { ClawAgen } from '@clawagen/node';
const c = new ClawAgen(process.env.CLAWAGEN_KEY);
for await (const chunk of c.chat.admin.stream({
message: 'What is in my MEMORY.md right now?',
})) {
if (chunk.type === 'text_delta') process.stdout.write(chunk.delta);
}` },
{ label: 'curl', raw: `curl -N https://api.clawagen.com/api/admin \\\n -H "X-API-Key: $CLAWAGEN_KEY" \\\n -H "Content-Type: application/json" \\\n -d '{"message":"What is in my MEMORY.md right now?"}'`,
code: `$ curl -N https://api.clawagen.com/api/admin \\
-H "X-API-Key: $CLAWAGEN_KEY" \\
-H "Content-Type: application/json" \\
-d '{"message":"What is in my MEMORY.md right now?"}'` },
{ label: 'python', raw: `from clawagen import ClawAgen\nc = ClawAgen(api_key=os.environ["CLAWAGEN_KEY"])\n\nfor chunk in c.chat.admin.stream(message="What is in my MEMORY.md right now?"):\n if chunk.type == "text_delta":\n print(chunk.delta, end="", flush=True)`,
code: `from clawagen import ClawAgen
c = ClawAgen(api_key=os.environ["CLAWAGEN_KEY"])
for chunk in c.chat.admin.stream(message="What is in my MEMORY.md right now?"):
if chunk.type == "text_delta":
print(chunk.delta, end="", flush=True)` },
]}
/>
4. Write your first skill
Skills are Markdown files. Drop one under skills/{name}/SKILL.md and your
agent can invoke it on demand. The system prompt lists skill names and one-line descriptions;
the full body is loaded only when the agent calls load_skill.
---
name: weekly-summary
description: Summarize this week's inbox activity across all channels
trigger: "summarize my week"
---
# Weekly summary
When the user asks for a weekly summary:
1. Run \`tunder messages list --since 7d --all-channels\` to fetch last 7 days.
2. Group by sender, count unread threads, highlight any flagged as urgent.
3. Reply with a one-paragraph summary, then 3–5 bullet action items.` }]} />
The agent sees ~540 tokens of skill names and descriptions at all times. Bodies
(hundreds or thousands of tokens each) only load when invoked. You can ship 30+ skills
without blowing the context budget.
5. Connect a channel
Once a channel is connected, incoming messages are routed to your CS agent. The Admin agent
stays on the web dashboard; customers and external contacts talk to CS.
await c.channels.whatsapp.connect({
phoneNumberId: process.env.WA_PHONE_NUMBER_ID,
accessToken: process.env.WA_ACCESS_TOKEN,
verifyToken: crypto.randomUUID(),
});
// Set the Meta webhook to https://api.clawagen.com/webhook/whatsapp/{tenantId}` }]}
/>
The dashboard uses Meta's Embedded Signup flow — one click and WhatsApp is wired up,
including webhook registration. The SDK path above is for programmatic control.
Next steps
You've got the basics. Here's where to go from here.