passlisted in Coinbase#4 by calls of 7 on this host
0.02 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 3
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-10-08 05:36 UTC
- First observed by TOLLderived
- 2026-09-28
- Pricederived
- 0.02 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 43 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
TOLL files hormuz risk screen under identity: a GET endpoint on straits.live, listed in the Coinbase registry.
Per call, hormuz risk screen declares 0.02 USDC on Base.
hormuz risk screen takes the query parameter all.
Its example response has the fields counts, health, schema, vessels, darkFleetTotal, vesselsInclude and 1 other.
hormuz risk screen answered the sweep of 2026-10-23 with a valid 402, as at every sweep since 2026-09-29.
straits.live lists 7 endpoints; hormuz risk screen is tied 4th by calls with 1 other.
hormuz risk screen takes 10% of the calls counted across straits.live.
Over 30 days: 3 calls, 2 payers.
hormuz risk screen was last called 5 days before the snapshot.
Closest in price to hormuz risk screen within identity: decide at agent402.tools and contract at oracle.cyberwarex.com.
Among comparable prices in identity, hormuz risk screen sits above 69% of them.
hormuz risk screen out-counts 57% of the 2,150 endpoints in identity that carry counters.
The wallet paid by hormuz risk screen is the payee of 7 endpoints on one host.
The seller's own tags are maritime, shipping, hormuz and sanctions.
The price of hormuz risk screen is declared by 190 other listings in identity too.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.02 USDC | exact | 0x1B24dE…02Cf1f |
the checks, as of 2026-10-23 08:19 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-23 08:19 UTC | pass | 0 | daily-2026-10-23 |
| 2026-10-21 10:54 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-20 10:30 UTC | pass | 0 | daily-2026-10-20 |
| 2026-10-19 08:05 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 10:07 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-17 20:20 UTC | pass | 0 | daily-2026-10-17 |
| 2026-10-16 06:18 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 08:02 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 06:09 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 10:49 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 08:11 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 06:57 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 14:56 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 07:27 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 08:56 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 08:12 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 09:04 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 08:12 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 10:41 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 05:35 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 14:48 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 07:43 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 07:02 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 19:20 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-29 17:49 UTC | pass | 0 | new-after-daily-2026-09-28 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-08 05:36 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"all": "1"
}
},
"output": {
"type": "json",
"example": {
"counts": {
"low": 1297,
"dark": 0,
"high": 34,
"total": 1412,
"spoofed": 14,
"moderate": 81,
"sanctioned": 34
},
"health": {
"note": null,
"trusted": true,
"aisSource": "live"
},
"schema": "https://straits.live/api/premium/hormuz/risk-screen",
"vessels": [
{
"imo": "8517243",
"band": "high",
"flag": "Iran",
"mmsi": "422143000",
"name": "MARIVAN",
"reasons": [
"ofac_sdn"
],
"lastSeenAt": "2026-07-21T20:30:00Z",
"sanctionedBy": [
"ofac"
]
}
],
"darkFleetTotal": 71,
"vesselsInclude": "flagged",
"activeWindowHours": 1.5
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-13 14:08 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "hormuz risk screen on straits.live", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/straits-live-api-premium-hormuz-risk-screen-5f3997/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-straits-live-api-premium-hormuz-risk-screen-5f3997-2026-10-13T14-08Z,
author = {TOLL},
title = {hormuz risk screen on straits.live},
howpublished = {\url{https://tollindex.com/e/straits-live-api-premium-hormuz-risk-screen-5f3997/at/2026-10-13T14-08Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.