Claw Cash

  • Name: Claw Cash
  • URL: https://clw.cash/
  • Category: agent wallet infrastructure / Bitcoin treasury automation / machine-payments wallet stack
  • Tags: bitcoin-ecosystem
  • Summary: Claw Cash is a Bitcoin-first agent wallet and payment-ops stack. The useful part is not the CLI veneer; it is the way the product bundles stablecoin ingress, Bitcoin treasury conversion, Lightning and Arkade payout paths, HTTP 402 payment handling, and signer-boundary choices into one operator surface. Treat it as wallet-and-signing infrastructure for agents, not as a protocol.
  • What it does:
    • Gives AI agents a CLI and API for receiving and sending Bitcoin, Lightning, Arkade-based BTC flows, and stablecoin swaps
    • Positions Bitcoin as the agent’s verifiable treasury asset while using stablecoins as human-facing ingress/egress rails
    • Supports payment links where a human pays in stablecoins and the agent ultimately receives BTC-denominated value routed to an Arkade target address
    • Exposes cash pay flows for Machine Payments Protocol / HTTP 402 Payment Required challenges, using Lightning and a payment preimage as proof
    • Offers challenge-callback authentication, Telegram deep-link login, and bot-session flows so other bots can provision per-user wallet sessions
    • Separates signing from the CLI through enclave-backed or worker-backed signer modes, with documented audit trails, ticket signing, rate limits, and recovery procedures
    • Publishes agent-facing operational instructions through a SKILL.md that explains command behavior, payment polling, and safe send/pay confirmation rules
  • Key claims:
    • The official site says “Stablecoins in. Bitcoin out.” and repeatedly argues that Bitcoin is the only money an agent can cryptographically verify, which is the clearest clue that Claw Cash is being sold as treasury-and-trust infrastructure for agents rather than as a generic multichain wallet
    • The README says the stack includes an API, enclave signer, SDK, skills, CLI, and schemas, which makes the project materially broader than a single command-line wallet
    • The site and package docs both present cash pay as a live Machine Payments Protocol client for services returning 402 Payment Required, with Lightning as the currently supported payment method and the preimage used as proof of payment
    • The operator runbook documents two signer modes: enclave mode and worker mode, showing that key-management trust assumptions are a first-class part of the product rather than an implementation detail
    • The same runbook says worker mode is cheaper but operator-trusted, while enclave mode keeps key material hardware-isolated; this is a strong signal that Claw Cash is packaging signing-boundary choices for operators of agent wallets
    • The SKILL.md package docs show a reactive operational model around auth, payment detection, swap monitoring, and user confirmations, which is unusually explicit about how an agent should actually behave around money movement
    • First-party materials are slightly inconsistent about the precise enclave branding: the marketing site foregrounds AWS Nitro Enclave language while the README and runbook describe an Evervault Enclave deployment and also document a Cloudflare-worker-only signer mode. The common thread is enclave-backed isolation, but the exact production stack should be treated cautiously until the docs converge
  • Whitepaper: No canonical standalone Claw Cash whitepaper or litepaper surfaced in this pass. The clearest current source of truth was the official site, repository README, operator runbook, and published SKILL.md; see ../whitepapers/claw-cash-primary-sources-2026-05-03.md.
  • Sources:

Internal linkages