Cowrie Research

xverse-primary-sources-2026-04-29

4 min read

Xverse primary-source snapshot

Last reviewed: 2026-04-29 UTC

Project status snapshot

What the official materials say

1) Homepage and consumer positioning

  • URL: https://www.xverse.app/
  • Key takeaways:
    • The homepage frames Xverse as “The Sovereign Onchain Bank & Bitcoin Wallet,” not merely as a simple wallet extension.
    • It emphasizes self-custody, yield, borrowing, spending, cross-layer portfolio management, privacy toggles, and a limited-release card product.
    • The site says Xverse supports activity across Bitcoin, Starknet, Stacks, and Spark, which already suggests a broader Bitcoin financial-access surface than a plain BTC wallet.

2) Security page as an architectural clue

  • URL: https://www.xverse.app/security
  • Key takeaways:
    • Xverse says it is self-custodial, keeps keys encrypted on-device, supports Ledger, and offers multisig support via Asigna.
    • It also highlights open-source and third-party audit claims, which matters because the wallet brand is backed by a visible technical and code surface rather than only closed consumer UX.

3) Docs home: the strongest source for category placement

  • URL: https://docs.xverse.app/
  • Key takeaways:
    • The docs homepage explicitly says the infrastructure behind Xverse is open to developers.
    • It splits the developer surface into Xverse API, Sats Connect, Xverse Agent Wallet, and MCP Server.
    • This is the clearest signal that Xverse is best cataloged as wallet/data/access infrastructure rather than as only a consumer wallet app.

4) Docs index (llms.txt): unusually broad Bitcoin surface

  • URL: https://docs.xverse.app/llms.txt
  • Key takeaways:
    • The index exposes a large API and SDK surface across Bitcoin RPC, mempool, UTXOs, balances, portfolio registration, Ordinals, Runes, BRC-20, Spark, swaps, Sats Connect methods, and agent-oriented sections.
    • The same index also shows MCP and AI-agent integration pages, which is unusual for a wallet brand and strongly suggests that Xverse is trying to become an AI-ready Bitcoin control plane.

5) Xverse API: data layer, transaction workflows, and machine-payable access

  • URL: https://docs.xverse.app/api/xverse-api.md
  • Key takeaways:
    • Xverse says the API is production infrastructure used by the Xverse wallet itself and now opened to external developers.
    • It positions the API as Bitcoin RPC, indexer, and data layer in one service.
    • Supported areas include Bitcoin mempool and transaction data, balances and UTXOs, Ordinals, Runes, BRC-20, portfolio analytics, inscriptions, swaps, and cross-chain routing.
    • The docs also say endpoints can be paid for over Lightning / MPP at 1 sat per call, which is a notable agent-native design choice.

6) Xverse Agent Wallet: headless agent wallet, not a wallet wrapper

  • URL: https://docs.xverse.app/xverse-agentic-wallet/xverse-agent-wallet.md
  • Key takeaways:
    • The docs call it “the first Bitcoin-native wallet built for AI agents.”
    • Xverse says the agent wallet is headless, self-custodial, CLI-driven, and built on the same xverse-core as the main wallet.
    • Claimed capabilities include Lightning payments, Spark and Starknet trading, Rune management, treasury rebalancing, and portfolio queries across multiple Bitcoin-adjacent rails.
    • This is one of the strongest signals that Xverse is now broader than a standard wallet brand.

7) MCP server: hosted read-only agent surface

  • URL: https://docs.xverse.app/api/mcp-server.md
  • Key takeaways:
    • Xverse says it runs a centrally hosted MCP server with Streamable HTTP transport and Xverse API-key authentication.
    • The server reportedly exposes 54 read-only tools across Bitcoin, Ordinals, Runes, BRC-20, Spark, and swaps.
    • The docs provide direct setup guidance for Claude Code, Cursor, VS Code, Codex, Windsurf, and Zed, which is unusually explicit agent-tooling support.

8) Sats Connect AI agent integration: method-level skills for coding agents

  • URL: https://docs.xverse.app/sats-connect/ai-agent-integration.md
  • Key takeaways:
    • Xverse documents Agent Skills for Sats Connect methods like getAddresses, signPsbt, spark_transfer, and more.
    • This matters because it shows the team is not only supporting wallet connections for human developers but also deliberately optimizing the SDK for AI-assisted integration flows.

9) GitHub organization: public repo evidence of the operating model

  • URL: https://github.com/secretkeylabs
  • Key takeaways:
    • The verified GitHub org exposes Sats Connect, xverse-core, the browser extension, roadmap materials, and sats-connect-skills.
    • The public repo footprint reinforces that Xverse is shipping a real wallet/access/integration stack rather than only a consumer-facing app.

Whitepaper / technical-doc status

  • No canonical standalone Xverse whitepaper or litepaper surfaced in this pass.
  • The best primary-source corpus is the official site plus the docs suite for API, wallet SDK, agent wallet, MCP, and AI-agent integration.
  • In practice, the docs are the current source of truth for what Xverse actually ships.

Research notes

  • Best current category for the library: Bitcoin wallet-control-plane infrastructure / Bitcoin data API and wallet SDK platform / agent-wallet and MCP-ready Bitcoin access layer.
  • The most important insight is that Xverse now spans consumer wallet UX, developer APIs, wallet SDKs, and AI-agent tooling in one coordinated stack.
  • The MCP and agent-wallet materials are especially high-signal because they show Xverse trying to become an AI-ready Bitcoin infrastructure layer, not just a wallet brand.
  • The GitHub org is useful corroboration because it exposes the code footprint behind the docs-first product expansion.

Graph View