No logo available for Rentcast to DuckDB connector icon

Load Rentcast data to DuckDB

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

SourceRentcastDestinationDuckDBIn-process analytical database. The default local destination for dlt pipelines.

RentCast is a real estate data platform providing programmatic access to property records, market trends, valuations, and listing data. Everything needed to build a working Rentcast → 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 Rentcast 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 Rentcast 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 Rentcast 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.


Rentcast API at a glance

Base URLhttps://api.rentcast.io/v1
Example endpointGET properties
Authenticationall requests require an API key passed in the X-Api-Key header — sent in the X-Api-Key header
PaginationOffset-based via offset, page size via limit (default 50, max 500). The API uses offset-based pagination. 'offset' should be a multiple of the 'limit' parameter and is incremented on each request. The 'limit' parameter controls the number of results returned per page. A header 'X-Total-Count' can be retrieved if 'includeTotalCount' is set to true.
Incremental fieldoffset
Record idid
API referencehttps://developers.rentcast.io/reference/getting-started-guide

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


How do I authenticate with the Rentcast API?

Requests are authenticated by providing an API key in the X-Api-Key HTTP header.

1. Get your credentials

  1. Sign in to your RentCast account. 2. Navigate to the API dashboard (https://app.rentcast.io/app/api). 3. Locate the API keys section. 4. Click 'Create API Key' and follow the on-screen prompts to generate your unique key.

2. Add them to .dlt/secrets.toml

[sources.rentcast_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 Rentcast data can I load into DuckDB?

These are the Rentcast endpoints dlt can load into DuckDB:

ResourceEndpointMethodData selectorDescription
propertiespropertiesGETSearch property records by address or location filters.
property_recordspropertiesGET(Alternative path) Search for property records.
sale_listingslistings/saleGETSearch for active and inactive sale listings.
rental_listingslistings/rental/long-termGETSearch for long-term rental listings.
market_statisticsmarket/statisticsGETRetrieve aggregate market statistics for a zip code.

How do I load only new Rentcast records?

Rentcast exposes offset on properties, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

{"name": "properties", "endpoint": { "path": "properties", "incremental": {"cursor_path": "offset", "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 Rentcast pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /properties and /listings from the Rentcast API into DuckDB:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def rentcast_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.rentcast.io/v1", "auth": {"type": "api_key", "api_key": api_key, "name": "X-Api-Key", "location": "header"}, }, "resources": [ {"name": "properties", "endpoint": {"path": "properties"}}, {"name": "listings", "endpoint": {"path": "listings/sale"}} ], } yield from rest_api_resources(config) def load_rentcast_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="rentcast_pipeline", destination="duckdb", dataset_name="rentcast_data", ) load_info = pipeline.run(rentcast_source()) print(load_info) if __name__ == "__main__": load_rentcast_to_duckdb()

Run it with python rentcast_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 Rentcast 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("rentcast_pipeline").dataset() df = data.properties.df() print(df.head())

SQL:

SELECT * FROM rentcast_data.properties LIMIT 10;

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


How do I deploy the Rentcast 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 Rentcast 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 Rentcast 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 Rentcast to DuckDB?

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