Load HARPA AI data to DuckDB

HARPA AI is a browser-orchestration and web-automation platform that allows users to run scraping, search, and AI actions on connected browser nodes via a Grid REST API. Everything needed to build a working HARPA AI → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your HARPA AI to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from HARPA AI to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the HARPA AI API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

HARPA AI API at a glance

These values come from the HARPA AI API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the HARPA AI API?

All requests require an 'Authorization' header with a Bearer token. The token is obtained from the HARPA AI Chrome extension's AUTOMATE tab.

1. Get your credentials

1. Install the HARPA AI Chrome extension from the official store (get.harpa.ai). 2. Open the HARPA AI extension in your browser. 3. Navigate to the AUTOMATE tab within the extension interface. 4. Locate the section for the API key, generate it if necessary, and copy the key. Note: For security reasons, the key is typically displayed only once, so store it securely.

2. Add them to .dlt/secrets.toml

Copy
[sources.harpa_ai_source]
api_key = "your_harpa_api_key_here"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What HARPA AI data can I load into DuckDB?

These are the HARPA AI endpoints dlt can load into DuckDB:

---

How do I load only new HARPA AI records?

The HARPA AI API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "scrape", "endpoint": {
    "path": "api/v1/grid",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated HARPA AI pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading api/v1/grid (the primary REST API endpoint for browser automation tasks) and the general base URL https://api.harpa.ai/api/v1/grid used for POST requests. from the HARPA AI API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def harpa_ai_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.harpa.ai/api/v1/grid",
            "auth": {"type": "bearer", "token": api_key},
        },
        "resources": [
            {"name": "scrape", "endpoint": {"path": "api/v1/grid"}},
            {"name": "serp", "endpoint": {"path": "api/v1/grid"}}
        ],
    }
    yield from rest_api_resources(config)


def load_harpa_ai_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="harpa_ai_pipeline",
        destination="duckdb",
        dataset_name="harpa_ai_data",
    )
    load_info = pipeline.run(harpa_ai_source())
    print(load_info)


if __name__ == "__main__":
    load_harpa_ai_to_duckdb()

Run it with python harpa_ai_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query HARPA AI data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("harpa_ai_pipeline").dataset()
df = data.grid.df()
print(df.head())

SQL:

Copy
SELECT * FROM harpa_ai_data.grid LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the HARPA AI to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw HARPA AI loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load HARPA AI data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack