Runes

The Runes API provides structured access to Bitcoin-native fungible tokens etched via the Runes protocol, exposing both metadata and transaction flow for precision indexing and analytics.

Runes are a Bitcoin-native standard for fungible tokens that operate directly on the UTXO model. Unlike off-chain or L2 solutions, Runes embed token logic within standard Bitcoin transactions, inheriting Bitcoin’s security guarantees without requiring additional infrastructure. As the protocol gains adoption, developers need visibility into etching events, token balances, and transfer flows to power wallets, dApps, and indexing infrastructure.

Technical Deep Dive

The Runes API surfaces all key aspects of the protocol, built for latency-sensitive environments and Bitcoin-native primitives.

The process involves:

• Etch tracking: Query and filter all known Rune tickers and metadata, including supply and etch timestamps.

• Balance resolution: Return user balances and associated UTXOs to support wallet UX and asset visibility.

• Transfer history: Fetch on-chain token movement with miner-inclusion timing for MEV analysis.

• MEV context: Optional ordering metadata (e.g., mempool arrival time, mined block height) supports front-running and reordering detection.

All endpoints return Bitcoin transaction identifiers (e.g., txid, vout) and adhere strictly to Bitcoin’s native data types.

Key endpoints include:

• GET /runes: List all etched runes with metadata

• GET /runes/{ticker}: Retrieve a specific Rune's metadata and supply

• GET /runes/{ticker}/balances/{address}: Fetch the Rune balance and underlying UTXOs for a Bitcoin address

• GET /runes/{ticker}/transfers: Stream historical Rune transfers with transaction context

Practical Implementation

Developers can leverage the Runes API to:

• Power wallet interfaces with real-time Rune balances and ticker metadata

• Monitor mint surges and etch events for speculative trading signals

• Build block explorers and analytics dashboards for Runes protocol activity

• Simulate MEV threats by modeling transfer order impact or rare etching competition

The API is accessible via authenticated REST requests and supports pagination and filter parameters for scalable data ingestion.