How connection works
Connection is how gateways, scripts, and IDEs participate in your Constellation OS program—the same API the console and assistant use.
Choose your path
| I want to… | Use |
|---|---|
| Call APIs from a service | API tokens |
| Run on a gateway or ground site | Fleet agent |
| Configure your IDE or agent | IDE handoff |
| Read request shapes | API reference |
API surfaces
| Surface | Purpose |
|---|---|
| Topology | Read fleet graph snapshots |
| Telemetry | Ingest metrics from edge collectors |
| Predictions | Run ML models (SNR, weather, jamming, etc.) |
| Federation | Request or supply capacity across partner networks (Enterprise) |
Each token carries scopes granted at creation time.
Telemetry routing
| Strategy | Behavior |
|---|---|
| Adaptive (default) | Direct API; fall back to console proxy on failure |
| Direct | Always use the Constellation API host |
| Console | Route through /app/api/os/ (restricted networks) |
Configure in Settings → API; the fleet agent reads resolved URLs from config.toml after configure.
Fleet agent install
curl -fsSL "https://console.constellation.space/app/integrations/install.sh" | bash -s -- \
--script-url "https://console.constellation.space/app/integrations/install.sh"
Then paste your token from Settings → API. Details: Fleet agent.
Security
Tokens are issued from the console, shown once, and validated on every API request. Revoke instantly in Settings; revocation propagates to the API gateway. Treat secrets like passwords—never commit to source control.