# AEML Shipping Region Gauge — Port & Maritime Disruption Triangle

> AEML Shipping Region Gauge — Port & Maritime Disruption Triangle is a paid API for AI agents from aeml-x402.zeabur.app, paid per call via x402, $0.25/call, status unknown (last checked 2026-09-13).

Returns a three-leg observable gauge for a named port/shipping region: sea-state disruption risk (WMO marine + wind vs operational thresholds), sea-state causal decomposition (swell vs local storm vs distant groundswell), and live AIS vessel-flow throughput/congestion, with a cross-validated narrative on whether sea-state disruption has propagated to actual vessel flow.

## Facts

- Endpoint: GET https://aeml-x402.zeabur.app/gauge/shipping-region
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aeml-shipping-region-gauge-port-maritime-disruption-triangle-f2296f7c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wp_w_rxAJosJ1wRnEUPM1

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 aeml-shipping-region-gauge-port-maritime-disruption-triangle-f2296f7c
```

Example prompt: Pull the full shipping disruption triangle for the Strait of Malacca — I want the current sea state vs operational limits, what's driving the swells (local storm or distant groundswell), live AIS vessel throughput and congestion, and whether the sea conditions have actually translated into fewer ships moving through.

## When to prefer this

Choose this endpoint when you need a single-call triangulated picture of both physical sea conditions AND actual vessel flow at a named maritime chokepoint or port — particularly when you want cross-validation between meteorological disruption signals and AIS-confirmed traffic impacts. Prefer this over raw weather APIs when you need the logistics interpretation layer, and over standalone AIS feeds when you need the causal sea-state context. Best for supply chain monitoring agents, freight risk dashboards, and commodity flow intelligence that needs verifiable, citable observational data rather than forecasts.

## Known failure modes

- Invalid or unrecognized loc parameter — returns error or empty legs
- AISstream data unavailable for a region — leg may be stale or missing
- Open-Meteo Marine API outage — sea-state leg may show stale/dead_source flag
- Freshness threshold exceeded — provenance.freshness returns 'stale'
- Chokepoint outside covered geography — 422 or empty response
- Payment not received (x402) — 402 Payment Required before data is returned
- All three legs stale simultaneously — cross_line_narrative may be unreliable

## How this service works

[3-LEG] Shipping chokepoint chain, one chokepoint or port (?loc=malacca): leading sea state and wind against operating thresholds -> current wave decomposition, local storm against distant swell -> realized AIS transit throughput (confirmation gate). A sequential chain, not one reading - confidence = how many legs are lit, in order. Sources: IMF PortWatch, NOAA, Open-Meteo Marine. Descriptive only, never a forecast or advice. No data -> 422 no_charge, not billed.

## Output

A structured JSON object with: (1) 'legs' object containing named signal readings for each of the three triangle legs (sea-state/WMO, swell decomposition, AIS throughput/congestion) with current values, observation timestamps, data age, and record hashes; (2) a cross_line_narrative string describing whether sea-state disruption has propagated to vessel flow; (3) provenance metadata including freshness status, data lineage, and oldest leg age; (4) an Ed25519-signed _citation block for zero-trust offline verification; (5) decision_points listing swappable parameters for re-runs; (6) grade and scope disclaimers indicating this is screening-level observational data, not decision-grade forecasting.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "type": {
     "const": "http"
    },
    "method": {
     "type": "string",
     "enum": [
      "GET"
     ]
    },
    "queryParams": {
     "type": "object",
     "additionalProperties": false,
     "properties": {
      "loc": {
       "type": "string",
       "description": "required - location id; full list at free /gauge/preview",
       "examples": [
        "suez-redsea",
        "panama-pacific",
        "malacca",
        "hormuz",
        "goodhope",
        "channel"
       ],
       "x-accepted-values": {
        "shown": 6,
        "total": 12,
        "all": "https://api.truthbear.co/schemas/gauge-shipping-region.input.json"
       }
      }
     },
     "required": [
      "loc"
     ]
    }
   },
   "required": [
    "type",
    "method",
    "queryParams"
   ]
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "const": "json"
    },
    "example": {}
   },
   "required": [
    "type"
   ]
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aeml-shipping-region-gauge-port-maritime-disruption-triangle-f2296f7c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from aeml-x402.zeabur.app](https://www.zero.xyz/host/aeml-x402.zeabur.app/llms.txt)