# US Tide Predictions — High & Low Tides by Station (`plaindata/us-tide-predictions`) Actor

Get US tide predictions — high/low tide times and heights or hourly levels — for any coastal station or whole states, up to a year ahead. Data: NOAA CO-OPS API (public domain), not affiliated.

- **URL**: https://apify.com/plaindata/us-tide-predictions.md
- **Developed by:** [plaindata](https://apify.com/plaindata) (community)
- **Categories:** Travel, Developer tools, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 result returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## US Tide Predictions — High & Low Tides by Station

Get **US tide predictions** — high and low tide times and heights, or hourly / 6-minute water levels — for any of 3,000+ coastal prediction stations, or every station in a state, up to a year ahead. Uses the official **NOAA CO-OPS API**. Great for fishing and boating apps, marine logistics, coastal construction scheduling, travel sites and AI agents.

### Input examples

```json
{ "stationIds": ["9414290", "8518750"], "days": 7, "interval": "hilo" }
{ "states": ["ME"], "days": 3, "interval": "hilo", "units": "metric" }
{ "stationIds": ["8443970"], "beginDate": "2027-01-01", "days": 31, "interval": "h", "timeZone": "gmt" }
```

Station IDs are listed on tidesandcurrents.noaa.gov (e.g. 9414290 San Francisco, 8518750 The Battery NY, 8443970 Boston).

### Output (one row per prediction)

| Field | Meaning |
|---|---|
| stationId, stationName, state, latitude, longitude | Station |
| time | Local or GMT time (see timeZone) |
| type | high / low (high-low mode only) |
| height, units, datum | Predicted water level, feet or metres, relative to datum |
| timeZone, interval | Settings used |
| noaaUrl | Station page |
| source | Data source statement |

### Data source & licence

NOAA National Ocean Service, CO-OPS data API. NOAA's disclaimer: "The information on government servers are in the public domain, unless specifically annotated otherwise, and may be used freely by the public." Values are passed through unmodified and are not presented as official government material. Source: NOAA/NOS/CO-OPS.

### Notes

Predictions are astronomical tides and do not include weather effects; not for navigation. Requests are spaced (about one per second) and identified with an application name, as CO-OPS asks. Not affiliated with or endorsed by NOAA.

# Actor input Schema

## `stationIds` (type: `array`):

7-digit tide station IDs, e.g. 9414290 (San Francisco), 8518750 (The Battery, NY), 8443970 (Boston).

## `states` (type: `array`):

Two-letter state codes to include every prediction station in that state, e.g. ME, FL. Up to 50 stations per run.

## `beginDate` (type: `string`):

YYYY-MM-DD. Default: today (UTC).

## `days` (type: `integer`):

Up to 365 (31 for 6-minute interval).

## `interval` (type: `string`):

High/low tides only, hourly, or every 6 minutes.

## `units` (type: `string`):

Feet or metres.

## `datum` (type: `string`):

Vertical reference, usually MLLW.

## `timeZone` (type: `string`):

Local standard/daylight time or GMT.

## `maxItems` (type: `integer`):

Up to 100,000 per run.

## Actor input object example

```json
{
  "stationIds": [
    "9414290",
    "8518750"
  ],
  "days": 7,
  "interval": "hilo",
  "units": "english",
  "datum": "MLLW",
  "timeZone": "lst_ldt",
  "maxItems": 1000
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "stationIds": [
        "9414290",
        "8518750"
    ],
    "days": 7,
    "maxItems": 1000
};

// Run the Actor and wait for it to finish
const run = await client.actor("plaindata/us-tide-predictions").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "stationIds": [
        "9414290",
        "8518750",
    ],
    "days": 7,
    "maxItems": 1000,
}

# Run the Actor and wait for it to finish
run = client.actor("plaindata/us-tide-predictions").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "stationIds": [
    "9414290",
    "8518750"
  ],
  "days": 7,
  "maxItems": 1000
}' |
apify call plaindata/us-tide-predictions --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,plaindata/us-tide-predictions"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/jiZmBVZ01aX3nLoAB/builds/iDbaDPhmDSi4dZMMG/openapi.json