Tools · Wallets & toolkits

Xverse Agent Wallet

A self-custodial Bitcoin wallet built for AI agents — it answers an HTTP 402 by paying the Lightning invoice itself, no human checkout.

What it is

The Xverse Agent Wallet is a self-custodial Bitcoin wallet designed for autonomous agents. It implements the Machine Payments Protocol (MPP) — a standard Xverse credits to Stripe and Tempo, not an Xverse invention: the agent calls an API, receives an HTTP 402, pays the returned Lightning invoice (settling over Spark), and receives the data — autonomously, with no human in the checkout loop. Keys stay on the machine, encrypted at rest (AES-256-GCM); the underlying xverse-core library has been third-party audited.

It’s the consumer-grade Xverse wallet’s architecture turned toward agents: self-custody plus machine-tempo, human-free payment.

It is multi-chain, and that is a fact about what you are adopting. Xverse describes it as “multi-chain from birth” — the same wallet holds BTC, trades on Starknet DEXes via AVNU, swaps on Flashnet over Spark, and manages Runes on Bitcoin L1, with Stacks via Bitflow. It also carries fiat on-ramps: Xverse’s own agent page says you “fund your agent with fiat via MoonPay, Revolut, or Banxa.” Two things follow for a builder. A wallet holding several assets widens the freeze surface to every asset it holds, not just the one you meant to use — the same reasoning Exchange applies to multi-asset accounts. And a fiat on-ramp is a KYC surface attached to a wallet whose selling point is that an agent needs no account: the on-ramp providers are the ones asking for identity, and using one puts a human’s verified identity behind the funding leg.

MCP. Xverse markets the agent wallet as MCP-compatible, and its agent page’s FAQ is specific about where the server lives: “The Xverse API ships a native MCP server that plugs into Claude, Cursor, Codex, Copilot, Cline, Windsurf, OpenClaw, and Hermes.” Note the attribution — it credits the Xverse API, a sibling product, rather than the agent wallet itself, and Xverse publishes no endpoint URL or package name for it. So an agent can reach Xverse over MCP, but not yet by copying a connection string out of the docs.

When to use it

• Giving an agent a self-custodial wallet that pays 402-gated APIs on its own.
• Deployments that want keys on-device (encrypted) rather than delegated to a remote wallet.
• Settlement over Spark with Lightning interoperability.

Dependencies

The audited xverse-core library and a Spark backend for settlement, plus a funding source; keys stay encrypted on-device (AES-256-GCM) and the agent answers HTTP 402s by paying Lightning invoices itself. Inherits Spark’s mainnet-beta operator-trust assumptions.

Quick start

Xverse puts one command on its agent page and in its docs:

npx @secretkeylabs/xverse-agent-wallet --install

Then read the agent-wallet docs at docs.xverse.app/xverse-agentic-wallet/; the audited core library is xverse-core at github.com/secretkeylabs/xverse-core. The agent funds a wallet and then transacts against 402-gated endpoints via the Machine Payments Protocol.

Gotchas

• Self-custodial, but the agent spends autonomously without per-payment approval — a key/host compromise means autonomous fund drain (mitigated, not eliminated, by on-device encryption). Cap balances and scope what the agent can pay.
• Settlement runs over Spark, itself a mainnet-beta L2 — it inherits Spark’s early-stage operator-trust assumptions. See Spark.
• The agent-wallet surface is newer and less battle-tested than the established Xverse consumer wallet.
• The fiat on-ramps re-introduce KYC at the funding leg. MoonPay, Revolut and Banxa each verify a human. A wallet an agent can operate without an account is still being funded through a route that wants identity — so “no account” describes the wallet, not the money’s path into it.
• Multi-chain means multi-issuer. Holding Runes, Starknet assets or cross-chain stablecoins in the same wallet widens what a third party can freeze or devalue. The BTC and Lightning legs are the ones that carry no issuer.