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.
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.)
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.
P2P Channel
Sub-second latency. Drones in radio range subscribe to each other's intent broadcasts. No central authority required for deconfliction.
Cloud Channel
Eventually-consistent mirror. Hash-chained logs for accident investigation, regulatory dashboards, and historical analysis.
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.
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.
/v1/reservationsReserve a 4D space-time slot in the hex grid.{
"vehicle_id": "uuid",
"route": [{ "lat": 13.7563, "lng": 100.5018 }, ...],
"altitude_band": 140,
"direction_class": "SE",
"eta_ms": 1200,
"priority": "delivery"
}{
"reservation_id": "rsv_4f3a...",
"cells": ["H7-NE-140", "H8-E-140", ...],
"expires_at": "2026-05-10T08:42:31Z"
}/v1/intentSubscribe to live intent broadcasts within a geo-radius.{
"subscribe": { "centre_lat": 13.75, "centre_lng": 100.5, "radius_m": 5000 }
}{
"vehicle_id": "uuid",
"position": { "lat": ..., "lng": ..., "alt": 140 },
"intent": { "next_cell": "H7-E-140", "uncertainty_m": 12 },
"trust_score": 0.94,
"ts": "..."
}/v1/negotiationsInitiate P2P negotiation for an intersection conflict.{
"initiator_id": "uuid",
"responder_id": "uuid",
"conflict_cell": "H7-NE-140",
"proposal": { "yield": false, "alt_change": +20 }
}{
"agreement": "accepted",
"fallback_used": false,
"log_hash": "0x4f3a89b1...",
"ts": "..."
}/v1/audit/{reservation_id}Retrieve hash-chained audit log for a reservation.—{
"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.
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.
// click Send to call the mock endpoint
Try: remove a field → 422 · invalid direction → 422 · valid body → 201 with reservation_id
From reservation to resolution.
A canonical drone-to-drone negotiation. Negotiation bound (filed, Claim 3): 500 ms maximum.
| # | Actor | Action | Target |
|---|---|---|---|
| 01 | Drone A | POST /reservations | VerSky Cloud |
| 02 | VerSky Cloud | 200 OK + reservation_id | Drone A |
| 03 | Drone A | BROADCAST intent (P2P) | Nearby Drones |
| 04 | Drone B | Detect conflict at H7-NE-140 | — |
| 05 | Drone B | POST /negotiations | Drone A (P2P) |
| 06 | Drone A | Counter-propose: altitude action | Drone B |
| 07 | Drone B | Accept · log hash 0x4f3a... | Both + Cloud |
| 08 | Drones | Execute resolution, broadcast new intent | All |
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.
Reference implementation, simulation harness — see /implement
Embedded SDK for flight controllers (PX4, ArduPilot)
High-throughput cloud workers
Browser/Node.js client SDK
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.