# US Land Border Crossing Wait & Logistics Disruption Gauge

> US Land Border Crossing Wait & Logistics Disruption Gauge 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-15).

Returns a real-time causal-chain snapshot for a specific US land border crossing: upstream pressure signals, current CBP wait times by lane type, and downstream logistics/supply-chain impact indicators.

## Facts

- Endpoint: GET https://aeml-x402.zeabur.app/gauge/border-wait-region
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/us-land-border-crossing-wait-logistics-disruption-gauge-95bf3679
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Xq5SjTN7I7O_dly_neXEs

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 us-land-border-crossing-wait-logistics-disruption-gauge-95bf3679
```

Example prompt: Pull the current border wait and logistics disruption snapshot for Laredo World Trade — I need to see CBP commercial truck wait times, open lane counts, upstream pressure signals, and any downstream supply-chain impact right now.

## When to prefer this

Choose this endpoint when you need a single-call, causal-chain view of a specific US land border crossing combining official CBP wait time data with upstream pressure and downstream logistics impact signals — particularly for cross-border trucking operations, manufacturing supply-chain risk screening, or customs brokerage pre-clearance assessment. Prefer this over raw CBP data feeds when you need correlated multi-leg context and verifiable provenance in one response. Not suitable for turn-by-turn routing or binding customs advice.

## Known failure modes

- Unknown or unsupported entity key returns an error or empty legs
- CBP data source temporarily unavailable causes stale or missing wait time readings
- Data age may be hours old if CBP updates infrequently — flagged via freshness field
- Endpoint returns screening-level data only; not suitable for binding routing or customs decisions
- Commercial vs passenger lane availability varies by crossing; some lanes may report null if not applicable

## How this service works

[3-LEG] Land border chain, one crossing (?entity=laredo-world-trade): leading upstream pressure - lead traffic, staffing and inspection intensity -> current current CBP border wait times by lane -> realized realized commercial freight delay (confirmation gate). A sequential chain, not one reading - confidence = how many legs are lit, in order. Sources: US CBP. Descriptive only, never a forecast or advice. No data -> 422 no_charge, not billed.

## Output

A structured JSON object containing: a named entity key for the queried crossing, per-leg signal readings (upstream pressure, current CBP wait times by lane, downstream logistics impact), a cross-line narrative describing the causal relationship between signals, provenance metadata (data age, freshness, lineage traceable to CBP), a verifiable citation object with Ed25519 signature and record hash, an honest grade disclosure (screening-level, not decision-grade), and optional decision points indicating which parameters can be swapped for a follow-up call.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "queryParams"
   ],
   "properties": {
    "type": {
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "entity"
     ],
     "properties": {
      "entity": {
       "type": "string",
       "examples": [
        "laredo-world-trade",
        "laredo-colombia",
        "laredo-bridge1",
        "otay-mesa-commercial",
        "san-ysidro",
        "el-paso-ysleta"
       ],
       "description": "required - monitored object id, paired with signal_id; free list at GET /gauge/catalog?signal_id=<signal_id> -> signals[0].entities[]",
       "x-accepted-values": {
        "all": "https://api.truthbear.co/schemas/gauge-border-wait-region.input.json",
        "shown": 6,
        "total": 20
       }
      }
     },
     "additionalProperties": false
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "const": "json"
    },
    "example": {}
   }
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/us-land-border-crossing-wait-logistics-disruption-gauge-95bf3679/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)