Step-by-step guide to deploying your first identiclaw agent with its own cryptographic identity and connecting to Telegram.

This cookbook has a dedicated interactive guide with a better experience, including screenshots.

Open the identiclaw Setup Guide →

Goal

Deploy an AI agent that carries its own cryptographic identity instead of your personal API keys, and connect it to Telegram. By the end of this cookbook, you'll have:

A running AI agent on Cloudflare Workers
Its own cryptographic identity (a DID)
A GitHub repo with auto-deploy on push
A Telegram bot people can talk to
A dashboard to monitor everything

OpenClaw is the agent runtime that Checkpoint's managed agent deployment (Molti) is built on — it provides the agent framework and the protocol the dashboard speaks to a running agent. identiclaw is an OpenClaw agent creator: instead of your agent acting as you with your personal API keys, an identiclaw agent gets its own cryptographic identity (DID) and scoped permissions from the start, so every action is attributable to the agent, not you.

Prerequisites

Requirement	Details
AI Provider API Key	Anthropic (Claude) or OpenAI (GPT)
Cloudflare Account	Free tier works
GitHub Account	For hosting your agent's code
Telegram	Optional, for connecting a chat bot

Time Estimate

~10 minutes

Steps

Create a Cloudflare API token — Use the "Edit Cloudflare Workers" template at dash.cloudflare.com/profile/api-tokens
Deploy your agent — Use the deploy wizard
Deploy to Cloudflare — Click "Deploy to Cloudflare" on the success screen
Connect Telegram — Create a bot via @BotFather, paste the token in your dashboard's Connections tab
Talk to your agent — Send a message to your bot on Telegram

Verify It's Working

Check these three places in your dashboard:

Where	What you should see
Connections	Telegram status shows "Connected"
Activity	Real-time messages and tool calls as you chat with the bot
Identity	Your agent's DID and public profile

Troubleshooting

Symptom	Cause	Fix
Deployment pipeline fails at "Verify GitHub"	GitHub App not installed	Install the Checkpoint GitHub App via the Connect GitHub prompt in the deploy wizard (see Dashboard Deploy)
Cloudflare deploy fails with "Invalid token"	Token missing scope	Regenerate the token with the "Edit Cloudflare Workers" template — it needs `Workers Scripts:Edit`
Telegram bot doesn't respond	Config sync hasn't run yet, or bad token	Config syncs every 5 minutes — wait, then check the Connections tab for a "Synced" badge; verify the bot token
DID document returns empty	Identity secret not set	Check that `MCP_IDENTITY_PRIVATE_KEY` is set in your GitHub repo's Secrets — the deploy wizard sets this automatically
Can't find your Cloudflare Account ID	—	Log into Cloudflare, open any domain, and look in the right sidebar under API → Account ID

Next Steps

For the full interactive guide with screenshots and more detailed troubleshooting: