# TravelPulse Flight Disruption Risk API

> TravelPulse Flight Disruption Risk API is a paid API for AI agents from travelpulse.theaslangroupllc.com, paid per call via x402, $0.25/call, status unknown (last checked 2026-09-16).

Returns a 0-100 disruption risk score for a given airport and date, combining live weather forecasts, strikes, congestion, and seasonal delay patterns, plus mitigation steps and applicable passenger-rights compensation regimes.

## Facts

- Endpoint: GET https://travelpulse.theaslangroupllc.com/api/travel/disruption
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/travelpulse-flight-disruption-risk-api-b786469e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1oTFJi9nqm1-IyN4BIK0x

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 travelpulse-flight-disruption-risk-api-b786469e
```

Example prompt: What's the flight disruption risk score for JFK on December 22nd — and if things go wrong, what compensation am I entitled to?

## When to prefer this

Use this endpoint when you need a single composite disruption risk score for a specific airport and date, especially when passenger-rights compensation context is also needed. Prefer this over a plain weather endpoint when strike, congestion, and regulatory compensation data are also relevant to the traveler's decision.

## Known failure modes

- Invalid or unrecognized airport code returns an error or empty result
- Date too far in future may result in lower-confidence scores or no live weather data
- Missing required parameters (airport or date) returns a validation error
- Weather data service unavailability may degrade score quality or cause timeout
- Non-existent date formats cause parse errors

## How this service works

Flight disruption risk for an airport and date: 0-100 risk score from live weather forecast plus strikes, congestion, and seasonal delay patterns, with mitigation steps and applicable passenger-rights compensation regimes.

## Output

A disruption risk score from 0 to 100 for the specified airport and date, derived from live weather forecasts, strike data, congestion levels, and seasonal delay patterns, along with recommended mitigation steps and an overview of applicable passenger-rights compensation regimes (e.g. EU261, UK261, Canada APPR).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "airport"
 ],
 "properties": {
  "date": {
   "type": "string",
   "description": "Travel date YYYY-MM-DD (defaults to near-term outlook)"
  },
  "lang": {
   "type": "string",
   "description": "Response language"
  },
  "airport": {
   "type": "string",
   "description": "Airport IATA code or city (e.g. JFK, Heathrow, Frankfurt)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/travelpulse-flight-disruption-risk-api-b786469e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from travelpulse.theaslangroupllc.com](https://www.zero.xyz/host/travelpulse.theaslangroupllc.com/llms.txt)