Spire Developer Documentation

website·Indexed 38 days ago

https://developers.spire.com

Technical documentation for Spire's satellite services, including the Tasking API for constellation orientation and payload management, the Spire Linux Agent (v1.5.2) for payload-in-space customers, and the Signaling API (v1.0). Covers API authentication, satellite bus and data pipeline operations, scheduling, and SDK instantiation.

Tokens
28.9K
Snippets
161
Records
217
Agent score
52%

What's inside Spire

  1. Overview of the Spire Data Pipeline API

    The Data Pipeline API enables Space Services Customers to perform two primary data operations: downloading data from their payloads and receiving data uploaded to their payloads. This API is exposed and managed through the Spire Linux Agent (version 1.5.1).
  2. Overview of the Spire Satellite Bus API

    The Satellite Bus API provides Space Services Customers with the ability to access spacecraft position and attitude data in near real-time and issue dynamic pointing commands. This API is exposed and managed through the Spire Linux Agent (version 1.5.0).
  3. Overview of the Spire Linux Agent

    The Spire Linux Agent (version 1.5.2) is a daemon running on a Spire Space Services customer's payload. It provides a set of APIs that enable the payload to interface with the satellite bus. Note that the agent was formerly known as the OORT Agent, and the 'OORT' name may still appear in SDK modules and process names.
  4. Overview of the Spire Data Pipeline API

    The Data Pipeline API enables Space Services Customers to perform two primary data operations with their payloads: downloading data from payloads and receiving data uploaded to payloads. This API is exposed and managed through the Spire Linux Agent (Version 1.5.0).
  5. Overview of the Spire Linux Agent

    The Spire Linux Agent (version 1.5.0) is a daemon that runs on a Spire Space Services customer's payload. It provides a set of APIs that enable the payload to interface with the satellite bus. Note that the agent was formerly known as the OORT Agent, and the 'OORT' name may still appear in SDK modules and process names.
  6. Overview of the Spire Data Pipeline API

    The Data Pipeline API (Version 1.5.2) is used by Space Services Customers to manage data transfers for their payloads. It supports both downloading data from payloads and receiving data uploaded to payloads. The API is exposed and accessed through the Spire Linux Agent.
  7. Overview of the Spire Tasking API

    The Spire Tasking API provides a direct interface for scheduling windows within the Spire constellation. It is designed for both manual scheduling of individual windows and as a backend service for automated scheduling systems.
  8. Overview of Spire MockFM service

    MockFM is a ground-side service providing virtual satellites (mock Flight Models) to Space Services customers. It allows developers to familiarize themselves with the Tasking API and the process of interacting with space assets without requiring physical flight hardware. Spire treats MockFMs as assets in orbit, providing them with a realistic contact schedule for tasking and management.
  9. Overview of the Spire Satellite Bus API

    The Satellite Bus API (version 1.5.1) provides Space Services Customers with the ability to access spacecraft position and attitude data in near real-time and issue dynamic pointing commands. This API is exposed and managed through the Spire Linux Agent.
  10. Overview of the Spire Satellite Bus API

    The Satellite Bus API (Version 1.5.2) allows Space Services Customers to access spacecraft position and attitude data in near real-time and to issue dynamic pointing commands. This API is exposed and managed through the Spire Linux Agent.
  11. Overview of the Spire Linux Agent

    The Spire Linux Agent (version 1.5.1) is a daemon that runs on a Spire Space Services customer's payload. It provides a set of APIs that enable the payload to interface with the satellite bus. Note that the agent was formerly known as the OORT Agent, and the 'OORT' name may still appear in SDK modules and process names.
  12. Overview of the Spire Signaling API v2.0

    The Signaling API v2.0 defines the interface payloads must expose to receive notifications of upcoming events from the satellite bus. The system operates by having the satellite bus call a payload executable (payload_exec) via SSH. The bus provides window configuration files on the payload file system containing signal information and data from the Tasking API. The payload is responsible for implementing an executable that accepts specific arguments, interprets these configuration files, and performs the required actions.