VerSkyLicense inquiry
Protocol Reference

Architecture, data flow, and API surface.

VerSky™ is a layered protocol — physical to application — built so any drone, eVTOL, or autonomous aerial vehicle can participate without vendor lock-in.

v0.1-alpha · Reference spec · Python MVP in tests · TS / C++ / Rust planned
System Overview

A four-tier system stack.

VerSky sits at Tier 3 — the protocol tier, between network transport and the application. Hardware (T1) and the OS/fleet manager (T4) are out of scope for the protocol itself. (The AACP Layers 1-5 referenced elsewhere on this site are the protocol-internal model inside Tier 3, not a different stack.)

Tier
T4
Application
Consumer-facing software that calls VerSky APIs.
Fleet ManagerDrone OSMission PlannerCompliance Dashboard
Tier
T3
Protocol
The patent-protected protocol tier — VerSky. Contains AACP Layers 1-5 internally.
Altitude-Direction EncodingHex-Cell Capacity4D Space-Time ReservationAACP P2P NegotiationTrust Scoring
Tier
T2
Network
Transport for protocol messages and audit logs.
P2P Mesh (LoRa / 5G)VerSky Cloud (REST + WS)Hash-Chain Log Sink
Tier
T1
Physical
Hardware that runs the protocol stack.
GNSS ReceiversIMU SensorsRadio / ModemCompute (MCU / SoC)
Data Flow

Two parallel channels: peer-to-peer and cloud.

Drones broadcast intent and position over P2P mesh radio for low-latency deconfliction. The same data is mirrored to VerSky Cloud for audit and visibility.

DRONE ADRONE BeVTOL CP2P MESHVerSky CloudREST · WSS · Hash LogHTTPS / WSSRegulator Dashboard(Read-only)AERIAL FLEETINFRASTRUCTURE
UDP · LoRa · 5G mesh

P2P Channel

Sub-second latency. Drones in radio range subscribe to each other's intent broadcasts. No central authority required for deconfliction.

HTTPS · WebSocket

Cloud Channel

Eventually-consistent mirror. Hash-chained logs for accident investigation, regulatory dashboards, and historical analysis.

Hex Spatial Reasoning

Why hexagons, not squares.

Square grids have eight neighbours but only four with equal distance — the diagonals are √2× further. Hexagons have six neighbours, all equidistant. That symmetry is what lets altitude encode direction uniformly.

SQUARE4 + 4 diagonalsHEX6 equidistantequal distance to all neighbours = uniform direction encoding
    Neighbours
    6 equidistant cells per altitude band
    Tessellation
    Perfect — no gaps, no overlaps
    Direction encoding
    6 hex faces × N altitude bands = 6×N total directional slots
    Conflict surface
    Reduced — each cell shares an edge, not a corner
    Cell capacity
    Per-cell soft cap based on radio range and minimum separation
API Reference · v0.1-alpha

REST + WebSocket surface.

The protocol exposes four primary endpoints. A Python reference implementation of these primitives is built and under test today (see /implement); other language SDKs are planned.

POST/v1/reservationsReserve a 4D space-time slot in the hex grid.
Request
{
  "vehicle_id": "uuid",
  "route": [{ "lat": 13.7563, "lng": 100.5018 }, ...],
  "altitude_band": 140,
  "direction_class": "SE",
  "eta_ms": 1200,
  "priority": "delivery"
}
Response
{
  "reservation_id": "rsv_4f3a...",
  "cells": ["H7-NE-140", "H8-E-140", ...],
  "expires_at": "2026-05-10T08:42:31Z"
}
WS/v1/intentSubscribe to live intent broadcasts within a geo-radius.
Request
{
  "subscribe": { "centre_lat": 13.75, "centre_lng": 100.5, "radius_m": 5000 }
}
Response
{
  "vehicle_id": "uuid",
  "position": { "lat": ..., "lng": ..., "alt": 140 },
  "intent": { "next_cell": "H7-E-140", "uncertainty_m": 12 },
  "trust_score": 0.94,
  "ts": "..."
}
POST/v1/negotiationsInitiate P2P negotiation for an intersection conflict.
Request
{
  "initiator_id": "uuid",
  "responder_id": "uuid",
  "conflict_cell": "H7-NE-140",
  "proposal": { "yield": false, "alt_change": +20 }
}
Response
{
  "agreement": "accepted",
  "fallback_used": false,
  "log_hash": "0x4f3a89b1...",
  "ts": "..."
}
GET/v1/audit/{reservation_id}Retrieve hash-chained audit log for a reservation.
Request
Response
{
  "reservation_id": "rsv_4f3a...",
  "events": [
    { "t": "...", "type": "reserved", "hash": "0x..." },
    { "t": "...", "type": "negotiation", "hash": "0x..." },
    ...
  ],
  "chain_valid": true
}

Reference spec only. URLs, field names, and types may change before v1.0. A Python reference implementation of the underlying primitives is already in tests; public SDK distribution and the finalised HTTP/WS surface remain roadmap items.

Try It

Call the reservation endpoint right here.

Edit the request body, hit Send, and inspect the response. This is a client-side mock built around the cell-level reservation primitive from the Python reference implementation — a simpler shape than the route-level draft shown in the API Reference table above. Both are illustrative; the final HTTP/WS contract is set ahead of v1.0.

POST/v1/reservationsdraft
Illustrative · client-side mock (no network)
Request body
Response
// click Send to call the mock endpoint

Try: remove a field → 422 · invalid direction → 422 · valid body → 201 with reservation_id

Negotiation Sequence

From reservation to resolution.

A canonical drone-to-drone negotiation. Negotiation bound (filed, Claim 3): 500 ms maximum.

#ActorActionTarget
01Drone APOST /reservationsVerSky Cloud
02VerSky Cloud200 OK + reservation_idDrone A
03Drone ABROADCAST intent (P2P)Nearby Drones
04Drone BDetect conflict at H7-NE-140
05Drone BPOST /negotiationsDrone A (P2P)
06Drone ACounter-propose: altitude actionDrone B
07Drone BAccept · log hash 0x4f3a...Both + Cloud
08DronesExecute resolution, broadcast new intentAll
Reference Implementation

Python today; other languages planned.

The Python reference implementation of the core primitives is built and under test today (pre-public-release, gated access). Public distribution and licensing terms are finalised ahead of release. Other language SDKs are roadmap items.

Python
MVP built

Reference implementation, simulation harness — see /implement

C / C++
Planned

Embedded SDK for flight controllers (PX4, ArduPilot)

Rust
Planned

High-throughput cloud workers

TypeScript
Planned

Browser/Node.js client SDK

License · TBD

Licensing terms for the reference implementation are to be determined. The design intent is a durable open framework for the protocol — final terms will be published on the Trust & License page ahead of release.