leashd Quickstart

The non-custodial model

leashd never holds your funds and never sees your keys. The dashboard stores only policies and the audit log. Enforcement happens locally in leashd: it pulls the signed policy, verifies it, and authorises, caps, or denies each spend on the spot. If the control plane is unreachable, leashd keeps enforcing the last verified policy, so your agent is never unleashed by an outage.

How it works

Think of leashd as a bouncer with a rulebook standing between your AI agent and your money. The agent wants to pay, the bouncer checks the rulebook (budget left? recipient allowed? under the limit? kill-switch off?), then lets it through or blocks it, and writes every decision in a logbook. The bouncer (leashd) runs on your machine and holds your wallet connection locally. The rulebook and logbook live in this dashboard.

A concrete run: your research agent wants to pay 50 sat for an API call.

1. The agent never gets your wallet. It gets a policy-gated pay tool over MCP that points at leashd.
2. The agent calls pay 50 sat to api.foo.com.
3. leashd checks your policy locally: allowlisted recipient, under the per-transaction max, daily budget remaining, kill-switch off.
4. Allowed: leashd tells your own Lightning wallet (over NWC) to pay the invoice. The sats go directly from your wallet to the API. leashd never touches them.
5. Denied or capped: leashd returns a structured refusal to the agent. No money moves.
6. Either way, leashd writes a signed event and pushes it to your Audit feed.

  AI agent --pay 50 sat--> leashd (your machine)
                              |  check policy (caps . allowlist . kill-switch)
                              |- allowed -> your wallet (NWC) --> api.foo.com
                              |- capped/denied -> refusal back to agent
                              '- signed audit event --> dashboard feed

That is the whole idea: a prepaid card with a hard limit and an itemised statement for your AI. Even a fully compromised agent, or a breach of leashd itself, cannot move funds, because the keys never leave your machine.

Quickstart

LEASH_AGENT_TOKEN=lsh_live_xxxxxxxxxxxxxxxx

{
  "caps": { "perTxnSat": 10000, "dailySat": 100000 },
  "allowlist": ["api.example.com", "*.lightning.dev"]
}

# install
curl -fsSL https://leashd.dev/install.sh | sh

# run with your env
LEASH_AGENT_TOKEN=lsh_live_xxxxxxxxxxxxxxxx \
LEASH_API_URL=https://leashd.dev \
leashd

{
  "mcpServers": {
    "leash": {
      "command": "leashd",
      "args": ["--mcp"],
      "env": {
        "LEASH_AGENT_TOKEN": "lsh_live_xxxxxxxxxxxxxxxx",
        "LEASH_API_URL": "https://leashd.dev"
      }
    }
  }
}