canonical: https://jentic.com/apis/nsidc.org/nsidc-web-service-documentation-index

# NSIDC Web Service Documentation Index

The NSIDC Web Service Documentation Index is the search interface to the National Snow and Ice Data Center's data and metadata collection. It exposes an OpenSearch endpoint that returns matching datasets for a query, a facets endpoint that summarises those results by category, and a suggestions endpoint that completes partial search terms. A companion endpoint describes the search interface itself. Developers use it to build NSIDC dataset discovery, such as the Arctic Data Explorer, into their own applications. It is a read-only, public search API.

## For AI agents

Search the National Snow and Ice Data Center dataset collection with OpenSearch, read facet summaries of the results, and get search-term suggestions. Read-only and requires no authentication.

## Scope

Does not download dataset files, run analysis, or return weather observations. Use for searching the NSIDC dataset collection and reading facets and search suggestions only.

## Capabilities

- Search NSIDC datasets by term, date range, and spatial extent using OpenSearch
- Read facet summaries that group search results by category
- Get suggested search terms for a partial query
- Read a description of the NSIDC search interface and its parameters
- Filter and sort dataset results with OpenSearch and its Geo and SRU extensions

## Use cases

### Add NSIDC dataset discovery to an app

A research or geospatial application can let users search the National Snow and Ice Data Center collection directly. The app sends a query with optional date and spatial filters to the OpenSearch endpoint and displays the matching datasets. Through Jentic an agent discovers the search operation by intent and calls it with the search terms and filters.

Example prompt: Search NSIDC datasets for the term 'sea ice concentration' and return the first ten matching datasets

### Guide search with facets and suggestions

To help a user narrow a broad query, an agent reads the facet summary for a search and offers the categories with the most results, then uses the suggestions endpoint to complete partial terms as the user types. This mirrors how the Arctic Data Explorer guides its own search box. The result is faster, more relevant dataset discovery.

Example prompt: Get the facet counts for a search on 'glacier' and return the suggested terms for the partial query 'gla'

### Filter datasets by time and place

An agent studying a region over a period can search the collection with a spatial extent and a start and end date, using the OpenSearch Geo and SRU extensions the endpoint supports. This returns only the datasets relevant to that area and window, so the agent avoids sifting the full collection. Results can be sorted by the available sort keys.

Example prompt: Search NSIDC datasets within a bounding box for a given start and end date and return the matches

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/OpenSearch` | Search the dataset collection using the OpenSearch 1.1 specification |
| GET | `/Facets` | Return facet counts corresponding to a search |
| GET | `/suggest` | Suggest search terms for a partial query |
| GET | `/OpenSearchDescription` | Describe the search interface and its parameters |

## Key resources

- **OpenSearch** — Search the dataset collection by term, date, and spatial extent
- **Facets** — Summarise search results by category
- **Suggest** — Suggest search terms for a partial query

## Why Jentic

- **Setup:** Wiring the NSIDC Web Service Documentation Index by hand is light because it needs no key, but you still write the HTTP client, assemble the OpenSearch query parameters and their Geo and SRU extensions, and parse the search, facet, and suggestion responses yourself. Through Jentic you install once, import the API from the API Directory, and your agent calls the search with no credential to provision.
- **Permission scoping:** The NSIDC Web Service Documentation Index is read-only and exposes only search, facet, suggestion, and description operations, so a rule can allow your agent to run searches and read facets and nothing more. There are no write or delete operations, and the API carries no credential that could reach beyond reading the public collection.
- **Credential handling:** The NSIDC Web Service Documentation Index is public and uses no credential, so there is nothing for Jentic to store or inject. The calls your agent makes carry no secret into its prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search datasets' or 'suggest search terms', and Jentic returns the matching NSIDC operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **NOAA API** — Broad US weather and climate data versus NSIDC's snow and ice dataset collection.
- **NCEI API** — Another environmental data archive whose collection overlaps NSIDC on climate records.
- **OpenWeatherMap API** — Live and forecast weather that can add current conditions to a dataset a user found via NSIDC.

## FAQ

### What authentication does the NSIDC Web Service Documentation Index use?

The NSIDC Web Service Documentation Index requires no authentication. Its OpenAPI spec declares no security scheme, so the search, facet, and suggestion endpoints are public and need no key or token. Because there is no credential, there is nothing to store, rotate, or expose when an agent calls it through Jentic.

### How do I search NSIDC datasets through this API?

Send a query to the OpenSearch endpoint with your search terms and optional date and spatial filters, and it returns the matching datasets following the OpenSearch 1.1 specification. An agent can pair this with the facet counts and the term suggestions to guide a user toward the right dataset.

### What do the facets and suggestions endpoints do?

The facets endpoint summarises a search's results by category so a user can narrow a broad query, and it takes the same parameters as the search endpoint. The suggestions endpoint completes partial search terms, the way the Arctic Data Explorer fills its search box as the user types.

### What are the rate limits for the NSIDC Web Service Documentation Index?

The OpenAPI spec does not declare rate limits for the NSIDC Web Service Documentation Index. It is a public research service, so apply conservative client-side throttling and caching and check the NSIDC documentation for current guidance.

### Can I limit what my agent is allowed to do with the NSIDC Web Service Documentation Index?

Yes. The NSIDC Web Service Documentation Index is read-only and exposes only search, facet, suggestion, and description operations, so an agent connected through Jentic can only read from the collection and cannot change any data. You choose which of these operations it may call, and every call it makes is logged.

### Is there an NSIDC API MCP server?

You don't need an MCP server to give your agent the NSIDC search API. Jentic connects it directly from the API Directory: import it and your agent calls the search, facet, and suggestion operations on demand, with no key to configure because the API is public.

### How do I search NSIDC datasets through Jentic?

Search Jentic for an intent like 'search datasets', which returns the NSIDC OpenSearch operation with its input schema so the agent supplies the search terms and filters and reads back the matching datasets, with no credential to configure because the API is public. To run it on your own infrastructure, install Jentic One from its GitHub repo.