Deploy your first identiclaw agent
This guide walks you through creating an AI agent with its own cryptographic identity, deploying it to Cloudflare Workers, and connecting it to Telegram so people can chat with it.
By the end of this guide, you'll have:
What you'll need
Telegram (optional)
To connect your agent as a Telegram bot so people can chat with it.
Create your Cloudflare API token
2 min
Your agent runs on Cloudflare Workers. You need an API token so we can deploy it for you. Here's exactly how to get one:
Go to Cloudflare API Tokens
Click Create Token
Find the Edit Cloudflare Workers template and click Use template
Under Account Resources, select your account. Under Zone Resources, select All zones (or a specific zone).
Click Continue to summary then Create Token
Copy the token now — you won't be able to see it again.
Required token permissions
| Permission | Access |
|---|---|
| Workers Scripts | Edit |
| Account Settings | Read |
Where's my Account ID?
In the Cloudflare Dashboard, click any domain. Your Account ID is in the right sidebar under API → Account ID. It looks like a1b2c3d4e5f67890...
Deploy your agent
3 min
Head to the deploy wizard. If you don't have an account yet, you'll sign up first (takes 30 seconds), then the wizard opens automatically.
Open deploy wizardAlready signed in? Go to your dashboard and click Deploy.
What the wizard asks for
A human-readable name. This is how your agent introduces itself.
Auto-generated from agent name. Lowercase, hyphens only.
Which LLM powers your agent. You can change this later.
Stored as an encrypted GitHub Secret. Never exposed in code.
Paste the token you just created. Can also add later.
Found in your Cloudflare dashboard URL or sidebar.
What happens behind the scenes
The wizard creates a private GitHub repo, generates an Ed25519 keypair for your agent's identity (DID), stores all secrets as encrypted GitHub Secrets, sets up a CI/CD pipeline, and registers your agent with Know That AI. Takes about 60 seconds.
Deploy to Cloudflare
1 min
After the wizard completes, you'll see a success screen with your new repo. Click the Deploy to Cloudflare button — this opens Cloudflare's deploy-from-GitHub flow.
Alternatively, via CLI:
# Clone your new repo git clone https://github.com/YOUR_USER/my-first-agent cd my-first-agent # Install dependencies npm install # Deploy npx wrangler deploy
Either method works. The GitHub Actions workflow also auto-deploys on every push to main.
Click Deploy to Cloudflare on the success screen
Follow Cloudflare's prompts to authorize the GitHub connection
Your agent is now live! You'll get a URL like my-first-agent.YOUR_ACCOUNT.workers.dev
Quick verify
curl https://my-first-agent.YOUR_ACCOUNT.workers.dev/.well-known/did.json
If you see a JSON response with a DID document, your agent is running.
Connect to Telegram
3 min
Now let's give your agent a face. You'll create a Telegram bot and connect it to your agent so anyone can chat with it.
Part A: Create a Telegram bot
Open Telegram and search for @BotFather
Send /newbot
Choose a display name (e.g. My First Agent)
Choose a username ending in bot (e.g. my_first_agent_bot)
BotFather gives you a token like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11. Copy it.
Part B: Add it to your dashboard
In your Checkpoint dashboard, go to your agent
Click the Connections tab
Click Add Channel → select Telegram
Paste your bot token and click Validate & Save
Config syncs automatically
Your Cloudflare Worker pulls channel config every 5 minutes. After saving, your Telegram bot will be live within 5 minutes. You'll see a “Synced” badge when it's connected.
Talk to your agent
1 min
Open Telegram, search for your bot's username, and send it a message. It should respond using your chosen AI provider.
You did it!
Your agent is live with its own cryptographic identity, running on the edge, and chatting on Telegram. Every action is tied to the agent's identity, not yours.
Verify in the dashboard
Go to your Checkpoint dashboard to see:
Connections
Telegram status shows "Connected"
Activity
See real-time messages and tool calls
Identity
Your agent's DID and public profile