Build on the routing layer

One API decides where AI compute jobs should run — orbital GPUs, terrestrial cloud, or edge — using live satellite positions, weather-gated pass windows, and real cost comparison. Route-only if you just want the decision; managed jobs if you want scheduling and public SLA grading.

60-second start — compute buyer

No signup needed for a first taste: grab the shared demo key, then ask for a routing decision.

# 1. Grab a demo API key (Pro-tier, shared, rate-limited)
curl https://www.orbitroute.ai/api/v1/keys/demo

# 2. Ask where a job should run — pure decision, no execution
curl -X POST https://www.orbitroute.ai/api/v1/route \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $YOUR_KEY" \
  -d '{"model_name": "llama-3-70b", "gpu_required": "H100",
       "input_size_mb": 512, "estimated_compute_seconds": 30}'

# 3. Or hand OrbitRoute the job: queued → pass-window scheduled → run → SLA-graded
curl -X POST https://www.orbitroute.ai/api/v1/jobs \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $YOUR_KEY" \
  -d '{"model_name": "llama-3-70b", "gpu_required": "H100",
       "input_size_mb": 512, "estimated_compute_seconds": 30}'

# 4. Check the public scoreboard — predicted vs actual, no key needed
curl https://www.orbitroute.ai/api/v1/jobs-stats/sla

Your own key (higher limits, your usage history): free signup — 100 routing decisions/day, no card.

60-second start — satellite operator

The federation API turns your capacity into routable supply: register once, advertise nodes, jobs route against your advertised physics and price.

# Register once — your or_op_ key is shown exactly once
curl -X POST https://www.orbitroute.ai/api/v1/federation/operators \
  -H "Content-Type: application/json" \
  -d '{"name": "Acme Orbital", "contact_email": "ops@acme.example", "jurisdiction": "US"}'

# Advertise a node → it becomes routable
curl -X POST https://www.orbitroute.ai/api/v1/federation/nodes \
  -H "Content-Type: application/json" \
  -H "X-Operator-Key: $ORBITROUTE_OPERATOR_KEY" \
  -d '{"node_id": "acme-tile-1", "norad_id": 25544, "gpu_type": "H100",
       "gpu_count": 8, "power_budget_w": 12000, "price_usd_per_gpu_hr": 1.99}'

Capability fields (power budget, eclipse battery fraction, ISL neighbors, jurisdiction, attestation) are in the full reference under CapabilityAdvertisement. Ground-segment partners: hello@orbitroute.ai.

Authentication

Core endpoints

SDKs

Python (sync + async, single httpx dependency) and TypeScript (zero-dependency, fetch-based) clients exist at v0.1.0 — install from source today; PyPI/npm publishing is coming. Until then the API surface above is small enough that plain HTTP is a fine integration path, and openapi.json feeds any generator.