U-space is the European framework for managing large numbers of drones in shared airspace. It defines mandatory services — network identification, geo-awareness, flight authorisation and traffic information — delivered by certified U-space service providers that operators must connect to in designated airspace.
EASA U-space
Statute European Union
U-space is unusual among regulations in that it does not merely permit or forbid: it specifies services. An operator in U-space airspace connects to providers for identification, authorisation and traffic information, which makes the regulation itself an integration requirement.
- Four mandatory services - Network identification, geo-awareness, flight authorisation and traffic information.
- Certified service providers - A supervised provider market, rather than a single state-run system.
- Designated airspace - Member states decide where U-space applies, which paces the rollout.
- Interfaces by necessity - Services delivered to operators at scale are, unavoidably, APIs.
U-space is the closest thing in robotics to the mandated-API pattern this research has documented in banking and health. It does not say publish an API; it defines services that cannot practically be delivered as anything else. The State of Robotics & Autonomous Systems APIs argues that where a rule demands machine-readable exchange, interfaces follow — and U-space is the European test of that proposition, still early enough to watch.
Referenced in API Evangelist papers
This regulation shows up in my published research. These reports read the machine-readable evidence provider by provider — and put this regulation in the context of a real sector.
The State of Robotics & Autonomous Systems APIs
A regulation that specifies SERVICES rather than permissions — the closest thing in robotics to the mandated-API pattern seen in banking and health.
