Arcadia Signal API Python API Docs | dltHub
Build a Arcadia Signal API-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Arcadia Signal is an energy-data platform providing programmatic access to North American electricity tariff data and a bill-calculation engine. The REST API base URL is https://api.genability.com and All requests require HTTP Basic 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 Arcadia Signal API data in under 10 minutes.
What data can I load from Arcadia Signal API?
Here are some of the endpoints you can load from Arcadia Signal API:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| tariffs | /rest/public/tariffs | GET | Get a list of all tariffs. | |
| lses | /rest/public/lses | GET | Get a list of all Load Serving Entities (utilities). | |
| tariffs_by_id | /rest/public/tariffs/{masterTariffId} | GET | Get a single tariff by its ID. | |
| lses_by_id | /rest/public/lses/{lseId} | GET | Get a single LSE by its ID. | |
| echo | /rest/public/echo/authenticate | GET | Validate app credentials. |
How do I authenticate with the Arcadia Signal API API?
Arcadia Signal API uses HTTP Basic authentication. You must pass your appId as the username and your appKey as the password, or provide an Authorization: Basic header containing the Base64-encoded appId
string.1. Get your credentials
To obtain your API credentials for the Arcadia Signal API, log in to the Arcadia dashboard (often referred to as 'Dash by Arcadia'). Within the platform, locate your application or API integration settings to generate or retrieve your 'appId' and 'appKey'. Once retrieved, you can validate these credentials using the 'Echo Authenticate' endpoint provided in the Arcadia documentation to ensure they are active and configured correctly.
2. Add them to .dlt/secrets.toml
[sources.arcadia_signal_api_source] appId:appKey = "REPLACE_ME"
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 Arcadia Signal API 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 arcadia_signal_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline arcadia_signal_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset arcadia_signal_api_data The duckdb destination used duckdb:/arcadia_signal_api.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 lses and tariffs from the Arcadia Signal API 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 arcadia_signal_api_source(appid_appkey=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.genability.com", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": appid_appkey}, }, "resources": [ {"name": "tariffs", "endpoint": {"path": "rest/public/tariffs"}}, {"name": "lses", "endpoint": {"path": "rest/public/lses"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="arcadia_signal_api_pipeline", destination="duckdb", dataset_name="arcadia_signal_api_data", ) load_info = pipeline.run(arcadia_signal_api_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("arcadia_signal_api_pipeline").dataset() sessions_df = data.tariffs.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM arcadia_signal_api_data.tariffs LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("arcadia_signal_api_pipeline").dataset() data.tariffs.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 Arcadia Signal API 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 Arcadia Signal API?
Request dlt skills, commands, AGENT.md files, and AI-native context.