GoldRush Python API Docs | dltHub
Build a GoldRush-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
GoldRush (formerly Covalent) is a REST API for accessing historical and near-real-time blockchain data across multiple chains. The REST API base URL is https://api.covalenthq.com/v1 and all requests require a Bearer token in the Authorization header.
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 GoldRush data in under 10 minutes.
What data can I load from GoldRush?
Here are some of the endpoints you can load from GoldRush:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| token_balances | /v1/{chain}/address/{wallet}/balances_v2/ | GET | Get token balances for address | |
| transactions | /v1/{chain}/address/{wallet}/transactions_v3/ | GET | Get paginated transactions for address | |
| log_events | /v1/{chain}/events/address/{contractAddress}/ | GET | Get log events by contract address | |
| nft_holdings | /v1/{chain}/address/{wallet}/balances_nft/ | GET | Get NFT holdings for address | |
| block_details | /v1/{chain}/block_v2/{blockHeight}/ | GET | Get details for a specific block | |
| token_prices | /v1/pricing/historical_by_addresses_v2/{chain}/{currency}/{contract}/ | GET | Get historical token prices | |
| chains | /v1/chains/ | GET | Get list of all supported chains |
How do I authenticate with the GoldRush API?
All requests must include an API key as a Bearer token in the Authorization HTTP header (e.g., 'Authorization: Bearer <API_KEY>').
1. Get your credentials
To obtain credentials for GoldRush, sign in to the GoldRush Platform at https://goldrush.dev/platform/. Navigate to your account settings. For the Foundational, Streaming, CLI, or x402 APIs, use your standard GoldRush API key (prefixed with cqt_ or ckey_). For the Pipeline REST API, you must create a dedicated ServiceKey under the Service Keys section in your account settings; these keys are shown only once at creation.
2. Add them to .dlt/secrets.toml
[sources.goldrush_source] api_key = "cqt_your_api_key_here" service_key = "your_service_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 GoldRush 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 goldrush_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline goldrush_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset goldrush_data The duckdb destination used duckdb:/goldrush.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 /platform/pipeline-api/ and /platform/pipeline-api/{id}/ from the GoldRush 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 goldrush_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.covalenthq.com/v1", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "transactions", "endpoint": {"path": "/v1/{chain}/address/{wallet}/transactions_v3/", "data_selector": "items"}}, {"name": "token_balances", "endpoint": {"path": "/v1/{chain}/address/{wallet}/balances_v2/", "data_selector": "items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="goldrush_pipeline", destination="duckdb", dataset_name="goldrush_data", ) load_info = pipeline.run(goldrush_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("goldrush_pipeline").dataset() sessions_df = data.transactions.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM goldrush_data.transactions LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("goldrush_pipeline").dataset() data.transactions.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 GoldRush 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 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 GoldRush?
Request dlt skills, commands, AGENT.md files, and AI-native context.