# Global Maritime Intelligence & Strategic Chokepoints Monitor (`khnaami/global-maritime-intelligence-strategic-chokepoints-monitor`) Actor

Apify Actor for real-time global maritime traffic & supply chain intelligence: IMF/UN PortWatch satellite transits, AIS fleet telemetry, 2026 UK naval security attack ledgers (UKMTO & Ambrey London), IMO vessel registries, and marine bunker freight rerouting simulations.

- **URL**: https://apify.com/khnaami/global-maritime-intelligence-strategic-chokepoints-monitor.md
- **Developed by:** [khalid naami](https://apify.com/khnaami) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## 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

## 🚢 Global Maritime Traffic & Supply Chain Intelligence Actor

**Real-time IMF/UN PortWatch satellite transits, AIS fleet telemetry, 2026 UK naval security attack ledgers (UKMTO, Ambrey London, MAIB, Lloyd's JWC), global commercial IMO vessel registries, and marine bunker freight rerouting simulations.**

***

### 🌟 What Does This Actor Do?

This actor extracts, aggregates, and computes institutional-grade intelligence across the global maritime supply chain:

1. **Strategic Chokepoints Satellite Telemetry (PortWatch UN/IMF):**
   - Annual transit volumes, deadweight capacity, vessel breakdown (Container, Crude Tanker, Bulk Carrier, General Cargo, Ro-Ro).
   - Dominant cargo streams, geopolitical risk rankings, and Lloyd's Joint War Committee (JWC) listed area classifications.
2. **180-Day Daily Transit Time Series & Disruption Diagnostics:**
   - Day-over-day vessel counts and capacity series.
   - Algorithmic 30-day disruption diagnostic metrics detecting supply chain contraction or expansion.
3. **Live AIS Transiting Fleet Radar:**
   - Active vessels underway in strategic waterways with speed, GPS coordinates, flag, reported cargo manifest, and MMSI identifiers.
4. **2026 Maritime Security & UK Naval Threat Ledger:**
   - Documented 2026 attacks, ballistic missiles, explosive USV boats, and armed boardings with official references from **UKMTO (UK Royal Navy)**, **Ambrey Intelligence London**, **UK MAIB**, and **Lloyd's JWC War Risk Ratings (JWLA)**.
5. **Global Commercial Fleet Registry & Ownership Directory (IMO/ITU/Equasis):**
   - Technical specifications, engine models, fuel grades, service speed, daily fuel consumption (MT/day), commercial operator, beneficial owner, P\&I Club, and War Risk routing statuses.
6. **Marine Bunker Futures & Geopolitical Rerouting Freight Modeler:**
   - Live Brent crude benchmark (`BZ=F`) and 5-Hub bunker price matrix (Singapore, Rotterdam, Gibraltar, Balboa, Houston) across VLSFO & MGO with forward curves.
   - Rerouting simulation calculating extra nautical miles, days at sea, fuel burned, and per-voyage/fleet cost shocks when diverting around Africa or South America.

***

### 📥 Input Configuration

| Field | Type | Default | Description |
| :--- | :--- | :--- | :--- |
| `chokepoints` | Array | `["ALL"]` | List of passages to analyze (`ALL`, `Bab el-Mandeb Strait`, `Suez Canal`, `Strait of Hormuz`, `Strait of Malacca`, `Panama Canal`, `Strait of Gibraltar`, etc.). |
| `daysBack` | Integer | `180` | Time series lookback for daily transits and 30-day disruption diagnostics. |
| `includeLiveAIS` | Boolean | `true` | Include active AIS vessels in regional waterways. |
| `includeSecurityLedger` | Boolean | `true` | Include 2026 UK naval security attacks and UKMTO warning bulletins. |
| `includeVesselRegistry` | Boolean | `true` | Include global commercial vessel specifications and ownership chains. |
| `includeBunkerEconomics` | Boolean | `true` | Include 5-hub marine bunker price matrix and rerouting freight simulations. |
| `vesselSearchFilter` | String | `""` | Optional search filter for specific ship name, IMO, or operator. |

***

### 📤 Output Dataset Format

The actor outputs clean, structured JSON objects with a `recordType` field:

#### 1. Strategic Chokepoint Telemetry (`chokepoint_telemetry`)

```json
{
  "recordType": "chokepoint_telemetry",
  "chokepointName": "Bab el-Mandeb Strait",
  "timestamp": "2026-09-27T10:00:00Z",
  "data": {
    "port_id": "choke003",
    "annual_vessel_volume": 21850,
    "fleet_distribution": {
      "containers": 8900,
      "oil_tankers": 5700,
      "dry_bulk": 4800
    },
    "security_risk_status": "Critical (Security Zone 2026)",
    "lloyds_jwc_war_zone": "JWLA-032 (High Risk War Zone - 1.0% Surcharge)",
    "supply_chain_diagnostics": {
      "baseline_180d_avg_daily_transits": 48.5,
      "recent_30d_avg_daily_transits": 28.2,
      "flow_deviation_pct": -41.86,
      "supply_chain_state": "CONTRACTION / REROUTING PRESSURE"
    }
  }
}
```

#### 2. 2026 UK Maritime Security Incident (`security_incident_2026`)

```json
{
  "recordType": "security_incident_2026",
  "chokepointName": "Bab el-Mandeb / Southern Red Sea",
  "timestamp": "2026-09-27T10:00:00Z",
  "data": {
    "incident_id": "INC-2026-0924-01",
    "date": "2026-09-24",
    "vessel_name": "MT Blue Ocean Star",
    "imo": "9488392",
    "flag": "Liberia 🇱🇷",
    "vessel_type": "Aframax Crude Oil Tanker",
    "attack_type": "USV Explosive Boat Swarm Attack",
    "uk_reporting_authority": "UKMTO (Royal Navy) & Ambrey London",
    "advisory_ref": "UKMTO Incident 142/2026",
    "lloyds_jwc_rating": "JWLA-032 (High War Risk - Level 5)",
    "summary": "Targeted 45 nm SW of Mokha by two uncrewed surface vessels (USVs). Verified by Ambrey London: Private security repelled craft."
  }
}
```

#### 3. Vessel Registry & Ownership Dossier (`vessel_dossier`)

```json
{
  "recordType": "vessel_dossier",
  "chokepointName": "Rerouted via Cape of Good Hope (2026 Routine)",
  "timestamp": "2026-09-27T10:00:00Z",
  "data": {
    "vessel_name": "MSC IRINA",
    "imo": "9929429",
    "mmsi": "636021961",
    "flag": "Liberia 🇱🇷",
    "vessel_type": "Ultra Large Container Vessel (Megamax-24)",
    "capacity": "24,346 TEU",
    "deadweight_dwt": 240000,
    "dimensions": { "loa_meters": 399.9, "beam_meters": 61.3, "max_draft_meters": 16.5 },
    "commercial_operator": "MSC Mediterranean Shipping Company (Switzerland)",
    "beneficial_owner": "Aponte Family Holding (Geneva, CH)",
    "pi_insurance_club": "UK P&I Club / Steamship Mutual"
  }
}
```

***

### ⚡ Integration & API Usage

You can run this Actor via the Apify API, Python SDK, or JavaScript SDK:

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_API_TOKEN>")

run = client.actor("your-username/marine-traffic-actor").call(run_input={
    "chokepoints": ["ALL"],
    "daysBack": 180,
    "includeLiveAIS": True,
    "includeSecurityLedger": True,
    "includeVesselRegistry": True,
    "includeBunkerEconomics": True
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)
```

# Actor input Schema

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

List of global passages to analyze. Select specific waterways or leave empty for ALL global chokepoints.

## `daysBack` (type: `integer`):

Number of historical days for daily vessel counts, capacity time-series, and 30-day disruption diagnostics.

## `includeLiveAIS` (type: `boolean`):

Extract active transiting vessels with GPS coordinates, speed, flag, cargo manifest, and MMSI identifiers.

## `includeSecurityLedger` (type: `boolean`):

Extract documented 2026 missile, drone, and USV strikes with UKMTO, Ambrey London, and Lloyd's JWC ratings.

## `includeVesselRegistry` (type: `boolean`):

Extract commercial fleet specifications, ownership chains, engine ratings, and War Risk routing statuses.

## `includeBunkerEconomics` (type: `boolean`):

Calculate 5-hub bunker fuel pricing (Singapore, Rotterdam, Gibraltar, Balboa, Houston) and geopolitical detour freight cost impacts.

## `vesselSearchFilter` (type: `string`):

Filter vessel registry by specific Ship Name, IMO, or Operator (e.g. 'EVER GIVEN', '9929429', 'Maersk', 'Frontline').

## Actor input object example

```json
{
  "chokepoints": [
    "ALL"
  ],
  "daysBack": 180,
  "includeLiveAIS": true,
  "includeSecurityLedger": true,
  "includeVesselRegistry": true,
  "includeBunkerEconomics": true
}
```

# Actor output Schema

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

Real-time PortWatch satellite transits, AIS fleet radar, 2026 UK naval security attack ledgers, and bunker rerouting models

## `summary` (type: `string`):

Master summary report and global chokepoint statistics

# 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 = {
    "chokepoints": [
        "ALL"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("khnaami/global-maritime-intelligence-strategic-chokepoints-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 = { "chokepoints": ["ALL"] }

# Run the Actor and wait for it to finish
run = client.actor("khnaami/global-maritime-intelligence-strategic-chokepoints-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 '{
  "chokepoints": [
    "ALL"
  ]
}' |
apify call khnaami/global-maritime-intelligence-strategic-chokepoints-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,khnaami/global-maritime-intelligence-strategic-chokepoints-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/3Mgl20fcbaDImErsu/builds/SwhY2AeujZqAr4cpp/openapi.json