Mempool Python API Docs | dltHub
Build a Mempool-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Mempool.space provides a REST API for accessing Bitcoin data, including transactions, addresses, blocks, and mining information. The API supports various endpoints for real-time and historical data. Use the API to query details about the Bitcoin network. The REST API base URL is https://mempool.space/api and optional header‑based X‑Mempool‑Auth for accelerator endpoints (no API key required for public endpoints).
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Mempool data in under 10 minutes.
What data can I load from Mempool?
Here are some of the endpoints you can load from Mempool:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| difficulty_adjustment | /api/v1/difficulty-adjustment | GET | Returns difficulty adjustment details (object) | |
| prices | /api/v1/prices | GET | Returns Bitcoin price information (object) | |
| address | /api/address/:address | GET | Address details with chain and mempool stats (object) | |
| address_txs_chain | /api/address/:address/txs/chain | GET | Confirmed transactions for an address (top‑level array) | |
| address_utxo | /api/address/:address/utxo | GET | List of UTXOs for an address (top‑level array) | |
| block | /api/block/:hash | GET | Block details (object) | |
| blocks_tip_height | /api/blocks/tip/height | GET | Current tip height (primitive) | |
| mempool | /api/mempool | GET | Mempool statistics (object) | |
| mempool_txids | /api/mempool/txids | GET | List of mempool transaction IDs (top‑level array) | |
| mempool_recent | /api/mempool/recent | GET | Recent mempool transactions (top‑level array) | |
| tx | /api/tx/:txid | GET | Transaction details (object) | |
| tx_hex | /api/tx/:txid/hex | GET | Hex‑encoded transaction (string) | |
| tx_outspends | /api/tx/:txid/outspends | GET | Spending status of outputs (top‑level array) | |
| fees_recommended | /api/v1/fees/recommended | GET | Recommended fee rates (object) | |
| fees_precise | /api/v1/fees/precise | GET | Precise fee rates (object) | |
| lightning_nodes | /api/v1/lightning/nodes/country/:country | GET | Lightning nodes by country (top‑level array) | |
| accelerator_top_up_history | /api/v1/services/accelerator/top-up-history | GET | Authenticated accelerator top‑up history (top‑level array) | |
| accelerator_balance | /api/v1/services/accelerator/balance | GET | Authenticated accelerator balance (object) |
How do I authenticate with the Mempool API?
The public endpoints require no authentication. Private accelerator endpoints require an X-Mempool-Auth header containing a provider‑issued token.
1. Get your credentials
- Contact the mempool.space team or the specific accelerator service (e.g., Stacksats) to request an X‑Mempool‑Auth token.
- Provide your account details and the intended use case.
- Receive the token (e.g., "stacksats") which you will include in the
X-Mempool-Authheader for accelerator endpoints. - Store the token in your secrets.toml as shown in the
secrets_toml_examplesection.
2. Add them to .dlt/secrets.toml
[sources.mempool_source] x_mempool_auth = "your_x_mempool_auth_token_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
dlt ai toolkit rest-api-pipeline install
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Mempool API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
python mempool_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline mempool_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset mempool_data The duckdb destination used duckdb:/mempool.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline mempool_pipeline show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads mempool_recent and tx from the Mempool API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def mempool_source(x_mempool_auth=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://mempool.space/api", "auth": { "type": "api_key", "x_mempool_auth": x_mempool_auth, }, }, "resources": [ {"name": "mempool_recent", "endpoint": {"path": "api/mempool/recent"}}, {"name": "tx", "endpoint": {"path": "api/tx/:txid"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="mempool_pipeline", destination="duckdb", dataset_name="mempool_data", ) load_info = pipeline.run(mempool_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("mempool_pipeline").dataset() sessions_df = data.mempool_recent.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM mempool_data.mempool_recent LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("mempool_pipeline").dataset() data.mempool_recent.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Mempool data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Mempool?
Request dlt skills, commands, AGENT.md files, and AI-native context.