Coin Metrics Python API Docs | dltHub

Build a Coin Metrics-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Coin Metrics provides a REST API to access institutional-grade cryptocurrency market and reference data. The REST API base URL is https://api.coinmetrics.io/v4 (for professional data) or https://community-api.coinmetrics.io/v4 (for community data) and API key is provided via a query parameter for paid endpoints, while community endpoints do not require authentication..

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 add "dlt[hub]" and start loading Coin Metrics data in under 10 minutes.


What data can I load from Coin Metrics?

Here are some of the endpoints you can load from Coin Metrics:

ResourceEndpointMethodData selectorDescription
assetsreference-data/assetsGETdataLists all supported assets.
exchangesreference-data/exchangesGETdataLists all supported exchanges.
marketsreference-data/marketsGETdataLists all supported markets.
indexesreference-data/indexesGETdataLists all supported indexes.
asset_metricstimeseries/asset-metricsGETdataRetrieves time series asset metrics.

How do I authenticate with the Coin Metrics API?

The API uses a query parameter named 'api_key' for authentication. This key should be appended to requests, e.g., ?api_key=YOUR_API_KEY.

1. Get your credentials

To obtain an API key for the Coin Metrics Pro API, you must request it directly by contacting their team through the official contact page at https://coinmetrics.io/contact/ or their institutional data request form. There is no self-service dashboard for generating API keys; they are provisioned upon account setup for institutional users. Once received, the key is typically passed as a query parameter named api_key in your HTTP requests.

2. Add them to .dlt/secrets.toml

[sources.coin_metrics_source] api_key = "your_api_key_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 init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub 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:

uv run dlthub ai toolkit install rest-api-pipeline

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 Coin Metrics 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:

uv run python coin_metrics_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline coin_metrics_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset coin_metrics_data The duckdb destination used duckdb:/coin_metrics.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub 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 catalog and timeseries/asset-metrics from the Coin Metrics 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 coin_metrics_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.coinmetrics.io/v4 (for professional data) or https://community-api.coinmetrics.io/v4 (for community data)", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "assets", "endpoint": {"path": "v4/reference-data/assets", "data_selector": "data"}}, {"name": "asset_metrics", "endpoint": {"path": "v4/timeseries/asset-metrics", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="coin_metrics_pipeline", destination="duckdb", dataset_name="coin_metrics_data", ) load_info = pipeline.run(coin_metrics_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("coin_metrics_pipeline").dataset() sessions_df = data.asset_metrics.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM coin_metrics_data.asset_metrics LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("coin_metrics_pipeline").dataset() data.asset_metrics.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 Coin Metrics data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Coin Metrics?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines