# Straits.live Webhook Registration – Strait of Hormuz Crisis Monitor

> Straits.live Webhook Registration – Strait of Hormuz Crisis Monitor is a paid API for AI agents from straits.live, paid per call via x402, $0.5/call, status unknown (last checked 2026-09-15).

Registers a webhook subscription to receive real-time push notifications for Strait of Hormuz shipping crisis events

## Facts

- Endpoint: POST https://straits.live/api/premium/webhooks
- Price: $0.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/straits-live-webhook-registration-strait-of-hormuz-crisis-monitor-1368b172
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cEAfln4PH7M9VyCUzPa0B

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability straits-live-webhook-registration-strait-of-hormuz-crisis-monitor-1368b172 -d '<json body>'
```

Example prompt: Set up a webhook for me on Straits.live so I get pushed notifications whenever the Hormuz transit count or open/closed verdict changes — subscribe to all events and let me know the secret and expiry.

## When to prefer this

Choose this endpoint when you need event-driven, push-based notifications about Strait of Hormuz shipping crisis changes rather than polling. It is ideal for automated pipelines, trading systems, or dashboards that must react immediately to changes in transit counts, open/closed verdicts, or oil price triggers without continuously calling the status API. Prefer this over polling endpoints when low latency reaction to state changes is critical and you want to minimize API call costs.

## Known failure modes

- Invalid or missing 'events' filter string returns a 400 Bad Request
- Payment of 0.5 USDC not completed via x402 protocol results in 402 Payment Required
- Malformed webhook target URL causes registration failure
- Quota exhausted — deliveries remaining reaches 0 before expiry, stopping further notifications
- Webhook expires at expiresAt timestamp requiring re-registration
- Network or service downtime at straits.live causes registration to fail with 5xx error

## How this service works

Is the Strait of Hormuz open? Effectively no, it is closed to commercial shipping as of 13 July 2026. 34 ships transited vs ~88/day normal. Brent $81.10. Updated every 5 minutes.

## Output

Returns a JSON object containing a unique webhook ID, the schema URL for the subscription, a signing secret for payload verification, an expiry timestamp (e.g. 2026-08-08T12:00:00Z), and the number of remaining deliveries (e.g. 100). The agent can use the secret to validate incoming webhook payloads and the expiry to know when to renew.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "events": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "...",
  "schema": "https://straits.live/api/premium/webhooks",
  "secret": "...",
  "expiresAt": "2026-08-08T12:00:00Z",
  "deliveriesRemaining": 100
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/straits-live-webhook-registration-strait-of-hormuz-crisis-monitor-1368b172/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from straits.live](https://www.zero.xyz/host/straits.live/llms.txt)