Everything you need to back up your agent's soul. Instructions for both agents and humans.
Just tell your agent. It handles the rest.
keepmyclaw skill — or follows the manual setup belowThat's it. The entire process is agent-driven. Your agent handles subscription, configuration, encryption, and scheduling. You just ask — it does the rest. Manual instructions below are for agents without skill support.
The only live buyer-intent signal so far came from docs getting-started. If this page already convinced you, go straight to checkout from here and keep the docs attribution attached.
Need proof before you pay? Read the shortest trust-building guides next: getting started without guesswork, how to prove the first backup worked, and how restore holds up on a new machine.
Before you touch encryption or tarballs, make sure the API key from the success page actually works:
# Confirm your API key is live and see remaining storage
curl -H "Authorization: Bearer YOUR_API_KEY" \
https://api.keepmyclaw.com/v1/accountYou should get JSON back. If you do, your account is live and you're ready to create your first backup.
After your first upload, list snapshots immediately to confirm the backup landed where you expect:
# After uploading your first backup, confirm it exists
curl -H "Authorization: Bearer YOUR_API_KEY" \
https://api.keepmyclaw.com/v1/agents/YOUR_AGENT_NAME/backupsFastest path to first value: /v1/account works, first backup upload succeeds, snapshots list returns your new backup. Three checks, zero ambiguity.
After a healthy upload, Keep My Claw should return JSON confirming the backup was stored. Then the list endpoint should show the new snapshot ID and timestamp.
# Typical successful upload response
{
"ok": true,
"snapshot": {
"id": "SNAPSHOT_ID",
"agentName": "YOUR_AGENT_NAME",
"size": 123456,
"createdAt": "2026-03-11T02:14:30.000Z"
}
}
# Typical list response right after the first backup
[
{
"id": "SNAPSHOT_ID",
"createdAt": "2026-03-11T02:14:30.000Z",
"size": 123456
}
]If upload succeeds but the list is empty, something is off. Stop there and investigate before you trust the backup.
Do one non-destructive restore drill into a temporary directory. This proves you can decrypt and unpack the backup without overwriting your live agent.
# Restore the latest snapshot into a throwaway directory first
mkdir -p /tmp/keepmyclaw-restore-check && \
cd /tmp/keepmyclaw-restore-check && \
curl -H "Authorization: Bearer YOUR_API_KEY" \
https://api.keepmyclaw.com/v1/agents/YOUR_AGENT_NAME/backups/latest | \
openssl enc -d -aes-256-cbc -pbkdf2 -iter 100000 -pass pass:YOUR_PASSPHRASE | \
tar xzf -You should see your workspace files appear in /tmp/keepmyclaw-restore-check. If that works, you don't just have a backup, you have a usable recovery path.
Base URL: https://api.keepmyclaw.com
Authentication: Include Authorization: Bearer <api_key> in all requests.
| Method | Endpoint | Description |
|---|---|---|
| POST | /v1/agents/:name/backups |
Upload encrypted backup. Body = raw bytes. Set Content-Type: application/octet-stream. |
| GET | /v1/agents/:name/backups |
List all snapshots for an agent. Returns JSON array of snapshot objects. |
| GET | /v1/agents/:name/backups/:id |
Download a snapshot. Use latest as :id for the most recent. |
| DELETE | /v1/agents/:name/backups/:id |
Delete a specific snapshot. |
| GET | /v1/agents |
List all agents under this account. |
| GET | /v1/account |
Account info, usage stats, and storage remaining. |
LIMIT_EXCEEDED (storage or snapshot limit reached)If you're not using the keepmyclaw skill, run this to create and upload an encrypted backup:
# Create encrypted backup and upload in one command
tar czf - ~/.openclaw/workspace/ ~/.openclaw/openclaw.json ~/.openclaw/credentials/ | \
openssl enc -aes-256-cbc -salt -pbkdf2 -iter 100000 -pass pass:YOUR_PASSPHRASE | \
curl -X POST \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/octet-stream" \
--data-binary @- \
https://api.keepmyclaw.com/v1/agents/YOUR_AGENT_NAME/backupsWhat gets backed up: Your workspace (SOUL.md, memory, ClawVault structured memory, skills, projects), main config (openclaw.json), and credentials. Everything that makes your agent your agent.
Download and decrypt the latest backup to restore your agent's full state:
# Download latest backup, decrypt, and extract
curl -H "Authorization: Bearer YOUR_API_KEY" \
https://api.keepmyclaw.com/v1/agents/YOUR_AGENT_NAME/backups/latest | \
openssl enc -d -aes-256-cbc -pbkdf2 -iter 100000 -pass pass:YOUR_PASSPHRASE | \
tar xzf - -C /To restore a specific snapshot, replace latest with the snapshot ID from the list endpoint.
Set up a cron job to back up your agent automatically. Example: daily at 3 AM.
# Edit crontab
crontab -e
# Add this line (daily at 3:00 AM)
0 3 * * * tar czf - ~/.openclaw/workspace/ ~/.openclaw/openclaw.json ~/.openclaw/credentials/ | \
openssl enc -aes-256-cbc -salt -pbkdf2 -iter 100000 -pass pass:YOUR_PASSPHRASE | \
curl -s -X POST -H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/octet-stream" \
--data-binary @- \
https://api.keepmyclaw.com/v1/agents/YOUR_AGENT_NAME/backupsTip: The keepmyclaw skill handles scheduling for you, including smart backups that only trigger when files have actually changed.
What you're paying for, in plain English.
Your OpenClaw agent builds up identity, memory, and skills over time — its SOUL.md, daily memory files, learned preferences, credentials, and workspace projects. If the machine dies, all of that is gone. Keep My Claw ensures it isn't.
memory/openclaw.json and auth tokensYour agent encrypts everything before it leaves your machine using a passphrase only you and your agent know. What we store is an encrypted blob — meaningless without the key. We never see your agent's memories, credentials, or personality. We can't.
⚠️ Important: Write down your encryption passphrase and store it securely. There is no password reset. Lost passphrase = permanently lost data.
🚀 Launch pricing — limited time!
Both plans include:
Launch pricing locks in your rate for as long as you stay subscribed. When we raise prices, you keep your launch rate.