No dashboard. No YAML. No DevOps. Just open Telegram, tap a few buttons, and your agent is live — with an on-chain identity, cryptographic receipts, and a reputation that builds with every conversation. This guide walks through every screen you will see when launching an agent via the @mylclaw_bot Telegram bot.Documentation Index
Fetch the complete documentation index at: https://docs.lucid.foundation/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- A Telegram account (any platform — mobile, desktop, or web)
- That is it. No API keys, no wallets, no installs. The bot provisions everything for you.
Launch Walkthrough
Open Telegram and find the bot
Search for @mylclaw_bot in Telegram’s search bar, or open this link directly:t.me/mylclaw_botTap Start if this is your first time chatting with the bot. It will greet you and create your Lucid account automatically — no sign-up form, no email verification.
Send /launch
Type OpenClaw is Lucid’s general-purpose conversational agent — a good starting point. More agent templates are being added regularly.
/launch and send it. The bot responds with a catalog of available agents displayed as inline buttons:Tap OpenClaw
The bot fetches the agent details and asks how the agent should think — meaning which LLM provider powers its intelligence:
- Lucid Gateway routes requests through TrustGate to the best available model. No configuration required.
- Use your own API key lets you supply an OpenAI, Anthropic, or other provider key for direct access.
Choose Lucid Gateway
Select Lucid Gateway (no key needed). The bot handles all model routing for you via TrustGate — no API key required.Next, the bot asks where the agent should run:
- Lucid Cloud deploys to Lucid-managed infrastructure with a single tap. Zero configuration.
- Own Railway Account lets you connect your personal Railway account for self-managed hosting.
Choose Lucid Cloud
Select Lucid Cloud (one-click). The bot now asks which skills (tool integrations) you want your agent to have:Tap any skills you want to enable. Each skill gives your agent access to external tools via MCP (Model Context Protocol). You can skip this entirely if you just want a conversational agent.
Tap Done
After selecting skills (or none), tap Done. The bot shows a confirmation screen summarizing your choices:Review the summary. Everything look right? Tap Launch.
Tap Launch
The bot begins deployment:Behind the scenes, Lucid is:
- Creating a passport (on-chain identity) for your agent
- Building and pushing a container image
- Deploying to Lucid Cloud (Railway-managed infrastructure)
- Binding the agent to your Telegram chat as its communication channel
Send any message
Type anything — a question, a task, a conversation starter. Your message is routed through the bot to your deployed agent, and the agent’s response comes back in the same chat.Every interaction generates a cryptographic receipt anchored on-chain. Your agent is building verifiable history and reputation from the very first message.
Bot Commands
Once your agent is deployed, the bot provides several utility commands:/plan — Check your plan and usage
See your current plan tier, how many agents you have deployed, and your usage limits./upgrade — Upgrade to Pro
View available plans and upgrade directly from Telegram. The bot generates a Stripe Checkout link — tap it to complete payment in your browser, then return to Telegram./status — Check agent status
View the status of your deployed agents — whether they are running, stopped, or deploying./help — See all commands
Lists every available command with a short description.What Happened Behind the Scenes
When you tapped Launch, Lucid executed the full agent deployment pipeline:| Step | What happened | Layer |
|---|---|---|
| Identity | A passport was minted for your agent on Solana devnet | Settlement |
| Container | An OCI image was built and pushed to the container registry | Execution |
| Deploy | The container was deployed to Railway (Lucid Cloud) | Execution |
| Channel | Your Telegram chat was bound as the agent’s communication channel | Coordination |
| Receipts | Every message now generates a SHA-256 hashed receipt | Settlement |
| Epochs | Receipts batch into Merkle Mountain Range trees and anchor on-chain | Settlement |
| Reputation | Your agent’s reputation score updates with every verified interaction | Settlement |
Next Steps
- How Agents Work — Understand the agent lifecycle: Init, Plan, Accomplish, Execute, Validate
- Passport Management — Manage your agent’s on-chain identity
- Receipts & Proofs — How every interaction becomes a verifiable receipt
- Payments — Understand payments, credits, and settlement
- Deploy from CLI — For developers who prefer the command line
.png?fit=max&auto=format&n=VsjUqn6fLqEhBiuI&q=85&s=8b4c7e6431e9a6af1ef23b77bb4ff5fd)
.png?fit=max&auto=format&n=VsjUqn6fLqEhBiuI&q=85&s=d5651a45e4bfbabc33f74e146af3f94a)