Strait of Hormuz Intelligence Feed

Scrape Strait of Hormuz vessel positions and enrich each result with tanker flow, oil chokepoint, and maritime risk signals.

What This Actor Does

This Actor works like a Hormuz AIS and tanker traffic scraper with extra intelligence fields. It returns vessel rows from the Strait of Hormuz, Gulf of Oman approach, and Persian Gulf approach, then enriches each row with risk score, tanker classification, movement direction, slow/stopped vessel flags, news risk, and a plain-English recommendation.

It answers:

• Which vessels and tankers are currently visible around the Strait of Hormuz?
• Are tankers moving slowly or stopping near the transit corridor?
• Is visible tanker flow inbound, outbound, or mixed?
• Are shipping or geopolitical news signals elevated?
• Should risk teams monitor this chokepoint more closely?

Simple Input

The default settings are ready to run. No AIS API key is required.

{
  "includeNewsSignals": true,
  "includeAIS": true,
  "maxVessels": 100,
  "tankersOnly": false,
  "alertThreshold": 70
}

Input Fields

• includeNewsSignals - Add Hormuz, tanker, and maritime security news signals.
• includeAIS - Add public AIS/map vessel-density and slow-vessel signals.
• maxVessels - Maximum vessel rows to save. Default is 100.
• tankersOnly - Save only tanker-related vessels to the dataset.
• alertThreshold - Risk score level that triggers an alert.

Output

The Actor returns vessel rows:

• 1 dataset result = 1 vessel
• Each vessel row includes Hormuz risk context, tanker flow signal, risk score, and recommended action.
• The full Markdown intelligence brief is saved separately as REPORT.md.

Each vessel row can include:

• vessel_name
• mmsi
• imo
• source_ship_id
• vessel_type
• is_tanker
• tanker_category
• latitude
• longitude
• speed_knots
• course
• direction
• zone_segment
• zone_segments
• tanker_zone_segments
• destination
• is_slow_vessel
• is_stopped_or_waiting
• risk_score
• risk_level
• tanker_flow_signal
• pressure_signal
• news_risk_signal
• summary
• recommended_action

It also saves:

• REPORT.md
• SIGNALS.csv

Sources

• Public AIS/map tile signals for visible vessel positions.
• Google News RSS for Hormuz, tanker, and maritime disruption keywords.
• EIA World Oil Transit Chokepoints for static oil chokepoint context.
• IEA Strait of Hormuz oil security context for strategic importance and LNG exposure.

Zone Segments

The Actor classifies each vessel into one approximate monitoring segment:

• hormuz_transit_corridor
• fujairah_anchorage
• gulf_of_oman_approach
• persian_gulf_approach
• uae_oman_coastal_staging
• outer_monitoring_area

Example Output

{
  "row_type": "vessel",
  "date": "2026-05-22",
  "observed_at": "2026-05-22T10:12:47.000Z",
  "zone": "Strait of Hormuz",
  "source": "Public AIS map tile scraper",
  "vessel_name": "EXAMPLE TANKER",
  "mmsi": "422123456",
  "vessel_type": "Oil Tanker",
  "latitude": 26.18,
  "longitude": 56.32,
  "speed_knots": 2.4,
  "course": 105,
  "direction": "eastbound_outbound_to_gulf_of_oman",
  "is_tanker": true,
  "tanker_category": "oil_tanker",
  "is_slow_vessel": true,
  "is_stopped_or_waiting": false,
  "risk_score": 74,
  "risk_level": "high",
  "tanker_flow_signal": "declining",
  "pressure_signal": "stretched",
  "news_risk_signal": "medium",
  "summary": "Strait of Hormuz tanker and vessel risk is elevated. Vessel-density, slow movement, tanker concentration, or disruption news signals should be monitored closely.",
  "recommended_action": "Increase monitoring frequency and review tanker, insurance, and route exposure around the Hormuz transit corridor."
}

If AIS is unavailable, the Actor still saves REPORT.md and SIGNALS.csv with warnings.

Use Cases

• Energy market researchers monitoring oil chokepoint risk
• Maritime risk teams watching tanker movement
• Shipping analysts tracking Gulf of Oman and Persian Gulf traffic
• Insurance and compliance teams monitoring route exposure
• Newsletter writers creating maritime risk briefs
• Supply-chain risk platforms needing structured chokepoint signals

Notes

• Public AIS/map signals can be delayed, incomplete, or unavailable.
• EIA/IEA context is static reference context, not live flow volume.
• Vessel and news signals can change between runs.
• Each dataset result is normally one vessel row.
• Free preview runs are limited to 10 vessel rows.
• Pricing works naturally as results-based usage because vessel rows are the main dataset output.
• If a live source is unavailable, the Actor continues with the remaining sources and adds a warning.
• This Actor provides public-source risk signals, not official security, logistics, or financial advice.