Load NatureServe Explorer data to DuckDB

NatureServe Explorer is a public REST API providing access to comprehensive conservation data on species and ecosystems across the Americas. Everything needed to build a working NatureServe Explorer → 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 NatureServe Explorer to DuckDB pipeline

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

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from NatureServe Explorer 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 NatureServe Explorer 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.

---

NatureServe Explorer API at a glance

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

---

How do I authenticate with the NatureServe Explorer API?

The NatureServe Explorer REST API is publicly accessible and does not require authentication for its endpoints.

No credentials required. The NatureServe Explorer API is public, so there is nothing to obtain and nothing to add to .dlt/secrets.toml — the pipeline above runs as written.

---

What NatureServe Explorer data can I load into DuckDB?

These are the NatureServe Explorer endpoints dlt can load into DuckDB:

---

How do I load only new NatureServe Explorer records?

NatureServe Explorer exposes modifiedSince on api/v1/search/species, 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.

Copy
{"name": "species_search", "endpoint": {
    "path": "api/v1/search/species",
    "incremental": {"cursor_path": "modifiedSince", "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 NatureServe Explorer pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading speciesSearch and export from the NatureServe Explorer API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def natureserve_explorer_source():
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://explorer.natureserve.org/api/",
        },
        "resources": [
            {"name": "species_search", "endpoint": {"path": "api/v1/search/species"}},
            {"name": "ecosystem_search", "endpoint": {"path": "api/v1/search/ecosystem"}}
        ],
    }
    yield from rest_api_resources(config)


def load_natureserve_explorer_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="natureserve_explorer_pipeline",
        destination="duckdb",
        dataset_name="natureserve_explorer_data",
    )
    load_info = pipeline.run(natureserve_explorer_source())
    print(load_info)


if __name__ == "__main__":
    load_natureserve_explorer_to_duckdb()

Run it with python natureserve_explorer_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 NatureServe Explorer 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):

Copy
import dlt

data = dlt.pipeline("natureserve_explorer_pipeline").dataset()
df = data.species_search.df()
print(df.head())

SQL:

Copy
SELECT * FROM natureserve_explorer_data.species_search LIMIT 10;

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

---

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

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

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

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack