API

The Rebar API provides structured access to Bitcoin-native assets and metaprotocol activity, empowering developers to build MEV-aware infrastructure directly on Bitcoin L1.

The Rebar Labs API is a RESTful interface that enables real-time and historical access to key metaprotocol data on Bitcoin L1. As Bitcoin DeFi expands atop protocols like Runes and Alkanes, developer access to verifiable, accurate data will be a competitive edge. The Rebar Labs API is positioned as the core infrastructure layer for interacting with Bitcoin-native assets, preserving L1 security while enabling programmable coordination.

All of our endpoints are secure and require authentication. You can request an API key via our contact form: https://rebarlabs.io/contact.

The API includes coverage for:

• Ordinals: Track inscription metadata, transfer history, sat position, and rarity classification.

• BRC-20s: Query token balances, minting events, transfer logs, and protocol compliance status.

• Runes: Monitor etching events, rune deployment data, and transaction flow across unspent outputs.

Endpoints follow consistent schemas and emphasize:

• Bitcoin-native primitives (e.g., txid, vout, scriptPubKey)

• Indexed metaprotocol overlays (e.g., ordinal IDs, rune tickers)

• MEV-sensitive transaction ordering metadata (e.g., mempool timestamps, miner-included position)

Developer Integration

Developers can integrate the API for a range of use cases:

• Build wallets that visualize Ordinals and BRC-20 balances with accurate UTXO tracking

• Track mint congestion and rarity volatility for BRC-20 and Runes

• Simulate MEV opportunities and protection strategies within Alkane contract flows

Authentication is via API key, with support for both public and private scopes. Rate limits are tiered to support dApp-level traffic as well as individual developer exploration. It is not required for public scoped endpoints but does affect rate limit applied.

Request your API key via our contact form: https://rebarlabs.io/contact.