Build powerful Bitcoin applications with production-grade APIs used by — now available to developers.

Our suite of APIs provides everything you need to interact with the modern Bitcoin ecosystem: from Ordinals and Runes, to Bitcoin-native swaps, inscriptions, and Bitcoin L2 integrations. Whether you're building wallets, DeFi platforms, NFT marketplaces, or cross-chain bridges, our infrastructure gives you access to reliable, real-time blockchain data and ready-to-use transaction workflows.

We built these APIs to solve the real infrastructure problems we faced while building the Xverse wallet. Now we’re opening them up so Bitcoin developers can skip the heavy lifting and focus on building.

Your Bitcoin RPC, indexer, and data layer — all in one API.

With the Xverse API, you get:

🔌 Endpoints

. Happy building!

Don't want to manage an API key? Every Xverse API endpoint also accepts payment over the — pay 1 satoshi per request via Lightning, no key required. This is the recommended path for AI agents and autonomous clients.

See MPP Lightning Payments for the full flow.

Have feedback, feature requests, or want to partner? — we’d love to hear from you.

Bitcoin RPC, real-time and comprehensive Bitcoin mempool & transaction data, advanced indexing of UTXOs & balances, optimised for apps and dashboards.

Monitor Bitcoin asset balances and activity across multiple addresses, with automatic daily tracking and historical portfolio insights.

Fetch detailed information on all inscriptions, UTXOs, rare sats — everything you need to power an Ordinals experience.

Automate Ordinal inscriptions with advanced features. Estimate costs, create orders, and track inscription statuses seamlessly.

Returns the balance and a paginated list of transaction IDs for a given Bitcoin address. Fully mempool-aware.

This endpoint returns the combined historical activity across BTC, inscriptions, and runes for a set of addresses, including all incoming/outgoing transfers.

This endpoint returns the real-time mempool activity across BTC, inscriptions, and runes for a set of addresses, including all incoming/outgoing transfers.

This endpoint returns confirmation status, block height, and timestamp for a given Bitcoin transaction. Mempool-aware.

This endpoint returns the raw hex for a given Bitcoin transaction. It supports confirmed and unconfirmed transactions.

This endpoint decodes a raw Bitcoin transaction. Optimized to use the RPC node only for parsing, while transaction hex and I/O data are retrieved from our indexer.

This endpoint returns detailed info on Ordinal assets (BTC, inscriptions, runes) for each input and output of a transaction.

It is mempool-aware and includes unconfirmed BTC, inscriptions & runes data for mempool transactions

This endpoint returns detailed info on Ordinal assets (BTC, inscriptions, runes) for each output of a transaction.

It is mempool-aware and includes unconfirmed BTC, inscriptions & runes data for mempool transactions

This endpoint returns detailed info on Ordinal assets (BTC, inscriptions, runes) for each input of a transaction.

It is mempool-aware and includes unconfirmed BTC, inscriptions & runes data for mempool transactions

Estimate the approximate fee per kilobyte required for a transaction to confirm in the next blocks, based on the current state of the mempool.

This endpoint can be used to post a signed raw transaction to the Bitcoin network

Returns the latest Bitcoin block with height, hash, timestamp, and more.

Returns block metadata (hash, timestamp, tx count, etc.) for a specific height.

This endpoint lets you run a mempool acceptance test to check if the mempool will accept the serialized hex-encoded raw transaction

This RPC Method returns the hash of the tip block in the most-work fully-validated chain.

This endpoint offers a unified RPC interface for Bitcoin Core node functionality:

• Blockchain data: getbestblockhash, getblock, getblockchaininfo, getblockcount, getblockfilter, getblockhash, getblockheader

This RPC Method returns an object that contains the information regarding blockchain processing in different states.

This RPC Method returns the height of the fully-validated chain. The genesis block has a height of 0.

This RPC Method returns the BIP-157 compact block filter and filter header for a given block.

This RPC Method returns the hash of the block provided its height.

This RPC Method returns the header of the block given it's hash.

This RPC Method calculates per block statistics for a given window.

This RPC Method returns information about all known chaintips in the block tree, including the main chain as well as orphaned branches.

This RPC Method calculates data about the total number and rate of transactions in the chain.

This RPC Method returns the proof-of-work difficulty as a multiple of the minimum difficulty.

This RPC Method returns all in-mempool ancestors for a transaction in the mempool.

This RPC Method returns all in-mempool descendants for a transaction in the mempool.

This RPC Method returns detailed mempool entry data for a specific transaction.

This RPC Method returns mempool statistics such as size, bytes, usage, and limits.

This RPC Method returns all transaction IDs currently in the mempool.

This RPC Method returns details about an unspent transaction output (UTXO).

This RPC Method returns a proof that specific transactions are included in a block.

This RPC Method creates an unsigned raw transaction from inputs and outputs.

This RPC Method decodes a serialized raw transaction hex into a JSON object.

This RPC Method decodes a hex-encoded script into a JSON object.

This RPC Method returns detailed information about a raw transaction by txid.

This RPC Method submits a raw signed transaction to the network.

This RPC Method tests whether a raw transaction would be accepted by the mempool.

This RPC Method creates a multisig address and redeem script from a set of public keys.

This RPC Method estimates the transaction fee per kilobyte needed for confirmation within a target number of blocks.

This RPC Method verifies whether a Bitcoin address is valid and provides related info.

This RPC Method verifies that a signed message was created with the private key corresponding to a given address.

This endpoint can be used to get the latest Bitcoin price

Use this endpoint to register a portfolio address for continuous balance tracking.

Xverse API will automatically keep its daily balance and activity updated.

This endpoint returns all the registered portfolio addresses for the current API key.

This RPC Method returns information about the block.

Automate Ordinal inscriptions with advanced features. Estimate costs, create orders, and track inscription statuses seamlessly.

Query Rune balances, metadata & trading data.

Integrate Runes into your apps without building infra.

Mint and etch Runes, with cost estimates, order management and execution.

This endpoint is commonly used to pass an ordinal collection ID, and get the full list of wallets holding inscriptions in that collection, and the number of items of the collection they hold.

This endpoint provides the historical floor price for a specific collection and a given time period.

Collection prices are sourced from multiple ordinals marketplaces.

This endpoint is commonly used to retrieve the list of inscriptions associated with an ordinal collection, together with their info and metadata.

This endpoint returns the information & metadata of a specific inscription ID.

This endpoint provides the top collections by sales volume for different time periods, along with collections' metadata & market data.

This endpoint returns the full activity history (transfers, listings, sales) for a specific inscription.

Returns a generated thumbnail image for the specified inscription ID

This endpoint returns the information & metadata for multiple inscription IDs in a single request.

Use this endpoint to retrieve the daily balance history for a registered portfolio address over a specific time period.

This endpoint returns the full list of indexed Ordinals collections with their basic information and metadata

This endpoint is used to retrieve the metadata & market data associated with an ordinal collection, based on the ordinal collection ID.

Returns historical activity (transfers, mints, etc.) for a specific Rune held by a given address.

This endpoint returns all Ordinal collections held by a given wallet address, along with the list of inscriptions owned within each collection.

This endpoint is used to retrieve the metadata & market data associated with a rune, based on the rune ID.

Search existing Runes by name, order results by name or by etching block + index.

This endpoint is used to retrieve the metadata & market data associated with a batch of up to 10 runes, based on the runes' IDs, in a single request.

This endpoint provides the historical floor price for a specific collection and a given time period.

This endpoint is commonly used to pass a rune ID, and get the full list of wallets holding the rune, and the amount they hold.

The Xverse API lets you watch blockchain addresses and receive transaction events as they happen.

This is built for apps that need to react to on-chain activity — without polling — such as wallets, payment flows, portfolio trackers, and backend reconciliation systems.

Address watching is currently available for Bitcoin. Support for Spark and Starknet webhooks is coming soon.

🔔 Transaction Webhooks

Webhooks are how Xverse delivers address activity events to your application.

Once a webhook subscription is registered for a set of addresses:

• Xverse monitors the addresses

• Transaction events are pushed to your backend via HTTP POST

• No custom indexing or node infrastructure is required

You can subscribe to:

• Incoming transactions

• Outgoing transactions

Start watching a set of addresses.

• Registers the address for transaction monitoring

• Enables webhook notifications for relevant transactions involving the addresses

When a transaction involving any of the watched addresses is confirmed, Xverse sends a POST request to your webhook URL:

Payloads for Spark and Starknet will follow a similar structure.

Returns all active address-watching webhook subscriptions for your API key.

Use this to

• Inspect active address watchers

• Debug webhook behavior

• Manage multiple monitored sets of addresses

Stop watching a set of addresses by deleting the webhook subscription.

Use this to

• Stop receiving notifications for an address

• Clean up unused subscriptions

The Xverse API supports the Machine Payments Protocol (MPP) — a pay-per-request authentication method over the Lightning Network. Instead of provisioning an API key, your client can pay a small Lightning invoice for each request.

This is built for AI agents and autonomous clients that need to access the API without human-managed credentials. Agents using the handle MPP payments transparently — the agent calls an endpoint, the wallet pays the Lightning invoice in the background, and the response comes back. No checkout, no human approval, no API key.

MPP is an open standard defined at . Any Lightning-compatible wallet or SDK can use it.

MPP uses an HTTP 402 challenge-response flow:

Send a request to any endpoint without an x-api-key or Authorization header. The server responds with

The Xverse MCP server provides a standardized interface that allows any compatible AI model or agent to access Bitcoin blockchain data through the Xverse API — including Bitcoin transactions, Ordinals, Runes, BRC-20, Spark, and swap quotes.

Connect to the MCP server natively in Claude, Cursor, and other clients, or use the mcp-remote module for backwards compatibility with clients that do not support remote MCP.

The Xverse MCP server is centrally hosted, uses Streamable HTTP transport, and authenticates with your existing Xverse API key. It exposes 54 read-only tools across Bitcoin, Ordinals, Runes, BRC-20, Spark, and Swaps — with more functionality on the way.

Setup Instructions

General

The MCP server supports Streamable HTTP transport and authenticates via your Xverse API key passed as a Bearer token:

https://mcp.secretkeylabs.io/mcp

Authentication: Authorization: Bearer <your-api-key>

You can get an API key from the Get Started page.

Then run /mcp once you've opened a Claude Code session to verify the connection.

CTRL/CMD + , to open Cursor settings. Navigate to the MCP tools page and add a new server with the following configuration:

CTRL/CMD + P and search for MCP: Add Server. Select Command (stdio) and enter:

Enter the name Xverse and hit enter. Activate the server using MCP: List Servers, selecting Xverse, and selecting Start Server.

Alternatively, add to your VS Code MCP settings file:

Run the following command in Terminal:

If this is your first MCP in Codex, enable the rmcp feature first:

CTRL/CMD + , to open Windsurf settings. Scroll to Cascade → MCP servers, select Add Server → Add custom server, and add:

CMD + , to open Zed settings. Add the following:

Many tools now support MCP servers. Configure them with the following settings:

The MCP server exposes 54 read-only tools organized by domain. All tools correspond to endpoints in the Xverse API.

The MCP server uses your Xverse API key as a Bearer token. Pass it in the Authorization header on connection. The same API key you use for REST API calls works with the MCP server — no separate credentials needed.

Yes, at the https://mcp.secretkeylabs.io/mcp endpoint.

No. The MCP server is currently read-only. It provides data access and swap quotes but does not execute transactions, mint tokens, or modify any on-chain state. Write operations may be added in the future.

The same rate limits from your Xverse API plan apply. If you hit a rate limit, the MCP server will return an error with Retry-After guidance so the AI agent can wait and retry automatically.

1. Verify your API key is valid and correctly formatted (UUID format: 8-4-4-4-12 hex characters).

2. If using mcp-remote, make sure you have a recent version of Node.js installed.

3. Try clearing cached auth info: rm -rf ~/.mcp-auth and reconnect.

Any client that supports the can connect. This includes Claude (Code, Desktop, and claude.ai), Cursor, VS Code, Codex, Windsurf, Zed, and many others. Clients that support Streamable HTTP can connect directly; older clients can use the mcp-remote bridge.