# UDAI System Overview

Unified Drone Airspace Interface (UDAI) is established as a **Digital Public Infrastructure (DPI)** to provide a secure, interoperable, and inclusive digital foundation for the national drone ecosystem. It serves as the digital backbone for low altitude airspace management, designed as a common good for regulators, manufacturers, and operators.

***

## 📌 Introduction

The **UDAI** platform is a digital registry and management system designed to enable controlled operations of unmanned aerial vehicles (UAVs) within managed airspace. The system provides a unified interface for drone traffic coordination, mission lifecycle management, and spatial policy enforcement.

***

## 🏗️ Core DPI Characteristics

### 1. Open Standards

UDAI implements open API specifications and data models. This ensures that any technical system can integrate with the platform without proprietary constraints. All technical definitions are public and follow system-wide compatibility guidelines.

### 2. Radical Inclusion

The system is architected to support entities of all sizes. Minimal technical barriers allow small-scale operators to access the same institutional-grade safety and registry tools as large industrial fleets.

### 3. Unified Registry

UDAI provides a single source of truth for:

* **Verified Pilots**: Identity management for remote pilots and administrators.
* **Organisation Registry**: National database of manufacturers, owners, and operators.
* **Asset Ledger**: Registry of physical drone assets and their ownership lifecycle.
* **Airspace Governance**: Defined segments of managed, restricted, or aware airspace.

### 4. Transparent Governance

Operational rules and airspace restrictions are managed through a centralized policy engine, ensuring all participants operate under the same verifiable, public rules.

***

## 🎯 Strategic Objectives

* **Safety**: Ensure secure and deconflicted drone operations in low-altitude airspace.
* **Compliance**: Enforce airspace rules and prevent unauthorized zone violations.
* **Awareness**: Enable real-time asset tracking and situational awareness.
* **Efficiency**: Streamline mission planning and automated permit approvals.
* **Governance**: Manage granular user roles and organisational hierarchies.
* **Accountability**: Maintain immutable audit logs for all systemic changes.

***

## ⚙️ Developer Guide

### 🔐 Security Architecture

* **Authentication**: Usage of JWT bearer tokens for all secure transactions.
* **Verification**: Multi-factor identity verification via email and phone OTP.
* **Authorisation**: Enforcement of RBAC and CBAC policies (Owner, Admin, Member, Monitor).
* **Auditability**: Comprehensive event logging for all registry and operational modifications.

### ⚙️ API Design Standards

* **RESTful Architecture**: All endpoints are resource-oriented and versioned (e.g., `/v1`).
* **Data Integrity**: Uses unified schemas and UUID identifiers for all resources.
* **Output Standards**: Supports consistent pagination, filtering, and sorting across collections.
* **Error Handling**: Standardized JSON error format for automated client-side processing.

### 🌐 API Access

**Technical Docs**: [Hostname and Error Codes](https://docs.udai.live/api-endpoints-reference/1.-authentication-apis/baseurl-api)

* **Base URL**: `https://api.udai.live/v1/`
* **JSON Format**: All requests and responses must use `application/json`.

### ❗ Error Format

All errors follow a consistent institutional pattern:

```json
{
  "error": "string",
  "message": "string",
  "status_code": 400,
  "timestamp": "2025-07-17T11:45:00Z",
  "path": "/api/v1/auth/login"
}
```

***

## 🧩 API Pillars

The UDAI system is strictly modular and divided into functional categories. For detailed technical specifications, refer to the [API Endpoints Reference](https://docs.udai.live/api-endpoints-reference) or the [Interactive API Specification](https://github.com/dronefed/udai-docs/blob/master/api-documentation/udai-api.yaml).

### 1. Authentication APIs

Handles identity management, OTP verification, organisation hierarchies, and access control policies.

### 2. Fleet APIs

Manages the national registry of drones, payload models, and asset ownership transfers.

### 3. Mission APIs

The orchestration layer for mission creation, flight planning, and spatial permit requests.

### 4. Telemetry APIs

Processes real-time flight session telemetry and provides live awareness fan-out to authorized monitors.

### 5. Airspace APIs

Governs 3D airspace zones, resource memberships, and the geospatial Constraint Engine.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.udai.live/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.