canonical: https://jentic.com/apis/rocketlaunch.live/rocketlaunch-live

# RocketLaunch.Live API

API providing rocket launch data including companies, launches, locations, missions, pads, tags, and vehicles. The API exposes 8 endpoints.

## For AI agents

Programmatically get next launches (free), search launches. Covers 8 operations.

## Scope

Does not handle payments, communications, or crm - use for maps and geolocation only.

## Capabilities

- Get next launches (free)
- Search launches
- List companies
- Query and filter RocketLaunch.Live API records by parameters
- Monitor RocketLaunch.Live API operational status and events

## Use cases

### Maps and Geolocation Operations

Use the RocketLaunch.Live API to perform maps geolocation operations programmatically. The API provides 8 endpoints covering core functionality including get next launches (free), search launches, list companies.

Example prompt: Call GET `/json/launches/next/{count}` to get next launches (free)

### Automated Companies Management

Automate companies operations by combining multiple RocketLaunch.Live API endpoints. Agents can search launches and then list companies in a single workflow.

Example prompt: Call GET `/json/launches` to search launches, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call RocketLaunch.Live 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.

Example prompt: Search Jentic for 'get next launches (free)', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/json/launches/next/{count}` | Get next launches (free) |
| GET | `/json/launches` | Search launches |
| GET | `/json/companies` | List companies |
| GET | `/json/locations` | List locations |
| GET | `/json/missions` | List missions |
| GET | `/json/pads` | List launch pads |
| GET | `/json/tags` | List tags |
| GET | `/json/vehicles` | List vehicles |

## Key resources

- **Companies** — Operations related to Companies
- **Launches** — Operations related to Launches
- **Locations** — Operations related to Locations
- **Missions** — Operations related to Missions
- **Pads** — Operations related to Pads

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 63 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 58 / 100
  - Developer Experience & Jentic Compatibility: 61 / 100
  - AI-Readiness & Agent Experience: 42 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/rocketlaunch.live/rocketlaunch-live/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the RocketLaunch.Live API by hand still means writing the client, paging its launch and mission feeds, and handling the request plumbing yourself even though it needs no auth. Through Jentic you install once, import the RocketLaunch.Live API from the API Directory, and your agent calls it.
- **Permission scoping:** The RocketLaunch.Live API is read-only feeds whose filters travel in the request, so limit the agent to the operations it needs, such as fetching the next launches or listing missions. You choose which feeds it may call, and it can read only those.
- **Credential handling:** The RocketLaunch.Live API needs no credential, so there is no secret to store; any configuration your Jentic One instance holds stays out of the agent's prompt, logs, and context.
- **Discovery method:** Agents search Jentic by intent such as 'get the next launches' or 'list launch companies', and Jentic returns the matching RocketLaunch.Live operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Here** — Alternative maps geolocation API
- **Tomtom** — Alternative maps geolocation API
- **Googleapis** — Complementary maps geolocation API

## FAQ

### What authentication does the RocketLaunch.Live API use?

The RocketLaunch.Live API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get next launches (free) with the RocketLaunch.Live API?

Yes. Use the GET `/json/launches/next/{count}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the RocketLaunch.Live 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 get next launches (free) through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get next launches (free)'. Jentic returns the matching RocketLaunch.Live API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the RocketLaunch.Live API have?

The RocketLaunch.Live API exposes 8 endpoints covering companies, launches, locations operations.

### Can I limit what my agent is allowed to do with the RocketLaunch.Live API?

Yes. Jentic One is self-hosted, so your own rules decide which RocketLaunch.Live operations the agent may call. Because these are read-only feeds, you can grant only the operations the agent needs, such as GET `/json/launches/next/{count}` for upcoming launches or GET `/json/missions`, while withholding others like listing companies, pads, or vehicles. The agent can read only the feeds you allow and cannot reach the rest.