Custom Workloads
Instead of using a preset, you can define arbitrary step DAGs withcustom_job in your plan request. The planner handles placement, transfer insertion, and scheduling the same way it does for presets.
Request Structure
Sendcustom_job instead of preset_id in POST /v1/plan:
Step Schema
Each step in thesteps array:
Where the step runs:
onboard, ground, or either. When set to either, the planner decides based on data reduction ratio and transfer cost.Resource requirements:
power_w— Power consumption in wattscompute— Fraction of compute capacity (0.0–1.0)thermal_w— Thermal dissipation in wattsmemory_mb— Memory required in MBstorage_mb— Storage required in MB
Fault tolerance. If set, provide
min_data_fraction (0.0–1.0) and reduced_duration_s.Security Overrides
Optionalsecurity object at the job level:
restricted classification, authenticated uplink, key rotation every 24 orbits.
Policy
Optionalpolicy object:
Validation Rules
- Every step must have a unique
id depends_onreferences must point to existing step IDs- No circular dependencies (validated via DFS)
locationmust beonboard,ground, oreitherduration_smust be positiverequiresmust include all 5 resource fields
400 with a validation_error describing the issue.
Example
A 2-step pipeline: capture sensor data on-board, then process on the ground.The planner automatically inserts transfer steps (downlink/uplink) at space-ground boundaries. Your 2-step job may produce a plan with 3+ segments.

