Install Jentic One Beta

Connect the NOAA ERDDAP API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NOAA ERDDAP 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnoaa.gov%2Fcoastwatch" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnoaa.gov%2Fcoastwatch" | 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 ERDDAP API.

Run a full-text search across NOAA's ERDDAP dataset collection

Run an advanced search filtered by dataset attributes

List dataset metadata and variables for a given dataset id

Query tabular datasets and return the selected rows as JSON or CSV

Query gridded datasets and return a subset as JSON

GET STARTED

Start building with NOAA ERDDAP API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use NOAA ERDDAP API for, with concrete tasks.

★ AI Environmental Data Agent

An AI agent connected through Jentic answers questions about ocean and atmospheric conditions by searching ERDDAP for a matching dataset, reading its metadata, and querying the values, so a user asking for recent buoy temperatures gets real numbers without the developer learning ERDDAP's query grammar. The agent finds the dataset id first, then pulls the rows it needs as JSON.

Search ERDDAP for a sea surface temperature dataset, read its variables, and query the most recent rows for a bounding box as JSON

Research Data Extraction

A research or data-science pipeline pulls environmental time series by resolving a dataset id, then requesting a tabular query filtered to the variables, station, and time range it needs. CSV output drops straight into analysis tools, and advanced search narrows the catalogue to the datasets that carry the required variables.

Query a tabular dataset for a single station over a date range and return the result as CSV

Gridded Data for Mapping

A mapping or modelling tool pulls a spatial subset of a gridded dataset such as chlorophyll or sea surface temperature by requesting a griddap query bounded to a latitude, longitude, and time window. The JSON response feeds a heatmap or model input without the tool downloading the entire grid.

Request a griddap subset of a sea surface temperature grid for a latitude and longitude box and return it as JSON

Key Endpoints

10 endpoints — the noaa erddap api provides restful access to oceanographic, atmospheric, and environmental datasets served by noaa coastwatch.

METHOD

PATH

DESCRIPTION

GET

/search/index.json

Full-text search for datasets

GET

/info/{datasetId}/index.json

Get metadata for a specific dataset

GET

/tabledap/{datasetId}.json

Query a tabular dataset and return JSON

GET

/tabledap/{datasetId}.csv

Query a tabular dataset and return CSV

GET

/griddap/{datasetId}.json

Query a gridded dataset and return JSON

GET

/categorize/index.json

List dataset categorization attributes

GET

/convert/time.json

Convert between time string and numeric formats

GET

/search/index.json

Full-text search for datasets

GET

/info/{datasetId}/index.json

Get metadata for a specific dataset

GET

/tabledap/{datasetId}.json

Query a tabular dataset and return JSON

GET

/tabledap/{datasetId}.csv

Query a tabular dataset and return CSV

GET

/griddap/{datasetId}.json

Query a gridded dataset and return JSON

GET

/categorize/index.json

List dataset categorization attributes

GET

/convert/time.json

Convert between time string and numeric formats

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

NOAA ERDDAP needs no API key, but wiring it by hand means learning its tabledap and griddap query grammar, dataset ids, and JSON or CSV output modes. Through Jentic you install once, import it from the API Directory, and your agent calls it.

Permission scoping

Every operation is a read, so a rule can keep your agent to just the search and dataset-query operations. You choose which operations it may call, and there is no write path to NOAA's data.

Credential isolation

ERDDAP is public, so there is no key to manage. When you add APIs that do require credentials, your own Jentic One instance keeps them encrypted and injects them at execution time, never placing them in the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find a sea temperature dataset' or 'query a tabular dataset', and Jentic returns the matching ERDDAP operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using NOAA ERDDAP API through Jentic.

What authentication does the NOAA ERDDAP API use?

The NOAA ERDDAP API is public: its OpenAPI spec declares no authentication, so search and dataset-query requests need no API key. Through Jentic it is still called from your own self-hosted instance, with every call logged.

Can I query tabular datasets with the NOAA ERDDAP API?

Yes. The tabledap operations take a dataset id and return the selected rows and variables as JSON or CSV, while griddap does the same for gridded data as JSON. You locate the dataset id first through full-text or advanced search.

What are the rate limits for the NOAA ERDDAP API?

The OpenAPI spec does not define rate limits for the NOAA ERDDAP API. NOAA asks users to query responsibly and documents guidance at https://coastwatch.pfeg.noaa.gov/erddap, so check there before scheduling heavy pulls.

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

Yes. Write a rule that allows only the search and dataset-query operations, so the agent reads environmental data and nothing else. ERDDAP exposes no write operations, so there is nothing to change, and every call the agent makes is logged.

How do I query a NOAA dataset through Jentic?

Search by intent in Jentic with a query like 'query an ERDDAP dataset', add the NOAA ERDDAP API from the Jentic API Directory, and your agent runs the search to find a dataset id then the tabledap or griddap query to pull the data. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Noaa Gov NOAA ERDDAP API

Browse all Noaa Gov APIs

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsData Pipelinesnone10 EndpointsREST

For Agents

Search NOAA's ERDDAP dataset collection, inspect dataset metadata, and query tabular or gridded environmental data as JSON or CSV. Public access with no API key.

Use for: Search NOAA ERDDAP for sea surface temperature datasets, Get the metadata and variables for a specific dataset, Query a tabular dataset and return CSV, Retrieve a subset of a gridded dataset as JSON

Not supported: Does not handle data visualization, forecasting, or dataset hosting. Use for searching and querying NOAA ERDDAP environmental datasets only.

The NOAA ERDDAP API provides RESTful access to oceanographic, atmospheric, and environmental datasets served by NOAA CoastWatch. It runs full-text and advanced dataset searches, lists dataset metadata and variables, and queries tabular (tabledap) and gridded (griddap) data with JSON or CSV output. A time-conversion endpoint and category browsing round out a service built for pulling environmental data into analysis pipelines.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

28%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

36%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

60%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the NOAA ERDDAP API to your agent

Capabilities

Start building with NOAA ERDDAP API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Noaa Gov NOAA ERDDAP API

Jentic AI Readiness Score

NOAA ERDDAP API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness