Pay-per-request METAR weather observations for any airport via FlightAware AeroAPI, settled with USDC micropayments.
What it does
This endpoint returns current METAR weather observations for a specific airport, identified by its ICAO or IATA code in the URL path parameter `:id`. It is part of the StableTravel API suite, which proxies FlightAware AeroAPI data through a pay-per-request MPP/x402 micropayment layer. Each call costs $0.004 (0.4 cents) in USDC, settled on Tempo L2 (chain ID 4217). No API keys or subscriptions are required — payment serves as authentication.
The response includes decoded METAR data: temperature, dewpoint, humidity percentage, barometric pressure, wind speed/direction, visibility, cloud layers, flight rules (VFR/IFR/etc.), density altitude, and the raw METAR string. Optional query parameters let you choose temperature units (fahrenheit or celsius) and request nearby weather station data via `return_nearby_weather=true`. A `timestamp` parameter allows querying historical observations.
This endpoint is one of over 60 travel-related endpoints on StableTravel, which covers flights (Amadeus GDS), hotels, activities, transfers, Google Flights price comparison, and the full FlightAware AeroAPI surface including real-time flight tracking, airport delays, flight history, and disruption counts. The OpenAPI 3.1 spec is published at `/openapi.json` with full response schemas for this endpoint.
Capabilities
Use cases
- —Check current weather conditions at an airport before a flight
- —Determine VFR/IFR flight rules for flight planning
- —Monitor wind speed and visibility for ground operations decisions
- —Feed real-time airport weather into an autonomous travel-planning agent
- —Aggregate METAR data across airports for disruption prediction
Fit
Best for
- —AI travel agents needing real-time airport weather without API key management
- —Aviation applications requiring decoded METAR data on demand
- —Lightweight weather checks at sub-cent cost per call
- —Agents that need weather context alongside flight tracking data from the same provider
Not for
- —High-frequency weather polling (cost accumulates; consider a subscription weather service)
- —Non-aviation general weather forecasts (this is airport-specific METAR data only)
- —Historical weather time-series analysis (only single-timestamp queries supported)
Quick start
npx agentcash fetch "https://stabletravel.dev/api/flightaware/airports/KJFK/weather/observations?temperature_units=fahrenheit"Example
Response
{
"time": "2025-07-19T18:56:00Z",
"clouds": [],
"dewpoint": 8,
"pressure": 1015,
"raw_data": "KJFK 191856Z 24010KT 10SM SCT035 18/08 A2997",
"conditions": null,
"visibility": 10,
"wind_speed": 10,
"pressure_hg": 29.97,
"temperature": 18,
"airport_code": "KJFK",
"flight_rules": "VFR",
"humidity_pct": 55,
"wind_friendly": "SW at 10 kts",
"wind_variable": false,
"cloud_friendly": "Scattered clouds at 3500 ft",
"wind_direction": 240,
"density_altitude": 120
}Endpoint
Quality
Full OpenAPI 3.1 schema with detailed response properties, clear pricing ($0.004/call), live 402 MPP challenge captured, comprehensive documentation including parameter descriptions and workflow guidance. Only minor gap: no example response in the spec itself, so the example above is inferred from the schema.
Citations
- —Endpoint price is $0.004 per callhttps://stabletravel.dev/openapi.json
- —Payment is via Tempo L2 (chain ID 4217) using USDC micropayments, method=tempo, intent=chargehttps://stabletravel.dev/openapi.json
- —Optional parameters include temperature_units (fahrenheit/celsius), return_nearby_weather, and timestamphttps://stabletravel.dev/openapi.json
- —Response includes airport_code, cloud_friendly, clouds, conditions, density_altitude, dewpoint, flight_rules, humidity_pct, pressure, pressure_hg, raw_data, temperature, time, visibility, wind_direction, wind_friendly, wind_speed, wind_variablehttps://stabletravel.dev/openapi.json
- —No API keys needed; payment via USDC on Base, Solana, or Tempo serves as authenticationhttps://stabletravel.dev