Anchor Browser Python API Docs | dltHub

Build a Anchor Browser-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

To create a new profile in Anchor Browser, use the API endpoint to store cookies, local storage, and cache from a browser session. The API documentation is available at https://docs.anchorbrowser.io/api-reference/profiles/create-profile. Profiles are essential for authenticated sessions. The REST API base URL is https://api.anchorbrowser.io and all requests require an API key passed in the anchor-api-key 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 pip install "dlt[workspace]" and start loading Anchor Browser data in under 10 minutes.


What data can I load from Anchor Browser?

Here are some of the endpoints you can load from Anchor Browser:

ResourceEndpointMethodData selectorDescription
profiles/v1/profilesGETdata.itemsList all stored profiles (returns data.count and data.items array of profiles)
profile/v1/profiles/{name}GETdataRetrieve a single profile by name (profile object inside data)
browser_sessions/v1/browser-sessionsGETdata.itemsList browser sessions
browser_session_downloads/v1/browser-sessions/{id}/downloadsGETdata.itemsGet downloads metadata for a session
integrations/v1/integrationsGETdata.itemsList integrations

How do I authenticate with the Anchor Browser API?

Anchor Browser uses an API key sent via the HTTP header "anchor-api-key" on every request. Include the header anchor-api-key: in all requests.

1. Get your credentials

  1. Sign in to the Anchor Browser dashboard (app.anchorbrowser.io). 2) Navigate to the Integrations or API Keys section. 3) Create a new API key or copy an existing one. 4) Store the key securely and use it as the value for the anchor-api-key header.

2. Add them to .dlt/secrets.toml

[sources.anchor_browser_source] api_key = "your_anchor_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 Anchor Browser 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 anchor_browser_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline anchor_browser_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset anchor_browser_data The duckdb destination used duckdb:/anchor_browser.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline anchor_browser_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 profiles and profile from the Anchor Browser 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 anchor_browser_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.anchorbrowser.io", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "profiles", "endpoint": {"path": "v1/profiles", "data_selector": "data.items"}}, {"name": "profile", "endpoint": {"path": "v1/profiles/{name}", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="anchor_browser_pipeline", destination="duckdb", dataset_name="anchor_browser_data", ) load_info = pipeline.run(anchor_browser_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("anchor_browser_pipeline").dataset() sessions_df = data.profiles.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM anchor_browser_data.profiles LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("anchor_browser_pipeline").dataset() data.profiles.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 Anchor Browser data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 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 Anchor Browser?

Request dlt skills, commands, AGENT.md files, and AI-native context.