Thespacedevs LaunchLibrary API v2.3.0

Name: LaunchLibrary API v2.3.0 API
Brand: LaunchLibrary API v2.3.0
Availability: InStock

✓ Official Vendor SpecCRMContact ManagementapiKey116 EndpointsREST

For Agents

Programmatically agencies_list, agencies_retrieve. Covers 116 operations with apiKey authentication.

Use for: I need to agencies_list, I want to agencies_retrieve, Search for api_throttle_list, Find all astronauts_list

Not supported: Does not handle payments, communications, or developer tools - use for crm only.

The [Launch Library 2](https://thespacedevs.com/llapi) (**LL2**) API is a product by [The Space Devs](https://thespacedevs.com) (**TSD**) with an up-to-date database of spaceflight events. ✅ API Version **Supported** ✅ This API version is the current latest supported version. Rate Limits While this API is **free to use**, it is subject to **rate limiting** (15 calls per hour) for non-authenticated. The API exposes 116 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the LaunchLibrary API v2.3.0 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LaunchLibrary API v2.3.0, 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fthespacedevs.com%2Fthespacedevs" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fthespacedevs.com%2Fthespacedevs" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 LaunchLibrary API v2.3.0 API.

agencies_list

agencies_retrieve

api_throttle_list

astronauts_list

astronauts_retrieve

GET STARTED

Start building with LaunchLibrary API v2.3.0 API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use LaunchLibrary API v2.3.0 API for, with concrete tasks.

★ CRM Operations

Use the LaunchLibrary API v2.3.0 to perform crm operations programmatically. The API provides 116 endpoints covering core functionality including agencies_list, agencies_retrieve, api_throttle_list.

Call GET /2.3.0/agencies/ to agencies_list

Automated 2.3.0 Management

Automate 2.3.0 operations by combining multiple LaunchLibrary API v2.3.0 endpoints. Agents can agencies_retrieve and then api_throttle_list in a single workflow.

Call GET /2.3.0/agencies/{id}/ to agencies_retrieve, then verify the result

AI Agent Integration via Jentic

AI agents discover and call LaunchLibrary API v2.3.0 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 apiKey tokens manually.

Search Jentic for 'agencies_list', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

116 endpoints — the [launch library 2](https://thespacedevs.

METHOD

PATH

DESCRIPTION

GET

/2.3.0/agencies/

agencies_list

GET

/2.3.0/agencies/{id}/

agencies_retrieve

GET

/2.3.0/api-throttle/

api_throttle_list

GET

/2.3.0/astronauts/

astronauts_list

GET

/2.3.0/astronauts/{id}/

astronauts_retrieve

GET

/2.3.0/celestial_bodies/

celestial_bodies_list

GET

/2.3.0/celestial_bodies/{id}/

celestial_bodies_retrieve

GET

/2.3.0/config/agency_types/

config_agency_types_list

GET

/2.3.0/agencies/

agencies_list

GET

/2.3.0/agencies/{id}/

agencies_retrieve

GET

/2.3.0/api-throttle/

api_throttle_list

GET

/2.3.0/astronauts/

astronauts_list

GET

/2.3.0/astronauts/{id}/

astronauts_retrieve

GET

/2.3.0/celestial_bodies/

celestial_bodies_list

GET

/2.3.0/celestial_bodies/{id}/

celestial_bodies_retrieve

GET

/2.3.0/config/agency_types/

config_agency_types_list

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the LaunchLibrary API by hand means adding its Token-prefixed Authorization header, choosing the rate-limited production host over the stale dev host, and handling your own retries. Through Jentic you install once, import the LaunchLibrary API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The LaunchLibrary API puts the record id in the URL path (/agencies/{id}/, /astronauts/{id}/), so a rule can pin your agent to a single record type: it can read those entries and nothing else. Every operation is read-only, so it retrieves data within the allowed set you describe and never mutates anything.

Credential isolation

Your LaunchLibrary token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list upcoming launches' or 'get astronaut details', and Jentic returns the matching LaunchLibrary operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using LaunchLibrary API v2.3.0 API through Jentic.

What authentication does the LaunchLibrary API v2.3.0 use?

The LaunchLibrary API v2.3.0 uses an API key passed in the `Authorization` header. 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 agencies_list with the LaunchLibrary API v2.3.0?

Yes. Use the GET /2.3.0/agencies/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the LaunchLibrary API v2.3.0?

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 agencies_list through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'agencies_list'. Jentic returns the matching LaunchLibrary API v2.3.0 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the LaunchLibrary API v2.3.0 have?

The LaunchLibrary API v2.3.0 exposes 116 endpoints covering 2.3.0 operations.

Can I limit what my agent is allowed to do with the LaunchLibrary API?

Yes. Because you run Jentic One yourself, self-hosted, your own rules decide which LaunchLibrary operations and credentials your agent may use. Every LaunchLibrary operation is read-only, so an agent can retrieve data but never change it, and since the record id sits in the URL path such as /agencies/{id}/ and /astronauts/{id}/, you can pin an agent to a single record type so it reads only those entries. That lets you grant, for example, astronaut lookups while withholding agency or launch queries.

Thespacedevs LaunchLibrary API v2.3.0

Connect the LaunchLibrary API v2.3.0 to your agent

Capabilities

Start building with LaunchLibrary API v2.3.0 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs