AgentQL Python API Docs | dltHub
Build a AgentQL-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
AgentQL is a web scraping and data extraction API that queries web pages and documents (HTML, PDFs, images) and returns structured JSON data. The REST API base URL is https://api.agentql.com/v1 and all requests require an X-API-Key header for 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 pip install "dlt[workspace]" and start loading AgentQL data in under 10 minutes.
What data can I load from AgentQL?
Here are some of the endpoints you can load from AgentQL:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| query_data | /query-data | POST | data | Query structured data from a webpage or raw HTML using an AgentQL query or prompt. |
| query_document | /query-document | POST | data | Query PDFs and image files; returns query results per page/image in the data object. |
| tetra_sessions | /tetra/sessions | POST | (response top-level) | Create remote browser session; response contains session_id, cdp_url, base_url. |
| sessions_stream | {session_base}/stream/0 | GET | (stream endpoint) | Streaming/viewing endpoint for remote browser session (constructed from base_url in session creation). |
| query_examples_docs | /docs (interactive) | GET | (varies) | Interactive API docs available at https://api.agentql.com/docs (referenced from docs). |
| query_status | /v1/tetra/sessions/{session_id} | GET | (response top-level) | Retrieve details for a browser session (response contains session fields such as session_id, base_url) — use session_id returned from POST. |
How do I authenticate with the AgentQL API?
AgentQL uses an API key provided in the X-API-Key HTTP header on every request. Include Content-Type: application/json for JSON requests and multipart/form-data for file uploads.
1. Get your credentials
- Go to the Dev Portal at https://dev.agentql.com/. 2) Sign in or create an account. 3) Navigate to API Keys / Credentials. 4) Create a new API key and copy the key. 5) Store the key securely; use it in the X-API-Key header.
2. Add them to .dlt/secrets.toml
[sources.agentql_scraping_data_api_source] api_key = "your_agentql_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 AgentQL 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 agentql_scraping_data_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline agentql_scraping_data_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset agentql_scraping_data_api_data The duckdb destination used duckdb:/agentql_scraping_data_api.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline agentql_scraping_data_api_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 query_data and query_document from the AgentQL 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 agentql_scraping_data_api_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.agentql.com/v1", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "query_data", "endpoint": {"path": "query-data", "data_selector": "data"}}, {"name": "query_document", "endpoint": {"path": "query-document", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="agentql_scraping_data_api_pipeline", destination="duckdb", dataset_name="agentql_scraping_data_api_data", ) load_info = pipeline.run(agentql_scraping_data_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("agentql_scraping_data_api_pipeline").dataset() sessions_df = data.query_data.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM agentql_scraping_data_api_data.query_data LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("agentql_scraping_data_api_pipeline").dataset() data.query_data.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 AgentQL 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
Authentication failures
If you receive 401/403 responses, ensure your X-API-Key header is set to a valid API key. Generate or rotate keys at https://dev.agentql.com/ and update the X-API-Key header.
Rate limits and request errors
The docs reference per-call consumption for document pages (1 API call per image or per PDF page). If you receive 429 Too Many Requests, back off and retry with exponential backoff. Monitor request volume when querying multi-page PDFs.
Pagination and large responses
AgentQL returns extracted data in the data object matching your query shape. For very large responses or multi-page documents, consider splitting requests (per-page document queries) or using faster extraction mode (params.mode = "fast") to reduce runtime/cost.
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 AgentQL?
Request dlt skills, commands, AGENT.md files, and AI-native context.