Every inscription.
Every Rune.
One API.
Query inscriptions, satoshi metadata, Rune details, and collection data through JSON-RPC and ORD-compatible REST API on your Quicknode endpoint. No custom indexer.
Every Ordinals and Runes dataset,
query-ready.
Raw Bitcoin RPC exposes blocks and transactions but does not index Ordinals, satoshi data, or Rune metadata. Building that layer yourself means block scanning, custom databases, and ongoing maintenance. The Ordinals & Runes API indexes it for you.
sat 1,452,891,330,221,420
Look up any inscription, down to its satoshi.
Query inscriptions by ID to retrieve content type, content length, metadata, and associated satoshi data. Access satoshi rarity classification, percentile, associated inscriptions, and paginated collection listings without custom indexing.
UNCOMMON•GOODS
etched 840,000 · divisibility 0
Runes from etching to live supply
Fetch Rune metadata including etching details, supply information, divisibility, and minting parameters via ord_getRune. Browse paginated Rune listings and query Bitcoin outputs for the inscriptions and Runes they contain.
ord_getInscription
id: 6fb9…ac2di0
GET /inscription/:id
200 · application/json
Two interfaces. The endpoint you already run.
Call methods through JSON-RPC or ORD-compatible REST. No new URL, no migration. Activate from the dashboard.
Fetch, browse, and inspect
any inscription or Rune.
21 methods cover inscriptions, satoshi metadata, Runes, and Bitcoin outputs. Standard Bitcoin RPC does not. Here is what you can pull:
An inscription by ID
Satoshi rarity, percentile, and linked inscriptions
Bitcoin outputs and the inscriptions or Runes they contain
Paginated collections and inscriptions
Rune metadata and etching details
Block-level and child inscriptions
One API behind every Ordinals app.
Wallets, explorers, marketplaces, analytics, and trackers. All powered by the same indexed API.
One piece of the
complete Bitcoin stack
Ordinals & Runes API attaches to your existing Quicknode Bitcoin endpoint, alongside Core RPC, Streams, Webhooks, and Blockbook on the same account, with no separate vendors to wire together.
Core RPC API
Raw Bitcoin JSON-RPC on the same endpoint Ordinals & Runes API attaches to. No separate provider.
Streams
Push new blocks and address activity to your backend as they confirm. No polling.
Webhooks
Fire HTTP callbacks on the onchain events your product cares about.
Blockbook
Address-level transaction history and UTXO data for Bitcoin. Indexed and queryable.
Ordinals & Runes API
21 JSON-RPC and ORD-compatible REST methods for inscriptions, satoshi metadata, and Runes on Bitcoin.
Need Another Dataset?
Request additional indexed datasets. Our team evaluates coverage requests as Bitcoin indexing expands.
| Ordinals indexing | Real-time push | Address indexing | Raw Bitcoin RPC | Fully managed | One account, one bill | |
|---|---|---|---|---|---|---|
| Quicknode | ||||||
| Standalone indexer | — | — | — | — | ||
| Self-hosted / DIY | — | — | — |
Ship your Ordinals app on Quicknode.
Activate from your dashboard. No migration, nothing to provision.
Frequently Asked Questions
Specifics on supported data, pricing, and how the Ordinals & Runes API attaches to your endpoint.Still have questions? Contact support.
What is the Ordinals & Runes API?
What data does the Ordinals & Runes API expose?
How is the Ordinals & Runes API different from raw Bitcoin RPC?
What interfaces does the API support?
How much does the Ordinals & Runes API cost?
How do I enable the Ordinals & Runes API on my endpoint?