# Chokepoint & Maritime Risk Monitor (Hormuz, Suez, Red Sea) (`weirworks/chokepoint-maritime-monitor`) Actor

Daily ship transits through 28 global chokepoints (Strait of Hormuz, Bab el-Mandeb, Suez, Panama, Bosporus, Malacca...) from IMF PortWatch with disruption flags versus last year, plus active NGA navigational warnings tagged by region.

- **URL**: https://apify.com/weirworks/chokepoint-maritime-monitor.md
- **Developed by:** [Weirworks](https://apify.com/weirworks) (community)
- **Categories:** News, Travel
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 chokepoints

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

## Chokepoint & Maritime Risk Monitor (Hormuz, Suez, Red Sea, Black Sea)

Daily **ship transit counts for 28 of the world's maritime chokepoints**, from the Strait of Hormuz and Bab el-Mandeb to Suez, Panama, the Bosporus, Kerch, Malacca and the Taiwan Strait. Each chokepoint gets **year-over-year comparisons and a disruption flag**. Active **navigational warnings** (military exercises, firing areas, GNSS jamming, hazardous operations) are included and tagged by region.

Built for commodity and freight traders, shipping and insurance risk teams, supply-chain planners, journalists covering the Iran and Red Sea crises or the Russia–Ukraine war, and AI agents that need maritime context.

### What you get

**One row per chokepoint:**

- Latest daily transits, and tanker transits.
- 7-day and 30-day average transits, overall and for tankers, compared with the same window one year earlier.
- `disruption` flag: `severe` (≤ −50% vs last year), `elevated` (≤ −25%) or `normal`.
- 7-day transits by ship type (tanker, container, dry bulk, general cargo, ro-ro) and average carried capacity in tons.
- Optional daily history (up to 400 days).

**One row per active navigational warning:**

- NAVAREA and subregion, message number and issue date.
- Full text.
- Region tags: Persian Gulf/Hormuz, Red Sea/Gulf of Aden, Black Sea/Ukraine, Eastern Mediterranean, Taiwan/South China Sea, Baltic.
- Risk keywords: missile, firing, drone, GNSS jamming, mine, piracy...

### Example output (October 2026)

| Chokepoint | 7-day avg transits | Same week 2025 | Change | Flag |
|---|---|---|---|---|
| Strait of Hormuz | 3.1 | 86.4 | −96% | severe |
| Kerch Strait | 0 | 18.4 | −100% | severe |
| Bosporus Strait | 49.6 | 91.4 | −46% | elevated |
| Bab el-Mandeb | 27.1 | 33.3 | −19% | normal |
| Suez Canal | 40.0 | 42.7 | −6% | normal |

### Input

```json
{
  "include": ["chokepoints", "warnings"],
  "chokepoints": ["Hormuz", "Bab el-Mandeb", "Suez", "Bosporus"],
  "onlyDisrupted": false,
  "dailyHistoryDays": 30,
  "warningRegions": ["Black Sea / Ukraine"],
  "securityWarningsOnly": true
}
```

### Data sources and caveats

- **Transits:** IMF PortWatch daily chokepoint data, derived from AIS ship tracking. It usually lags 4–7 days. Ships that switch off AIS ("dark" transits, common in conflict zones and shadow-fleet trades) aren't counted, so very low numbers mean traffic *visible on AIS* collapsed.
- **Warnings:** U.S. National Geospatial-Intelligence Agency (NGA) Maritime Safety Information broadcast warnings. Coverage is strongest for NAVAREA IV and XII and NGA's worldwide hydrographic warnings. Some regional authorities (e.g. UKMTO) aren't included.

### Pricing

- **$0.01 per chokepoint row.** A full 28-chokepoint snapshot costs $0.28.
- **$0.002 per warning.**

No start fee.

Questions: open an issue or email **hello@weirworks.com**.

*Independent tool by weirworks. Not affiliated with the IMF or NGA. Source: IMF PortWatch (portwatch.imf.org); NGA MSI.*

# Actor input Schema

## `include` (type: `array`):

Which datasets to output.

## `chokepoints` (type: `array`):

Names to include (partial match), e.g. <code>Hormuz</code>, <code>Bab el-Mandeb</code>, <code>Suez</code>, <code>Bosporus</code>, <code>Kerch</code>. Leave empty for all 28.

## `onlyDisrupted` (type: `boolean`):

Only chokepoints whose 7-day transits are 25%+ below the same week last year.

## `dailyHistoryDays` (type: `integer`):

Attach this many days of daily transit counts to each chokepoint row.

## `warningRegions` (type: `array`):

Only warnings mentioning these regions. Leave empty for all active warnings.

## `warningKeywords` (type: `array`):

Only warnings containing any of these words, e.g. <code>MISSILE</code>, <code>GNSS</code>.

## `securityWarningsOnly` (type: `boolean`):

Only warnings mentioning military activity, firing, missiles, drones, mines, GPS/GNSS jamming, piracy or attacks.

## `proxyConfiguration` (type: `object`):

Not needed: public sources.

## Actor input object example

```json
{
  "include": [
    "chokepoints",
    "warnings"
  ],
  "onlyDisrupted": false,
  "dailyHistoryDays": 0,
  "securityWarningsOnly": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

The dataset rows.

# 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 = {
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("weirworks/chokepoint-maritime-monitor").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 = { "proxyConfiguration": { "useApifyProxy": False } }

# Run the Actor and wait for it to finish
run = client.actor("weirworks/chokepoint-maritime-monitor").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 '{
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call weirworks/chokepoint-maritime-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,weirworks/chokepoint-maritime-monitor"
        }
    }
}
```

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/ilCdZbLJR68yInODT/builds/8RDbodfMLSDTSqb2I/openapi.json