Is this the same interface as running bitcoind myself?

Yes. BoltRPC exposes Bitcoin Core's JSON-RPC methods with their standard names, parameters and response shapes. Code written against a local node works by swapping the URL.

Can I broadcast transactions through BoltRPC?

Yes. sendrawtransaction is fully supported: sign locally, broadcast through your endpoint, and the transaction propagates from well-connected nodes.

Does Bitcoin have smart contracts or an EVM?

No. Bitcoin is a UTXO chain without a general-purpose VM. For programmable BTC, look at BOB, the Bitcoin-focused EVM rollup BoltRPC also serves.

How do confirmations work on Bitcoin?

Bitcoin finality is probabilistic: each block on top of a transaction makes reversal exponentially less likely. Exchanges conventionally credit deposits after 1-6 confirmations depending on amount.

Why not run my own Bitcoin node?

A production Bitcoin Core node needs hundreds of gigabytes of fast storage, days of initial sync and ongoing maintenance, and a second node for redundancy. A dedicated endpoint gives the same interface without the operations.

Does BoltRPC support WebSocket for Bitcoin?

No, Bitcoin Core's RPC interface is HTTP-based and has no WebSocket subscription model. Poll getblockcount for new blocks.

Bitcoin RPC Endpoint

Direct Bitcoin Core JSON-RPC without running your own node: blocks, transactions, fee estimates and broadcasts on a dedicated endpoint.

JSON-RPC 2.0

Start free trial Contact sales

LIVE LATENCY

37ms

LIVE

gateway round-trip · sampled every second

IN PRODUCTION AT Chainlink

Your endpoint, ready in one line.

Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.

HTTPS

https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/bitcoin

Replace YOUR_API_KEY with your API key. Get a free key →

Pick your stack.

Copy-paste examples for the libraries you already use. Swap the API key, hit run.

const url = "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/bitcoin";

const res = await fetch(url, {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    jsonrpc: "1.0",
    id: 1,
    method: "getblockchaininfo",
    params: [],
  }),
});
const { result } = await res.json();
console.log("Height:", result.blocks);

import requests

url = "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/bitcoin"
payload = {"jsonrpc": "1.0", "id": 1, "method": "getblockchaininfo", "params": []}

r = requests.post(url, json=payload)
print("Height:", r.json()["result"]["blocks"])

curl https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/bitcoin \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"1.0","id":1,"method":"getblockchaininfo","params":[]}'

Connect your exchange, payment processor, or indexer to Bitcoin Mainnet with BoltRPC. You get direct Bitcoin Core JSON-RPC access, the same interface as running your own full node, with predictable request-unit pricing and none of the sync, storage or maintenance burden.

Chain at a Glance


Protocol	Bitcoin Core JSON-RPC
Block time	~10 minutes
Model	UTXO (no accounts, no smart contract VM)
Native asset	BTC
Finality	Probabilistic (6 confirmations convention)
EVM compatible	No

What Bitcoin Infrastructure Actually Requires

Bitcoin looks simple from a distance, one asset, ten-minute blocks, but running production Bitcoin infrastructure is its own discipline. A synced Bitcoin Core node with transaction indexing needs hundreds of gigabytes of fast storage, takes days to sync from genesis, and must be maintained through every Core release. That is why exchanges, payment processors and analytics firms, among the heaviest RPC consumers in crypto, increasingly outsource the node and keep the interface: Bitcoin Core’s JSON-RPC, unchanged. Deposit detection scans every block for relevant outputs, fee estimation runs before every withdrawal batch, and broadcast reliability decides whether a user’s withdrawal confirms this block or three blocks later. BoltRPC serves that interface on dedicated infrastructure, one HTTP POST away.

Common Use Cases on Bitcoin

Exchange deposit and withdrawal infrastructure Scanning every block for deposits and broadcasting withdrawal batches is the classic Bitcoin workload: block-by-block getblock reads, getrawtransaction lookups and scheduled sendrawtransaction calls, around the clock.

Payment processors Invoice systems watch addresses for incoming payments and confirm them at target depth. Reliable chain-tip tracking and transaction lookups directly gate the customer’s checkout experience.

Analytics and proof-of-reserves UTXO analysis, balance attestations and flow tracking read large ranges of blocks and transactions, a read-heavy batch workload where fixed per-method pricing keeps large jobs predictable.

Bridges and Bitcoin L2s Bridge watchers verify BTC deposits before minting representations on other chains. They need a Bitcoin view they can trust and query heavily, often alongside an EVM endpoint like BOB from the same provider.

Built for teams that ship on Bitcoin.

A full node without the full node

Bitcoin Core JSON-RPC with the exact method names and response shapes of a local bitcoind, but no multi-day sync, no storage bill, no version maintenance. Existing integrations move over by changing one URL.

Built for deposit detection

Exchanges and payment processors scan every new block for customer deposits. Block-by-block reads with getblock and getrawtransaction are sustained, predictable load, priced with fixed request-unit weights, never surge-priced.

Reliable broadcasts

sendrawtransaction against well-connected nodes propagates withdrawals fast. When a user is watching a pending withdrawal, broadcast reliability is customer support load you don't get.

Fee estimation that tracks the mempool

estimatesmartfee against nodes with a live mempool view keeps withdrawal batches confirmed on schedule without systematically overpaying fees.

Bitcoin and its L2s from one provider

BoltRPC serves Bitcoin Core alongside BOB, the Bitcoin-focused EVM rollup, plus Ethereum, Solana and 20+ other networks behind one dashboard and one key pattern.

Full JSON-RPC coverage.

Every standard Bitcoin method you would expect. Archive-only methods are available on request for qualifying plans.

STANDARD6

getblockchaininfogetblockgetrawtransactionsendrawtransactionestimatesmartfeegetblockcount

Bitcoin, explained.

Common questions about connecting to Bitcoin over BoltRPC.

Ask a question →Read the docs

: The Bitcoin Mainnet RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/bitcoin. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io and POST standard Bitcoin Core JSON-RPC bodies to it.
: Yes. BoltRPC exposes Bitcoin Core's JSON-RPC methods with their standard names, parameters and response shapes. Code written against a local node works by swapping the URL; no cookie or rpcuser/rpcpassword setup is needed, the API key in the URL authenticates you.
: Yes. sendrawtransaction is fully supported: sign locally, broadcast through your endpoint, and the transaction propagates from our well-connected nodes.
: No. Bitcoin is a UTXO chain without a general-purpose VM. For programmable BTC, lending, DeFi, wrapped Bitcoin, look at BOB, the Bitcoin-focused EVM rollup BoltRPC also serves.
: Bitcoin finality is probabilistic: each ~10-minute block on top of a transaction makes reversal exponentially less likely. Exchanges conventionally credit deposits after 1-6 confirmations depending on amount; track depth by comparing the transaction's block height with getblockcount.
: A production Bitcoin Core node with transaction indexing needs hundreds of gigabytes of fast storage, days of initial sync and ongoing maintenance through every release, and then you need a second one for redundancy. A dedicated endpoint gives you the same interface with the operations handled by an ISO 27001 certified operator.
: No, Bitcoin Core's RPC interface is HTTP-based and has no WebSocket subscription model. Poll getblockcount for new blocks (a new block arrives roughly every 10 minutes, so light polling is enough).

Ship on Bitcoin this week.

An API key in under 60 seconds, Bitcoin plus 34 other chains, and a team that answers when you write.

Start free trial View pricing