How to access our archive via API or MCP
Developers and AI assistants can query The Launch Directory through our REST API or connect over MCP.
Updated
Integration methods
We offer two ways to access the archive programmatically. The REST API at /api/v1 follows OpenAPI 3.1 standards; its specification is filed at /api/v1/openapi.json. Alternatively, AI assistants—including Claude, ChatGPT and other MCP clients—can connect to our remote MCP server at /mcp to search launches and read listings. With your permission, assistants may also draft and manage your own listings through this connection.
Full technical documentation is available at /developers.
Authentication
You may sign in using OAuth, which will open a sign-in page on this site, or by supplying a personal API key from /account/developers. Keys are displayed only once; we store only a hash of each key.
Operational constraints
Rate limits and daily quotas apply to all API requests. Payment transactions always occur on this site itself; the API returns a checkout link when payment is required. Note that voting is not available through the API.
Questions people ask
- Can I use an AI assistant to manage my listings on The Launch Directory?
- Yes. AI assistants connected over MCP can draft and manage your listings if you grant permission. They authenticate via OAuth, which will open a sign-in page on this site.
- Where do I find my API key?
- Personal API keys are generated and shown at /account/developers. Each key is displayed once only; we retain only a hash for verification.
- How are charges handled through the API?
- All payments are processed on The Launch Directory itself. When payment is needed, the API returns a checkout link; you complete the transaction here.