Spacexdata SpaceX API
✓ Official Vendor SpecDeveloper ToolsSource Controlnone18 EndpointsREST
For Agents
Programmatically list all launches, get latest launch. Covers 18 operations.
Use for: I need to all launches, I want to latest launch, Search for next launch, Find all past launches
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
Open source REST API for SpaceX launch, rocket, core, capsule, starlink, launchpad, and landing pad data. The API exposes 18 endpoints.
Install Jentic One Beta
Connect the SpaceX API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SpaceX API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with SpaceX API.
List all launches
Get latest launch
Integrate SpaceX API into automated workflows
Query and filter SpaceX API records by parameters
Monitor SpaceX API operational status and events
Use Cases
Patterns agents use SpaceX API for, with concrete tasks.
★ Developer Tools Operations
Use the SpaceX API to perform developer tools operations programmatically. The API provides 18 endpoints covering core functionality including list all launches, get latest launch, get next launch.
Call GET /launches to list all launches
Automated Capsules Management
Automate capsules operations by combining multiple SpaceX API endpoints. Agents can get latest launch and then get next launch in a single workflow.
Call GET /launches/latest to get latest launch, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SpaceX API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'list all launches', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
18 endpoints — open source rest api for spacex launch, rocket, core, capsule, starlink, launchpad, and landing pad data.
METHOD
PATH
DESCRIPTION
GET
/launches
List all launches
GET
/launches/latest
Get latest launch
GET
/launches/next
Get next launch
GET
/launches/past
List past launches
GET
/launches/upcoming
List upcoming launches
GET
/launches/{id}
Get a launch by ID
GET
/rockets
List all rockets
GET
/rockets/{id}
Get a rocket by ID
GET
/launches
List all launches
GET
/launches/latest
Get latest launch
GET
/launches/next
Get next launch
GET
/launches/past
List past launches
GET
/launches/upcoming
List upcoming launches
GET
/launches/{id}
Get a launch by ID
GET
/rockets
List all rockets
GET
/rockets/{id}
Get a rocket by ID
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
SpaceX API none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'list all launches') and Jentic returns the matching SpaceX API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct SpaceX API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using SpaceX API through Jentic.
What authentication does the SpaceX API use?
The SpaceX API uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I list all launches with the SpaceX API?
Yes. Use the GET /launches endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SpaceX API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I list all launches through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'list all launches'. Jentic returns the matching SpaceX API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the SpaceX API have?
The SpaceX API exposes 18 endpoints covering capsules, cores, landpads operations.
GET STARTED