Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
NOAA CO-OPS website screenshot

NOAA CO-OPS

NOAA Center for Operational Oceanographic Products and Services (CO-OPS) provides REST APIs for tides and currents predictions, observed water levels, meteorological data (wind, barometric pressure, air and water temperature), and oceanographic products. The APIs serve real-time and historical data from NOAA observation stations across the United States coastline and Great Lakes.

agent ready

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles NOAA CO-OPS the way a machine reads it — 23 machine-readable artifacts across 13 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — NOAA CO-OPS scores 43.1/100 (thin), with a separate agent-readiness read of 45/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 43.1/100 · thin
Contract Quality 13.2 / 25
Developer Ergonomics 3.5 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 2.1 / 13
Governance 10.4 / 12
Discoverability 10.0 / 10
Regulatory · Government & Public Sector 6.2 / 15
Agent readiness — 45/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile NOAA CO-OPS

Each block below is one kind of artifact we hold for NOAA CO-OPS. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 13

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

NOAA CO-OPS Benchmarks API

The Benchmarks API from NOAA CO-OPS — 1 operation(s) for benchmarks.

NOAA CO-OPS Datagetter API

The Datagetter API from NOAA CO-OPS — 1 operation(s) for datagetter.

NOAA CO-OPS Extremewaterlevels API

The Extremewaterlevels API from NOAA CO-OPS — 1 operation(s) for extremewaterlevels.

NOAA CO-OPS Htf Annual API

The Htf Annual API from NOAA CO-OPS — 1 operation(s) for htf annual.

NOAA CO-OPS Htf Monthly API

The Htf Monthly API from NOAA CO-OPS — 1 operation(s) for htf monthly.

NOAA CO-OPS Htf Projection Decadal API

The Htf Projection Decadal API from NOAA CO-OPS — 1 operation(s) for htf projection decadal.

NOAA CO-OPS Peakwaterlevels API

The Peakwaterlevels API from NOAA CO-OPS — 1 operation(s) for peakwaterlevels.

NOAA CO-OPS Ports.json API

The Ports.json API from NOAA CO-OPS — 1 operation(s) for ports.json.

NOAA CO-OPS Sealvltrends API

The Sealvltrends API from NOAA CO-OPS — 1 operation(s) for sealvltrends.

NOAA CO-OPS Slr Projections API

The Slr Projections API from NOAA CO-OPS — 1 operation(s) for slr projections.

NOAA CO-OPS Stations API

NOAA CO-OPS station metadata, sensors, datums, and configuration

NOAA CO-OPS Stations.json API

The Stations.json API from NOAA CO-OPS — 1 operation(s) for stations.json.

NOAA CO-OPS Toptenwaterlevels API

The Toptenwaterlevels API from NOAA CO-OPS — 1 operation(s) for toptenwaterlevels.

Scroll within the panel for all 13 ·

Spectral Rules 1

Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.

NOAA CO-OPS API Rules

5 rules · 4 warnings

SPECTRAL

JSON Schema 2

Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.

Standalone JSON Schema definitions for this provider's data models.

CO-OPS Data Point

9 properties

JSON SCHEMA

CO-OPS Station

14 properties

JSON SCHEMA

Examples 5

Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.

Example request and response payloads for these APIs.

Sea Level Trend Response

3 fields

EXAMPLE

Station Metadata Response

3 fields

EXAMPLE

Tide Predictions Request

4 fields

EXAMPLE

Water Level Request

4 fields

EXAMPLE

Water Level Response

3 fields

EXAMPLE

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Noaa Co Ops Domain Security

TLSv1.2 · HSTS · DNSSEC · DMARC

SECURITY

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Noaa Co Ops Agentic Access

14 operations

14 operations · 0 acting

AGENTIC

Resources

Every other property we hold for NOAA CO-OPS — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 1

Portal, sign-up, and the first successful call

Documentation 3

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Access & Security 1

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

← All providers · Data indexed from github.com/api-evangelist/noaa-co-ops · machine-readable index on apis.io