OpenSky Network: what it returns, and whether it works in Clay

OpenSky Network is not available in Clay. It is best for Content demo, Monitoring. Pricing: Free. Access: Free REST API for non-profit research and education: anonymous 400 credits per day, registered 4,000, active feeders 8,000, licensed users 14,400 per hour; anonymous users get only the latest state vectors at 10 s resolution, registered users up to 1 hour back at 5 s. Any use by a for-profit or commercial entity requires a written licence from OpenSky (contact at opensky-network.org); commercial pricing not published..

Data domains: Transport, Locations.

What does OpenSky Network return?

Official fields: state vector icao24; callsign; origin_country; time_position; last_contact; longitude; latitude; baro_altitude; on_ground; velocity; true_track; vertical_rate; sensors; geo_altitude; squawk; spi; position_source; category. Flight objects (per OpenSky docs; table not rendered in my fetch) include icao24, firstSeen, estDepartureAirport, lastSeen, estArrivalAirport and callsign.

What can you derive from it?

1. Airport movements: estimated departures and arrivals per airport per day. 2. Aircraft activity: flights per icao24 over time for operators. 3. Trajectory checks: where an aircraft went on a given day.

How would a GTM team use it?

1. Diligence (research use): validate an aviation target's flight activity. 2. Market map: airports by movement volume for an aviation-services client. 3. Prototype: test an aircraft-based trigger before licensing ADS-B Exchange.

What are the caveats?

Not a native Clay integration as of 2026-10-17 (checked against Clay's integrations catalog). Can be called through Clay's HTTP API column where an API exists. Commercial use without a licence breaches OpenSky's terms, so a GTM practice should license first or use it only for research. No owner or operator data; join to the FAA registry. Coverage depends on volunteer receivers; flights/aircraft data is batch-updated nightly. Movement is not a business event.