Load NASA data to DuckDB

NASA Open APIs provides a collection of RESTful APIs for accessing space and Earth science data. Everything needed to build a working NASA → 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 NASA 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 NASA 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 NASA 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.

---

NASA API at a glance

These values come from the NASA API documentation. Check them against the vendor's current reference before relying on them in production.

---

How do I authenticate with the NASA API?

The API uses a query parameter named 'api_key' for authentication. Include this key in your request URL as 'api_key=YOUR_API_KEY'.

1. Get your credentials

To obtain an API key for the NASA Open APIs, navigate to the official API portal at https://api.nasa.gov/. Scroll down to the "Generate API Key" section, fill out the required form with your name and email address, and submit it. Your API key will be displayed on the page and typically sent to you via email. For initial testing and exploration, you may use the DEMO_KEY provided in documentation, though it carries significantly lower rate limits than a personalized key.

2. Add them to .dlt/secrets.toml

Copy
[sources.nasa_source]
nasa_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 NASA data can I load into DuckDB?

These are the NASA endpoints dlt can load into DuckDB:

---

How do I load only new NASA records?

NASA exposes updated_at on executions, 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": "cumulus_executions", "endpoint": {
    "path": "executions",
    "data_selector": "results",
    "incremental": {"cursor_path": "updated_at", "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 NASA pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /planetary/apod and /neo/rest/v1/feed from the NASA API into DuckDB:

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

@dlt.source
def nasa_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.nasa.gov",
            "auth": {"type": "bearer", "token": api_key},
        },
        "resources": [
            {"name": "cumulus_executions", "endpoint": {"path": "executions", "data_selector": "results"}},
            {"name": "pds_products", "endpoint": {"path": "search/1/products"}}
        ],
    }
    yield from rest_api_resources(config)


def load_nasa_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="nasa_pipeline",
        destination="duckdb",
        dataset_name="nasa_data",
    )
    load_info = pipeline.run(nasa_source())
    print(load_info)


if __name__ == "__main__":
    load_nasa_to_duckdb()

Run it with python nasa_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 NASA 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("nasa_pipeline").dataset()
df = data.executions.df()
print(df.head())

SQL:

Copy
SELECT * FROM nasa_data.executions LIMIT 10;

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

---

How do I deploy the NASA 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 NASA 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 NASA 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