Straits.live premium data
Strait of Hormuz shadow-fleet risk screen: the live-AIS vessel population (vessels seen on AIS within the last activeWindowHours, currently 1.5) ranked worst-first, each hull with its risk band, the typed reasons behind it (ofac_sdn, ais_dark, foc_tanker, imo_spoofed), which sanctions bodies list it (US OFAC and/or UK/FCDO), and a lastSeenAt timestamp (when the hull was last listed, not necessarily its last true AIS fix) so listing recency can be checked per row. A transparent rules engine (not ML) fusing OFAC + UK sanctions, live AIS, AIS-dark gaps, and spoofed-IMO detection into one compliance-grade screen. counts cover the screened population, that is every hull seen on AIS inside the active window, not every hull ever tracked; vessels lists only the flagged hulls (high + moderate) by default, ?all=1 adds the cleared low-band hulls. Quality-gated on live AIS; flags are best-effort from the MMSI MID (ITU-T M.585). Because the screen is bounded to the active AIS window, an ais_dark reason (and counts.dark) surfaces only for a hull that has just reappeared in-window; the full recently-dark fleet count is exposed separately as darkFleetTotal.
Listing completeness · 80/100
Presence of published information only. Not a security, reliability or performance score. Same rules for Datoka and external listings.
- Name and traceable source
- 10/10 · Present
- Meaningful description
- 10/10 · Present
- Connection or installation reference
- 20/20 · Present
- Dedicated documentation or source repository
- 0/15 · Missing or insufficient
- Explicit free access or numeric tariff
- 20/20 · Present
- Declared integration protocol
- 10/10 · Present
- Source updated within 90 days
- 10/10 · Present
- Declared capability names
- 0/5 · Missing or insufficient
Evaluated 2026-10-08 · Method listing-completeness-1. Scoring rules
Connect & use
Connect through the publisher’s supported interface. Any credentials or payments are handled by the provider.
x402 resource
https://straits.live/api/premium/hormuz/risk-screenRead the current payment requirements with a compatible client before authorizing a call.
Categories and declared capabilities
Topic categories are derived from publisher text for discovery, not independently verified capabilities.
The registry does not provide a verified tools list. See the observations, when available, for any tools/list check; a published tools list does not establish that execution succeeds.
Evidence, with its limits.
This listing is indexed. Any domain claim or endpoint observation appears separately with its date and limited scope. No payment execution, factual accuracy or safety certification is inferred.