Starport OS API

Programmatic access to Aevum Zenth's autonomous logistics, orbital routing, and fleet orchestration systems. RESTful, WebSocket streams, and GraphQL federation available.

Authentication & Base URL

All requests require an API key via the Authorization: Bearer <key> header. Keys are scoped to your organization tier and region endpoint.

Base URL

Auth Header

https://api.aevumzenth.com/v3/starport

Core Endpoints

Method	Path	Description
GET	/v3/starport/fleet/status	Retrieve real-time fleet readiness, telemetry health, and active routing assignments.
POST	/v3/starport/routes/optimize	Submit cargo/vehicle constraints for AI-driven pathfinding across orbital and terrestrial corridors.
PUT	/v3/starport/docking/slots/{id}	Reserve or modify orbital docking bay allocation with collision-free trajectory validation.
DELETE	/v3/starport/assignments/{id}	Cancel or abort an active logistics assignment. Triggers automated re-routing.

Request Example

cURL

Python

Node.js

curl -X POST https://api.aevumzenth.com/v3/starport/routes/optimize \
-H "Authorization: Bearer az_prod_..." \
-H "Content-Type: application/json" \
-d '{"origin": "GEO-SLOT-7", "destination": "LUNAR-PORT-ALPHA", "mass_kg": 4200, "priority": "high"}'

Response Structure

Successful route optimization returns a signed trajectory manifest with fuel estimations and docking windows.

JSON

                        {
                          "request_id": "req_9f8e7d6c5b4a3210",
                          "status": "optimized",
                          "trajectory": {
                            "delta_v_ms": 2450.3,
                            "flight_duration_sec": 14280,
                            "docking_window": "2026-11-14T08:30:00Z",
                            "collision_clearance": true
                          },
                          "fuel_estimate_kg": 184.5,
                          "signed_manifest": "az_sig_hmac256_7x9k2..."
                        }
                    

Rate Limits & Quotas

API access is governed by tier-based throughput limits. Starport OS routes are stateful and consume higher quota weights than telemetry reads.

Current Usage 14,280 / 50,000 req/hr

Exceeding limits returns 429 Too Many Requests with Retry-After header. Enterprise tiers support dynamic bursting.