CrewAI Python API Docs | dltHub

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

Last updated:

CrewAI AMP API is a platform for programmatically interacting with deployed CrewAI crews to manage execution and status monitoring. The REST API base URL is https://{your-crew-name}.crewai.com and all requests require a Bearer token.

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 CrewAI data in under 10 minutes.


What data can I load from CrewAI?

Here are some of the endpoints you can load from CrewAI:

ResourceEndpointMethodData selectorDescription
inputs/inputsGETDiscover required input parameters for the crew
kickoff/kickoffPOSTLaunch a new crew execution
execution_status/{kickoff_id}/statusGETPoll status and retrieve results of an execution
resume_execution/resumePOSTResume a crew execution with human feedback

How do I authenticate with the CrewAI API?

All requests to the CrewAI AMP API require a Bearer token provided in the Authorization header. Use the pattern 'Authorization: Bearer ', where the token is retrieved from the Status tab of your crew's detail page in the CrewAI AMP dashboard.

1. Get your credentials

Log in to the CrewAI AMP dashboard. Navigate to the detail page of your specific deployed crew. Select the Status tab to view and copy your Bearer Token (or User Bearer Token, depending on your required scope).

2. Add them to .dlt/secrets.toml

[sources.crewai_source] api_key = "your_bearer_token_from_dashboard" crew_url = "https://your-crew-name.crewai.com"

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 CrewAI 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 crewai_pipeline.py

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

Pipeline crewai_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset crewai_data The duckdb destination used duckdb:/crewai.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 /inputs and /kickoff from the CrewAI 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 crewai_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{your-crew-name}.crewai.com", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "inputs", "endpoint": {"path": "inputs"}}, {"name": "kickoff", "endpoint": {"path": "kickoff"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="crewai_pipeline", destination="duckdb", dataset_name="crewai_data", ) load_info = pipeline.run(crewai_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("crewai_pipeline").dataset() sessions_df = data.execution_status.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM crewai_data.execution_status LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("crewai_pipeline").dataset() data.execution_status.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 CrewAI 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 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 CrewAI?

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