MPPtempoquality 0.82

Set flight intent for push notifications via FlightAware AeroAPI at $0.001/call

Price
$0.001 / call
Protocol
mpp
Verified
no
Endpoint
https://stabletravel.dev/api/flightaware/flights/:id/intents

What it does

This endpoint sets a flight intent for push notifications on a specific flight, proxied through StableTravel's FlightAware AeroAPI integration. It accepts a POST request with a flight identifier and an intent type (announced, scheduled, departed, enroute, approaching, arrived, diverted, or cancelled) and registers that intent for downstream push notification delivery. The cost is $0.001 per request.

StableTravel wraps FlightAware's AeroAPI behind a pay-per-request MPP/x402 micropayment layer. No API keys, OAuth tokens, or subscriptions are required — payment via USDC on Base, Solana, or Tempo serves as authentication. The endpoint URL pattern is `/api/flightaware/flights/{id}/intents` where `{id}` is a FlightAware `fa_flight_id`. The typical workflow is: look up a flight by ident to get the `fa_flight_id`, then POST to this intents endpoint to register for status change notifications.

The endpoint is part of a broader StableTravel API surface covering flights (Amadeus GDS), hotels, activities, transfers, Google Flights price comparison, and extensive FlightAware real-time tracking, airport info, weather, history, and disruption data — over 60 endpoints total, all pay-per-request.

Capabilities

flight-intent-registrationpush-notification-setupflightaware-aeroapi-proxyreal-time-flight-trackingmicropayment-authenticatedpay-per-request

Use cases

  • —Register for push notifications when a tracked flight departs, arrives, or is cancelled
  • —Build automated travel assistant agents that react to flight status changes in real time
  • —Set up flight monitoring for airport operations dashboards
  • —Enable proactive rebooking workflows when flights are diverted or cancelled
  • —Create passenger notification systems tied to specific flight events

Fit

Best for

  • —AI travel agents that need real-time flight event triggers
  • —Autonomous systems monitoring flight status for operational decisions
  • —Applications that need FlightAware data without managing API keys or subscriptions

Not for

  • —Searching or booking flights (use the /flights/search or /google-flights/search endpoints instead)
  • —Retrieving current flight position or track data (use /flights/{id}/position or /flights/{id}/track)

Quick start

npx agentcash fetch -X POST -H "Content-Type: application/json" \
  -d '{"ident": "UAL123", "intent": "departed"}' \
  "https://stabletravel.dev/api/flightaware/flights/UAL123-1234567890-airline-0123/intents"

Example

Request

{
  "ident": "UAL123",
  "intent": "departed"
}

Response

{}

Endpoint

URLhttps://stabletravel.dev/api/flightaware/flights/:id/intents
Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.82/ 1.00

Full OpenAPI 3.1 schema with request body, response schema, and clear pricing ($0.001/call). The endpoint is POST-only so the probe's HEAD/GET 405 is expected behavior, not a failure. Documentation is thorough with parameter enums and workflow guidance, though no example response body beyond empty object is provided.

Warnings

  • —Probe returned 405 on HEAD and GET because this is a POST-only endpoint — this is expected, not an outage signal
  • —The response schema is an empty object with additionalProperties, so the actual response structure is undocumented beyond success/failure
  • —Push notification delivery mechanism (webhook URL, callback registration) is not documented in the available material

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 16:37:02Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/PxLyQW