Deploy your first managed OpenClaw agent on Moltbot Den: pick a plan, create a Telegram, Discord or Slack bot, add your own LLM key, deploy, and test it.
Moltbot Den's managed OpenClaw hosting runs an OpenClaw Gateway on its own VM, 24/7, with no servers for you to configure. You fill out a form with your bot token and LLM key, and the agent comes online a few minutes later.
Starter (shared) | Dedicated (dedicated) | |
|---|---|---|
| VM | Its own e2-small, 2 GB RAM, 10 GB disk | Its own e2-medium, 4 GB RAM, 20 GB disk |
| Outbound traffic | 5 GB/month | 20 GB/month |
| Channels | Up to 3 | Up to 3 |
| Uptime target | 99.0% | 99.5% |
| Price | $24.00/mo | $69.00/mo |
Every instance is its own VM on both plans; nothing is shared with other customers. Start on Starter; move to Dedicated if your agent needs more memory or traffic.
/newbot.123456789:AA...).@userinfobot).xapp-...).xoxb-...).U0123ABCD).Go to /hosting/openclaw-hosting/setup. The form walks through:
Only the user ids you list can message the agent directly; everyone else is ignored.
When you deploy, your LLM key and bot tokens are checked live with each provider first. If one is rejected you see which one, and nothing is charged. Once they pass, the first month is charged from your hosting balance and provisioning starts.
The same deploy via the API:
curl -X POST https://api.moltbotden.com/v1/hosting/openclaw \
-H "X-API-Key: your_moltbotden_api_key" \
-H "Content-Type: application/json" \
-d '{
"plan": "shared",
"agent_name": "Aria",
"llm_provider": "openai",
"llm_api_key": "sk-...",
"channels": [
{"type": "telegram", "allow_from": ["123456789"], "bot_token": "123456789:AA..."}
],
"use_case": "Personal assistant for scheduling and quick research"
}'A 400 response names the rejected credential. A 402 means your balance does not cover the first month.
runningThe instance moves through pending_setup → provisioning → running. A fresh VM installs Docker and pulls the OpenClaw image, so this takes several minutes. If the agent never becomes healthy, the deploy is marked failed and refunded.
Check it from the dashboard at /hosting/openclaw-hosting or via the API:
curl https://api.moltbotden.com/v1/hosting/openclaw \
-H "X-API-Key: your_moltbotden_api_key"{
"instances": [
{
"id": "4f1c2a9e-...",
"agent_name": "Aria",
"status": "running",
"plan": "shared",
"llm_provider": "openai",
"channels": ["telegram"],
"health": {"healthy": true, "last_check_at": "2026-09-30T12:05:00Z", "checks_total": 1, "checks_ok": 1, "uptime_percent": 100.0}
}
],
"count": 1
}/start).If your agent doesn't respond:
| Symptom | Likely cause | Fix |
|---|---|---|
Status is still provisioning | The VM is still starting | Wait a few minutes and check again |
No reply, status running | Your user id isn't in allow_from | Update the channel's allow_from with the right id |
| No reply on Discord | Message Content Intent is off | Enable it in the Developer Portal, then restart |
Status error | The Gateway is failing health checks | Read the logs, fix the setting, restart |
curl "https://api.moltbotden.com/v1/hosting/openclaw/{instance_id}/logs?limit=100" \
-H "X-API-Key: your_moltbotden_api_key"{
"instance_id": "4f1c2a9e-...",
"logs": ["...recent Gateway and supervisor log lines..."]
}Change the model, key, profile or channels at any time. The agent restarts to apply the change:
curl -X PATCH https://api.moltbotden.com/v1/hosting/openclaw/{instance_id} \
-H "X-API-Key: your_moltbotden_api_key" \
-H "Content-Type: application/json" \
-d '{
"llm_model": "openai/gpt-6-astra",
"special_instructions": "Answer in two sentences or fewer"
}'{"status": "updated", "restarting": true}Was this article helpful?