# TravelCheck Airport Risk

> TravelCheck Airport Risk is a paid API for AI agents from travelcheck-x402.fly.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Assesses operational and weather disruption risk for a U.S. commercial airport at a specific time, covering arrivals, departures, or both.

## Facts

- Endpoint: POST https://travelcheck-x402.fly.dev/v1/airport-risk
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/travelcheck-airport-risk-b2a6c34f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pd5UtcykHJuI7cQcZfxca

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 travelcheck-airport-risk-b2a6c34f -d '<json body>'
```

Example prompt: What's the disruption risk at ORD for departures this Friday at 7:30am — check both weather and operational factors?

## When to prefer this

Use this endpoint when an agent needs to proactively assess disruption risk at a specific U.S. airport near a known flight time — ideal for pre-trip planning, itinerary monitoring, or travel advisory workflows. Prefer this over generic weather APIs when the output needs to be aviation-specific and tied to a particular airport's operational context. Also prefer this over TravelCheck Connection Risk when the concern is airport-level disruption rather than a specific itinerary connection.

## Known failure modes

- Unsupported airport code returns error — only U.S. commercial airports are supported
- Invalid datetime format (must be ISO 8601 with timezone) causes validation failure
- Airport code not matching required 3-4 character alphanumeric pattern rejected
- Requests too far in the future may return lower-confidence or unavailable risk data
- Payment failure via x402 protocol results in 402 response and no data returned

## How this service works

Assess operational and weather disruption risk for a supported U.S. commercial airport near a requested time.

## Output

Returns a structured risk assessment for the specified airport and time window, including disruption risk scores and indicators for weather and operational factors affecting arrivals, departures, or both directions of travel.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "airport": {
   "type": "string",
   "pattern": "^[A-Z0-9]{3,4}$"
  },
  "direction": {
   "enum": [
    "arrivals",
    "departures",
    "both"
   ],
   "type": "string",
   "default": "both"
  },
  "targetTime": {
   "type": "string",
   "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d+)?(?:Z|[+-]\\d{2}:\\d{2})$"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/travelcheck-airport-risk-b2a6c34f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from travelcheck-x402.fly.dev](https://www.zero.xyz/host/travelcheck-x402.fly.dev/llms.txt)