# TruthBear Shipping Region Gauge

> TruthBear Shipping Region Gauge is a paid API for AI agents from api.truthbear.co, paid per call via x402, $0.25/call, status unknown (last checked 2026-09-14).

Runs a 3-leg sequential chain (sea state/wind → wave decomposition/storm vs swell → AIS transit throughput) to assess current shipping chokepoint conditions at a specified location.

## Facts

- Endpoint: GET https://api.truthbear.co/gauge/shipping-region
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/truthbear-shipping-region-gauge-6038b48e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4JqyK9VhcAd-c5KXleC2-

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 truthbear-shipping-region-gauge-6038b48e
```

Example prompt: Can you pull the current shipping chokepoint gauge for the Malacca Strait — I want to see all three legs: sea state vs wind thresholds, wave decomposition including storm vs distant swell, and the realized AIS transit throughput, plus how many legs are lit for confidence?

## When to prefer this

Choose this endpoint when you need a real-time, multi-signal descriptive assessment of conditions at a specific global shipping chokepoint, aggregating sea state, wave physics, and AIS throughput into a single confidence-weighted chain. Prefer it over single-source weather or AIS APIs when you want corroborating legs rather than one signal, and over forecast services when a current descriptive reading is sufficient. Best when monitoring known chokepoints (Malacca, Suez, Hormuz, Panama, Good Hope, English Channel) for logistics routing decisions or risk assessment.

## Known failure modes

- 422 no_charge: no data available for the requested location — not billed
- Invalid loc parameter: unknown or unsupported location ID — check /gauge/preview for full list
- Partial confidence: one or more legs unlit due to missing upstream data from IMF PortWatch, NOAA, or Open-Meteo Marine
- Network timeout or upstream source unavailability resulting in incomplete chain response

## How this service works

Truth Bear reports facts and their official sources — screening-grade, verifiable, not predictions or advice. Pay per call with USDC (x402) or a 30-day access pass by card / Apple Pay / Google Pay / PayPal.

## Output

A JSON response containing up to three sequential gauge readings: (1) leading sea state and wind vs operating thresholds, (2) current wave decomposition distinguishing local storm from distant swell, and (3) realized AIS transit throughput as a confirmation gate. Each leg is either lit or unlit, and overall confidence is expressed as the count of consecutive lit legs. Returns a 422 no_charge error with no billing if data is unavailable. Descriptive only — not a forecast or advice.

## 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",
 "example": {
  "legs": {
   "sea_state": {
    "band": null,
    "source_ref": "https://open-meteo.com/en/docs/marine-weather-api",
    "record_hash": "sha256:a69ae225e6aa376b3bfa3d9e9a8dd435783ca62c149e599621be7f311ca1e329"
   },
   "throughput": {
    "band": "no-coverage",
    "source_ref": "https://aisstream.io/documentation",
    "record_hash": "sha256:ae1dd2720dd4ae4d8ca046122b1e250d5646968a1cf5aec3af06d4e179bffa1e"
   },
   "route_disruption": {
    "band": "operable",
    "source_ref": "https://open-meteo.com/en/docs/marine-weather-api",
    "record_hash": "sha256:713b0c84338039b1860da52058d9089cc1f2b32404a575bf3d5a550023bf0cb9"
   }
  },
  "name": "Suez / Red Sea approach",
  "grade": "screening-level, not decision-grade",
  "scope": {
   "full": "https://api.truthbear.co/scope/v1",
   "verifiability": "unknown",
   "monitoring_not_forecast": true,
   "intelligence_not_command": true
  },
  "nature": "This API supplies data organisation and trend description only. It is not a recommendation to act; the decision is yours. Purely descriptive - no judgement, no prediction. Official source plus record_hash; verify with the free /gauge/verify.",
  "location": "suez-redsea",
  "provenance": {
   "freshness": "fresh",
   "age_hours_now": 15,
   "freshness_basis": "cadence=default; fresh<=24h; recent<=192h; dead_source>1440h; age_basis=request-time(now minus observed_at)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/truthbear-shipping-region-gauge-6038b48e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.truthbear.co](https://www.zero.xyz/host/api.truthbear.co/llms.txt)