Agent Protocol Specification
Version: 0.1.0 The RotaStellar Agent Protocol defines how satellite-side agents communicate with the Console API. It is a pull-based protocol designed for intermittent satellite connectivity.Authentication
All agent requests authenticate via API key in theX-API-Key header. The agent identifies itself via the X-Agent-ID header.
Agent Lifecycle
1. Register
The agent registers with the Console on first startup. This creates or updates an agent record.agent_id already exists for this user, the record is updated (upsert).
2. Poll for Workloads
The agent polls periodically for pending deployments assigned to its satellite.poll_interval_s and retry.
The server returns the oldest pending deployment where:
mode = 'live'satellite_idmatches the agent’s registered satellitestatus = 'pending'
dispatched.
3. Report Events
During execution, the agent reports events as they occur.job.accepted(whendispatched) → deployment status =runningjob.completed→ deployment status =completedjob.failed→ deployment status =failed
4. Report Telemetry
Agents send periodic heartbeats with health data.agent_id, status, and timestamp are optional.
Event Types
All events follow this structure:Lifecycle Events
Placement Events
Compute Events
Transfer Events
Security Events
Checkpoint Events
Orbital Compute Primitive Events
Eclipse, window, and pass steps emit specialized events. See Orbital Compute Primitives for details.Constellation Events
Multi-satellite DAG orchestration events. See Constellation Execution for details.ISL Transfer Events
Error Handling
All error responses follow this format:Rate Limits
Versioning
The protocol version is included in theUser-Agent header:

