Token Metrics Python API Docs | dltHub
Build a Token Metrics-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Token Metrics is an AI‑powered cryptocurrency analysis platform that provides market data, grading, and trading signals via a REST API. The REST API base URL is https://api.tokenmetrics.com/v2 and All requests require an API key passed in the request headers..
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 Token Metrics data in under 10 minutes.
What data can I load from Token Metrics?
Here are some of the endpoints you can load from Token Metrics:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| trading_signals | /trading-signals | GET | AI‑generated buy/sell/hold recommendations | |
| price | /price | GET | Current price data for all supported tokens | |
| tokens | /tokens | GET | Metadata and basic info for each token | |
| tm_grade | /tm-grade | GET | AI grading score for each token | |
| daily_ohlcv | /daily-ohlcv | GET | Historical OHLCV data on a daily basis | |
| hourly_ohlcv | /hourly-ohlcv | GET | Historical OHLCV data on an hourly basis | |
| market_metrics | /market-metrics | GET | Broad market metrics and aggregates | |
| indices | /indices | GET | List of crypto indices provided by Token Metrics | |
| ai_reports | /ai-reports | GET | Detailed AI analysis reports | |
| scenario_analysis | /scenario-analysis | GET | Scenario‑based forecasts and simulations |
How do I authenticate with the Token Metrics API?
Include the API key in the request header, for example Authorization: Bearer <API_KEY>.
1. Get your credentials
- Log in to https://app.tokenmetrics.com/en/api.
- Navigate to the API section.
- Click “Create New API Key”.
- Copy the generated key and store it securely.
- Use this key in the
Authorizationheader of each request.
2. Add them to .dlt/secrets.toml
[sources.token_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 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 Token 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:
python token_metrics_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline token_metrics_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset token_metrics_data The duckdb destination used duckdb:/token_metrics.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline token_metrics_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 trading_signals and price from the Token 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 token_metrics_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.tokenmetrics.com/v2", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "trading_signals", "endpoint": {"path": "trading-signals"}}, {"name": "price", "endpoint": {"path": "price"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="token_metrics_pipeline", destination="duckdb", dataset_name="token_metrics_data", ) load_info = pipeline.run(token_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("token_metrics_pipeline").dataset() sessions_df = data.trading_signals.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM token_metrics_data.trading_signals LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("token_metrics_pipeline").dataset() data.trading_signals.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 Token Metrics 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.
Troubleshooting
Authentication Errors
- 401 Unauthorized – Occurs when the API key is missing, malformed, or invalid. Ensure the
Authorizationheader contains a valid key.
Rate Limiting
- 429 Too Many Requests – The API enforces a request quota per minute. Implement exponential backoff and respect the
Retry-Afterheader.
Pagination
- Some list endpoints return a
next_pagetoken in the JSON response. Use this token as a query parameter (page_token) to retrieve subsequent pages.
General HTTP Errors
- 5xx Server Errors – Transient issues on the provider side; retry after a short delay.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
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 Token Metrics?
Request dlt skills, commands, AGENT.md files, and AI-native context.