Noaa Gov NOAA Climate Data Online (CDO) API

Name: NOAA Climate Data Online (CDO) API
Brand: NOAA Climate Data Online (CDO) API
Availability: InStock

✓ Official Vendor SpecData EnrichmentData TransformationapiKey13 EndpointsREST

For Agents

Install Jentic One Beta

Connect the NOAA Climate Data Online (CDO) API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NOAA Climate Data Online (CDO) API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with NOAA Climate Data Online (CDO) API.

List available climate datasets and inspect their metadata via /datasets and /datasets/{id}

Discover data categories and data types tied to a dataset through /datacategories and /datatypes

Look up monitoring stations and filter by dataset, location, or geographic extent via /stations

GET STARTED

Start building with NOAA Climate Data Online (CDO) API

Explore with Jentic

View OpenAPI Document

NOAA Climate Data Online (CDO) v2 exposes the National Centers for Environmental Information's archive of climate datasets, data categories, data types, locations, stations, and observed values. Agents can list and filter datasets like GHCND and GSOM, drill into the data types and categories each dataset publishes, look up monitoring stations and location codes, and pull observed values across date ranges and station sets via /data. The service is rate limited to 5 requests per second and 10,000 per day per token, and authentication is handled by an apiKey passed in the token header.

Use Cases

Patterns agents use NOAA Climate Data Online (CDO) API for, with concrete tasks.

★ Climate Trend Analysis

Researchers and ESG teams need consistent historical climate observations to compute trends across decades. The CDO API exposes datasets like GHCND and GSOM with /data endpoints that accept stationid, datatypeid, startdate, and enddate parameters, returning structured observation rows. By chaining /stations, /datatypes, and /data calls an agent can build a reproducible pipeline for temperature, precipitation, and snow trend analysis without scraping NCEI bulk archives.

Call /stations with locationid for a US state, then /data with datasetid=GHCND, the chosen stationid, datatypeid=TAVG, startdate=2014-01-01, enddate=2024-01-01

Insurance Risk Geolocation

Climate-aware underwriting workflows need historical observations tied to specific zip codes or counties. The /locations and /locationcategories endpoints resolve zip and FIPS codes to NOAA location ids, which can then be passed to /stations and /data. This produces a structured chain from a policy address to nearby station observations and historical extreme values for a risk score.

Resolve a US zip to a NOAA locationid via /locations?locationcategoryid=ZIP, list /stations for that location, and pull /data for the GSOM dataset over the last 30 years

Operational Weather Reporting

Operations and logistics teams need a daily report of station-level conditions across a fixed set of monitored sites. The /data endpoint accepts a list of stationids and a date range, returning observed values for each datatype requested. With /datasets and /datatypes the report can adapt automatically when NOAA adds or deprecates a data type without breaking the pipeline.

Call /data with datasetid=GHCND, a comma-separated list of stationids, datatypeid=PRCP, and yesterday's date as both startdate and enddate

AI Agent Climate Lookup

An LLM-powered agent answering questions like 'what was the average rainfall in San Francisco last summer?' can use Jentic to find and call the right CDO endpoint without hand-coding location and station resolution. Jentic search routes the question to /data with the correct dataset, datatype, and date range derived from intent, while the NOAA token stays in the vault.

Use Jentic to chain /locations, /stations, and /data to answer 'average daily precipitation for San Francisco in summer 2024'

Key Endpoints

13 endpoints — noaa climate data online (cdo) v2 exposes the national centers for environmental information's archive of climate datasets, data categories, data types, locations, stations, and observed values.

METHOD

PATH

DESCRIPTION

GET

/datasets

List available NOAA CDO datasets

GET

/datasets/{id}

Get metadata for a specific dataset

GET

/datatypes

List data types reported across datasets

GET

/locations

List location codes filtered by category

GET

/stations

List monitoring stations filtered by dataset or location

GET

/data

Retrieve observed values for a dataset, station, datatype, and date range

GET

/datacategories

List data categories grouping data types

GET

/datasets

List available NOAA CDO datasets

GET

/datasets/{id}

Get metadata for a specific dataset

GET

/datatypes

List data types reported across datasets

GET

/locations

List location codes filtered by category

GET

/stations

List monitoring stations filtered by dataset or location

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your CDO token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find weather stations for a location' or 'fetch historical climate data', and Jentic returns the matching CDO operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using NOAA Climate Data Online (CDO) API through Jentic.

What authentication does the NOAA CDO API use?

NOAA CDO uses an apiKey passed as the token header. Request a free token from the NOAA CDO portal. Through Jentic the token is stored in the vault and injected on every call without exposing it to the agent.

Can I get historical daily temperature data with the NOAA CDO API?

Yes. Call /data with datasetid=GHCND, the stationid for the location, datatypeid=TAVG (or TMIN/TMAX), and your startdate and enddate. The response returns daily observed values with units.

What are the rate limits for the NOAA CDO API?

NOAA enforces 5 requests per second and 10,000 requests per day per token, as declared in the spec's tokenAuth description. Jentic handles 429 responses with backoff and surfaces a clear error if the daily quota is exhausted.

How do I find weather stations near a specific zip code through Jentic?

Run pip install jentic, search Jentic for 'find noaa stations near a zip code', then chain /locations?locationcategoryid=ZIP to resolve the zip to a NOAA locationid and /stations?locationid=... to list nearby stations. Jentic injects the token automatically.

Is the NOAA CDO API free to use?

Yes. Tokens are issued free of charge from the NOAA CDO portal. Usage is bound by the 5 req/sec and 10,000 req/day quotas per token.

Which datasets are available through the NOAA CDO API?

Call /datasets to list the full catalog, including daily summaries (GHCND), monthly summaries (GSOM), normals (NORMAL_DLY, NORMAL_MLY), and other long-running NCEI products. /datasets/{id} returns coverage metadata.

Can I limit what my agent is allowed to do with the NOAA CDO API?

Yes. Because you run Jentic One yourself, your own rules decide which CDO operations the agent may call and which token it uses. Since CDO is read-only, you can scope by operation, allowing just the calls the agent needs, such as listing stations via /stations or fetching observations via /data, while leaving out /datacategories and /datatypes lookups. The NOAA token stays with your instance and is injected only for the operations you permit.