# StableTravel Flight Intents

> StableTravel Flight Intents is a paid API for AI agents from StableTravel at stabletravel.dev, paid per call via MPP, $0.001/call, status unknown (last checked 2026-09-14).

Set a geographic bounding-box intent for push notifications about flights in a specified area

## Facts

- Endpoint: POST https://stabletravel.dev/api/flightaware/flights/:id/intents
- Price: $0.001/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Provider: StableTravel
- Docs: https://stabletravel.dev
- Website: https://stabletravel.dev
- Tags: amadeus, flightaware, flights, hotels, activities, transfers, travel, data, web
- Canonical page: https://www.zero.xyz/c/stabletravel-intents-8db00254
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5J_V0aYcTZ7n5cuELBPsj

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 stabletravel-intents-8db00254 -d '<json body>'
```

Example prompt: Set up push notification intents for flight ID AA123 covering the geographic bounding box from latitude 25° to 49° north and -125° to -67° longitude west to east, with a maximum of 100 results.

## When to prefer this

Use this endpoint when you need to register a geographic area of interest tied to a specific flight ID so that push notifications are triggered for matching flights. Prefer this over polling-based tracking when you need event-driven alerts rather than on-demand queries.

## Known failure modes

- Missing required bounding box coordinates (north, west, south, east) returns 400 Bad Request
- Invalid flight ID in path returns 404 Not Found
- Longitude or latitude values out of valid range returns 422 Unprocessable Entity
- Insufficient USDC balance for $0.001 per-call fee returns 402 Payment Required
- FlightAware upstream service unavailable returns 503

## How this service works

Set flight intent for push notifications

## Output

A confirmation that the flight intent has been registered, associating the specified geographic bounding box (north, south, east, west boundaries) with the flight ID for push notification delivery.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "north",
  "west",
  "south",
  "east"
 ],
 "properties": {
  "max": {
   "type": "number",
   "description": "Maximum number of results (default 50)"
  },
  "east": {
   "type": "number",
   "description": "Eastern longitude boundary"
  },
  "west": {
   "type": "number",
   "description": "Western longitude boundary"
  },
  "north": {
   "type": "number",
   "description": "Northern latitude boundary"
  },
  "south": {
   "type": "number",
   "description": "Southern latitude boundary"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/stabletravel-intents-8db00254/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stabletravel.dev](https://www.zero.xyz/host/stabletravel.dev/llms.txt)