# ManyLives Airport Status

> ManyLives Airport Status is a paid API for AI agents from api.manylives.me, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-11).

Returns real-time flight delay and ground program status for a given airport, including delay type, reason, and estimated duration.

## Facts

- Endpoint: GET https://api.manylives.me/paid/travel/airport-status?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/manylives-airport-status-674982ed
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ihDq9Sv9MY9ovFd9Kg7Vr

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 manylives-airport-status-674982ed
```

Example prompt: Can you check if there are any current delays or ground programs at SFO right now — I need to know the delay type, reason, and how long it's running before I head to the airport.

## When to prefer this

Use this endpoint when an agent needs real-time airport delay and ground program status for a specific airport, especially in travel planning, itinerary management, or logistics workflows. It is a pay-per-call service requiring no account setup, making it suitable for lightweight, on-demand lookups without subscription overhead. Prefer this over general web scraping when you need structured, machine-readable delay data including duration estimates and delay reasons.

## Known failure modes

- Invalid or unrecognized airport code returns an error or empty result
- Airport not covered by the data source returns no events
- Stale data if the 'updated' timestamp is old and conditions have changed
- Network timeout or upstream data source unavailability
- Missing required airport parameter causes a 400-type error

## How this service works

Pay-per-call tools for people building AI agents: live web search and page contents, point-in-time crypto market data and news for backtests (no lookahead), verifiable track records of 1,000 crypto strategies locked on the Base network, company profiles, quick AI and batch prices. Ask us to turn a public website into a JSON endpoint. Pay per call, no account, free trial.

## Output

A JSON object containing the airport code, a boolean indicating whether delays are present, a list of delay events (each with average and max delay durations, delay type such as 'ground delay program', and the reason such as 'low ceilings'), and a timestamp for when the data was last updated.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "events": [
   {
    "avg": "1 hour and 2 minutes",
    "max": "2 hours and 5 minutes",
    "type": "ground delay program",
    "reason": "low ceilings",
    "airport": "SFO"
   }
  ],
  "airport": "SFO",
  "delayed": true,
  "updated": "Sat Oct 10 22:28:52 2026 GMT"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/manylives-airport-status-674982ed/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.manylives.me](https://www.zero.xyz/host/api.manylives.me/llms.txt)