Build on RGB, with AI agents that hold and move assets

Run an RGB Lightning Node with the kaleido CLI (needs Docker and Python 3.11+), or use KaleidoSwap Desktop, which runs one for you.

pipx install kaleido-cli           # or: pip install kaleido-cli
export PATH="$HOME/.local/bin:$PATH"   # if kaleido is not found
kaleido setup                      # create + start one node
kaleido node init                  # once: set a password, write down the mnemonic
kaleido node unlock                # after every restart
kaleido wallet balance             # check it answers

The node API is on http://localhost:3001. If that port is taken, kaleido setup picks the next free one: kaleido node list shows it; use it as RLN_NODE_URL below.

• BTC from the Mutinynet faucet (sign in with GitHub, or pay a small Lightning invoice) to the address from kaleido wallet address.
• Colorable UTXOs before receiving or issuing RGB: kaleido wallet create-utxos (or rln_create_utxos, or ask the agent).
• USDT and XAUT from the RGB faucet (sign in with GitHub): use its RGB on-chain tab with an invoice from kaleido asset invoice <asset id>, taking the asset id from the faucet page. 100 USDT or 0.1 XAUT per claim, 5 claims a day. Its Lightning tab only works once you have a channel (step 3).

Swaps settle over Lightning, so your node needs a channel with the KaleidoSwap LSP. Buy one after funding: the LSP opens it to you, optionally with USDT or XAUT on its side, and you pay a fee on-chain.

• Size and cost: 50k to 1M sat, with up to 1,000 USDT or XAUT per channel. Tested on signet: a 54k-sat channel with 10 USDT inbound cost 7,281 sat in total and was usable about 4 minutes after payment.
• Leave room to swap: a BTC→USDT swap must send the swap amount plus a 3,000-sat RGB payment minimum from your side of the channel. Set client_balance_sat to at least your largest swap + 6,000 sat, and fund your node with that much more on-chain. One payment is also capped at about 10% of the channel capacity, so the channel (lsp_balance_sat + client_balance_sat) must be at least 10 × (swap + 3,000 sat): 50,000 + 20,000 sat carries swaps up to about 4,000 sat. A channel with only 4,000 sat on your side cannot swap at all.
• Step by step (kaleido-mcp tools): kaleidoswap_lsp_get_info → rln_connect_peer to the LSP → kaleidoswap_lsp_estimate_fees → kaleidoswap_lsp_create_order (with your client_pubkey from rln_get_node_info) → rln_send_btc of the order's amount_due_sat to payment.onchain.address → rln_list_channels until it is usable. Pay the order total, not only the fee.
• With an agent: ask "I want to swap BTC for USDT but I have no channel. Buy me a channel from the KaleidoSwap LSP with 10 USDT inbound." It stops for your confirmation before paying.
• In KaleidoSwap Desktop: Channels → Order New Channel.
• Swap limits per trade: 0.000001 to 0.01 BTC, 0.5 to 1,000 USDT or XAUT. Allow a few blocks for the channel to open before you swap.

MCP is the standard way an AI app discovers and calls tools. You register kaleido-mcp once; the AI app starts it for you and you just chat.

claude mcp add kaleido -e RLN_NODE_URL=http://localhost:3001 -- npx -y kaleido-mcp

{
  "mcpServers": {
    "kaleido": {
      "command": "npx",
      "args": ["-y", "kaleido-mcp"],
      "env": { "RLN_NODE_URL": "http://localhost:3001" }
    }
  }
}

Check it: ask "What's my node info?". You should see a call to rln_get_node_info and your node's pubkey. RLN_NODE_URL is your node's API address.

The rgb-agent example runs a QVAC model, connects it to kaleido-mcp, loads the RGB node skill and asks three questions: balances, a 10 USDT invoice, then a 5 USDT send (only with RECIPIENT_INVOICE set). Edit steps in src/index.ts to ask your own.

npm create @kaleidorg/mind my-agent
cd my-agent && npm install
npm run start:offline  # fake node + scripted model: checks the setup, no download
npm run start:mock     # fake node, Qwen3.5 2B on-device (~1.3 GB, downloaded once)
npm run eval:mock      # 6 wallet tasks against the fake node
RLN_NODE_URL=http://localhost:3001 npm start   # your node via kaleido-mcp

> Which RGB assets do I hold, and what are the balances?
  tool rln_list_assets {}
You hold 1,000 USDT and 2 XAUT.

> Create an RGB invoice so I can receive 10 USDT.
  tool rln_create_rgb_invoice {"asset":"USDT","amount":10}
Here is your invoice: rgb:~/~/~/sig/…/10/utxob:…

> Send 5 USDT to this RGB invoice: rgb:…
  tool rln_send_asset {"asset":"USDT","amount":5,"to":"rgb:…"}
  Send 5 USDT to rgb:…. Confirm? [y/N]

Same in an MCP client, the KaleidoMind example, or the AI chat in our wallets. Short, specific requests work best.