GerryChain Python API Docs | dltHub
Build a GerryChain-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
GerryChain is a Python library for using Markov Chain Monte Carlo methods to study political redistricting. The REST API base URL is `` and No authentication required..
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 GerryChain data in under 10 minutes.
What data can I load from GerryChain?
Here are some of the endpoints you can load from GerryChain:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| bg_census_consolidated | https://raw.githubusercontent.com/mggg/GerryChain/main/docs/_static/05_bg_census_consolidated.json | GET | features | Consolidated block‑group census data used by GerryChain |
| pa_vtds | https://raw.githubusercontent.com/mggg/GerryChain/main/docs/_static/PA_VTDs.json | GET | features | Pennsylvania VTDs GeoJSON data |
| api_reference | https://mggg.github.io/GerryChain/api.html | GET | HTML documentation of the Python API | |
| docs_home | https://mggg.github.io/GerryChain/ | GET | Main documentation site for GerryChain | |
| readme | https://github.com/mggg/GerryChain/blob/main/README.rst | GET | Project README with overview and usage |
How do I authenticate with the GerryChain API?
Not applicable; access is via installing the Python package and reading local/static JSON files in the repository.
1. Get your credentials
Not applicable.
2. Add them to .dlt/secrets.toml
[sources.gerry_chain_source]
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 GerryChain 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 gerry_chain_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline gerry_chain_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset gerry_chain_data The duckdb destination used duckdb:/gerry_chain.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline gerry_chain_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 from the GerryChain 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 gerry_chain_source(=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "", "auth": { "type": "", "": , }, }, "resources": [ {"name": "bg_census_consolidated", "endpoint": {"path": "https://raw.githubusercontent.com/mggg/GerryChain/main/docs/_static/05_bg_census_consolidated.json", "data_selector": "features"}}, {"name": "pa_vtds", "endpoint": {"path": "https://raw.githubusercontent.com/mggg/GerryChain/main/docs/_static/PA_VTDs.json", "data_selector": "features"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="gerry_chain_pipeline", destination="duckdb", dataset_name="gerry_chain_data", ) load_info = pipeline.run(gerry_chain_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("gerry_chain_pipeline").dataset() sessions_df = data.bg_census_consolidated.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM gerry_chain_data.bg_census_consolidated LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("gerry_chain_pipeline").dataset() data.bg_census_consolidated.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 GerryChain 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
Installation errors
- ImportError: Ensure
gerrychainand its dependencies are installed viapip install gerrychain. - Version conflicts: Use a virtual environment to avoid package clashes.
Data loading errors
- FileNotFoundError: Verify the path or URL to the static JSON file is correct.
- JSONDecodeError: The JSON file may be corrupted; re‑download from the repository.
- KeyError (e.g., missing
features): Confirm the JSON structure matches the expected GeoJSON format.
Performance / memory issues
- Large census files can consume significant memory; consider streaming or loading only needed attributes.
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 GerryChain?
Request dlt skills, commands, AGENT.md files, and AI-native context.