Hook up the API or plug in an AI assistant
Access launches and listings via REST API or MCP. Use OAuth or an API key to sign in.
Updated
We've built two ways in for people writing code or running AI assistants.
The REST API route
Hit /api/v1 and use the OpenAPI 3.1 spec at /api/v1/openapi.json to see what you can do. You authenticate with OAuth (we'll pop up a sign-in page) or grab a personal API key from /account/developers. Keys show once only—after that we just keep the hash. Head to /developers for the full docs.
AI assistants over MCP
We run an MCP server at /mcp. Claude, ChatGPT and other MCP clients can search launches and read listings through it. If you want your assistant to draft and manage your own listings too, you'll need to give it permission first.
The small print
Rate limits and daily quotas are in place. When you need to pay—say, to bump a listing—the API hands back a checkout link; you settle up here on Zivaro Launch, not anywhere else. And voting? That only happens in the app. No voting through the code.
Start at /developers for the nitty-grit. Build something good.
Questions people ask
- Can I use an AI assistant to manage my launch?
- Yes. Set up MCP at /mcp and give your assistant permission. It can then draft and manage your listings.
- Do I need OAuth or can I use an API key instead?
- Either works. OAuth opens a sign-in page. API keys live at /account/developers—they're shown once, then we store only the hash.
- Where do I handle payments if the API asks for money?
- The API returns a checkout link. You pay on this site, not through a third party.