Hormuz Risk Screen
by Straits.live premium data in Security & trust
Strait of Hormuz shadow-fleet risk screen: the live-AIS vessel population (seen in the last 1.5h) ranked worst-first, each hull with its risk band, typed reasons (ofac_sdn, ais_dark, foc_tanker, imo_spoofed (tanker or cargo IMO fails check digit)), the sanctions bodies listing it (US OFAC, UK/FCDO) and a lastSeenAt timestamp. A transparent rules engine, not ML. Lists flagged hulls (high + moderate); ?all=1 adds low-band hulls. Quality-gated on live AIS. Fleet-wide dark count: darkFleetTotal.
https://straits.live/api/premium/hormuz/risk-screen- Price
- $0.02
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 410 ms
- 926 ms slowest 5%
- Last check
- Passed
- 21 min ago, next in 12 min
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://straits.live/api/premium/hormuz/risk-screen
Each call costs $0.02 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://straits.live/api/premium/hormuz/risk-screen?all=1Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
all | string | No | Set to 1 to include the cleared low-band hulls (default: flagged only) |
Example response
The provider's example. We can't check it without paying.
Example response, 36 lines
{
"activeWindowHours": 1.5,
"counts": {
"dark": 0,
"high": 34,
"low": 1297,
"moderate": 81,
"sanctioned": 34,
"spoofed": 14,
"total": 1412
},
"darkFleetTotal": 71,
"health": {
"aisSource": "live",
"note": null,
"trusted": true
},
"schema": "https://straits.live/api/premium/hormuz/risk-screen",
"vessels": [
{
"band": "high",
"flag": "Iran",
"imo": "8517243",
"lastSeenAt": "2026-07-21T20:30:00Z",
"mmsi": "422143000",
"name": "MARIVAN",
"reasons": [
"ofac_sdn"
],
"sanctionedBy": [
"ofac"
]
}
],
"vesselsInclude": "flagged"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.02.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://straits.live/api/premium/hormuz/risk-screen?all=1'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://straits.live/api/premium/hormuz/risk-screen?all=1' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fstraits.live%2Fapi%2Fpremium%2Fhormuz%2Frisk-screen
const res = await pay("https://straits.live/api/premium/hormuz/risk-screen?all=1");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://straits.live/api/premium/hormuz/risk-screen?all=1")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 21 min ago | Passed | 402 | 662 ms | $0.02 |
| 4 h ago | Passed | 402 | 438 ms | $0.02 |
| 8 h ago | Passed | 402 | 383 ms | $0.02 |
| 12 h ago | Passed | 402 | 412 ms | $0.02 |
| 16 h ago | Passed | 402 | 480 ms | $0.02 |
Show 10 older checks
| 19 h ago | Passed | 402 | 1.0 s | $0.02 |
| 22 h ago | Passed | 402 | 393 ms | $0.02 |
| 25 h ago | Passed | 402 | 398 ms | $0.02 |
| 28 h ago | Passed | 402 | 328 ms | $0.02 |
| 31 h ago | Passed | 402 | 407 ms | $0.02 |
| 34 h ago | Passed | 402 | 355 ms | $0.02 |
| 39 h ago | Passed | 402 | 735 ms | $0.02 |
| 44 h ago | Passed | 402 | 388 ms | $0.02 |
| 2 days ago | Passed | 402 | 354 ms | $0.02 |
| 2 days ago | Passed | 402 | 368 ms | $0.02 |