Thespacedevs LaunchLibrary API v2.3.0

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.