No logo available for Sixfold AI to DuckDB connector icon

Load Sixfold AI data to DuckDB

Build a Sixfold AI to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the Sixfold AI API base URL, auth, endpoints, and incremental loading.

SourceSixfold AISixfold AI API DocumentationDestinationDuckDBIn-process analytical database. The default local destination for dlt pipelines.

Sixfold AI is an insurance underwriting platform that provides an API for automating data gathering, ingestion, and risk analysis recommendations. Everything needed to build a working Sixfold 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 Sixfold AI to DuckDB pipeline

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

Prompt
Run uvx dlthub-init@latest to build a pipeline from Sixfold 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 Sixfold 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.


Sixfold AI API at a glance

Base URLhttps://api.sixfold.dev
Example endpointGET 2024-05/commercial/cases
Records found atdata
Authenticationall requests require a custom header containing the API key — sent in the SIXFOLD-API-KEY header
PaginationPage-number via none, next cursor at none, page size via page_size (default 20, max 100). Pagination uses numeric page and page_size query parameters (no cursor/next-page-token). Example: ?page=1&page_size=20.
Record idid
API referencehttps://api.sixfold.dev/

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


How do I authenticate with the Sixfold AI API?

All requests require the Sixfold API key to be included in the custom header 'SIXFOLD-API-KEY'.

1. Get your credentials

  1. Log in to the Sixfold AI portal at https://www.sixfold.ai.\n2. Navigate to Account Settings > API Keys.\n3. Click Create New API Key, provide a name, and confirm.\n4. Copy the generated API key immediately, as it is only displayed once. Store it securely.

2. Add them to .dlt/secrets.toml

[sources.sixfold_ai_source] api_key = "your_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 Sixfold AI data can I load into DuckDB?

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

ResourceEndpointMethodData selectorDescription
commercial_cases2024-05/commercial/casesGETdataRetrieve a list of commercial insurance cases
commercial_case2024-05/commercial/cases/{case_id}GETdataRetrieve details of a specific commercial case
commercial_case_status2024-05/commercial/cases/{case_id}/statusGETdataGet the current processing status of a case
commercial_case_pdf2024-05/commercial/cases/{case_id}.pdfGETDownload the PDF version of a commercial case report
commercial_case_docx2024-05/commercial/cases/{case_id}/narrative.docxGETDownload the narrative DOCX for a commercial case

How do I load only new Sixfold AI records?

The Sixfold 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.

{"name": "commercial_cases", "endpoint": { "path": "2024-05/commercial/cases", # 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 Sixfold AI pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading commercial/cases and commercial/cases/{case_id} from the Sixfold AI API into DuckDB:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def sixfold_ai_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.sixfold.dev", "auth": {"type": "api_key", "api_key": api_key, "name": "SIXFOLD-API-KEY", "location": "header"}, }, "resources": [ {"name": "commercial_cases", "endpoint": {"path": "2024-05/commercial/cases", "data_selector": "data"}}, {"name": "commercial_case", "endpoint": {"path": "2024-05/commercial/cases/{case_id}", "data_selector": "data"}} ], } yield from rest_api_resources(config) def load_sixfold_ai_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="sixfold_ai_pipeline", destination="duckdb", dataset_name="sixfold_ai_data", ) load_info = pipeline.run(sixfold_ai_source()) print(load_info) if __name__ == "__main__": load_sixfold_ai_to_duckdb()

Run it with python sixfold_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 Sixfold 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):

import dlt data = dlt.pipeline("sixfold_ai_pipeline").dataset() df = data.commercial_cases.df() print(df.head())

SQL:

SELECT * FROM sixfold_ai_data.commercial_cases LIMIT 10;

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


How do I deploy the Sixfold 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 Sixfold 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 Sixfold AI data to?

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

DestinationExample value
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

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

Was this page helpful?

Community Hub

Need more dlt context for Sixfold AI to DuckDB?

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