Cowrie Research

xverse

4 min read

Xverse

  • Name: Xverse
  • URL: https://www.xverse.app/
  • Category: Bitcoin wallet and access-stack platform / wallet-connectivity SDK / agent-wallet and MCP access layer
  • Tags: bitcoin-ecosystem stacks-ecosystem
  • Summary: Xverse is a Bitcoin wallet-access stack with some real hosted edges, not just a wallet app. The useful cut is the bundle: consumer wallet, Sats Connect, data API, agent wallet, and hosted MCP endpoint. Keep this note on that product and access stack. The named operator boundary around release workflow, hosted endpoint admission, API-key issuance, machine-payments access terms, and the legal/privacy shell now lives separately in secret-key-labs.
  • What it does:
    • Operates a self-custodial Bitcoin wallet that now markets itself as a “sovereign onchain bank” for earning, borrowing, spending, privacy, and cross-layer asset management across Bitcoin and Bitcoin-adjacent layers
    • Exposes Xverse API, a production-grade Bitcoin data and transaction-workflow surface covering Bitcoin RPC, mempool data, UTXOs, balances, portfolio analytics, Ordinals, Runes, BRC-20, Spark, inscriptions, swaps, and cross-chain routing
    • Maintains Sats Connect, a JavaScript wallet SDK that lets apps request addresses, signatures, PSBT signing, transfers, and other wallet interactions across Bitcoin, Spark, Starknet, and Stacks
    • Publishes Xverse Agent Wallet, a headless self-custodial wallet for AI agents that can hold, send, receive, swap, and trade across Bitcoin L1 and multiple Bitcoin-adjacent rails without a browser extension or UI
    • Runs a hosted MCP server that exposes read-only Bitcoin, Ordinals, Runes, BRC-20, Spark, and swap-quote data to Claude, Cursor, Codex, VS Code, Windsurf, Zed, and other MCP-capable clients
    • Supports machine-payable API access over Lightning / MPP, which is a notable clue that Xverse is actively targeting agentic and automated Bitcoin workflows rather than only human wallet UX
  • Key claims:
    • The homepage frames Xverse as “The Sovereign Onchain Bank & Bitcoin Wallet,” with self-custody, integrated Bitcoin L2 support, privacy features, hardware-wallet support, and a card/borrowing surface
    • The docs landing page says the infrastructure behind Xverse is now open to developers and explicitly splits the stack into Xverse API, Sats Connect, Xverse Agent Wallet, and MCP Server
    • The Xverse API docs position the service as the Bitcoin RPC, indexer, and data layer used by Xverse wallet itself, now opened to third-party builders
    • The Xverse Agent Wallet docs describe it as “the first Bitcoin-native wallet built for AI agents,” emphasizing headless CLI operation, self-custody, Lightning/MPP payments, and multichain Bitcoin-layer support
    • The MCP docs say Xverse runs a centrally hosted MCP server with 54 read-only tools across Bitcoin, Ordinals, Runes, BRC-20, Spark, and swaps, authenticated with an Xverse API key
    • The Sats Connect AI-agent docs say the project ships method-level Agent Skills for coding agents, which is another strong signal that Xverse is deliberately building for agent-native integration, not merely wallet connectivity
    • The GitHub org reinforces the control-plane reading: public repos include Sats Connect, Xverse core libraries, the browser extension, and agent-skill repos rather than only a thin wallet client

Internal linkages

Protocol / company boundary

  • Keep this note on the product and access-stack surface: wallet UX, Sats Connect methods, Xverse API capabilities, agent-wallet packaging, and the Bitcoin-adjacent rails the Xverse product bundle makes easy to use.
  • Use secret-key-labs when the useful question is who ships the releases, operates the hosted API and MCP endpoints, issues API access, sets machine-payments access terms, or controls the legal/privacy/support shell around that stack.
  • That split matters because what can Xverse expose to users, apps, and agents? and which company controls the easiest distribution and hosted infrastructure path around Xverse? are related but not identical questions.

Control surface

  • At the product layer, practical authority sits in Sats Connect method defaults, wallet and agent-wallet packaging, hosted MCP availability, and which Bitcoin-adjacent rails Xverse chooses to normalize behind one access stack.

  • Read it as a Bitcoin access stack with growing hosted edges, not as a neutral wallet primitive and not as an onchain bank in any analytically useful sense.

  • For the named operator boundary behind release workflow, endpoint admission, and hosted support/legal shell, read secret-key-labs.

  • Last reviewed: 2026-08-08 UTC

Graph View

Backlinks