Access Rovexa Launch through API or MCP
Connect to our REST API or link an AI assistant via MCP to search and manage your launches.
Updated
API and MCP endpoints
Two routes are open for developer access. The REST API runs at /api/v1 with a full OpenAPI 3.1 specification at /api/v1/openapi.json. Alternatively, connect an AI assistant (Claude, ChatGPT or other MCP clients) to our remote MCP server at /mcp; this lets your assistant search launches, read listings and, with your permission, draft and manage your own.
Both paths log in the same way: either OAuth (your assistant opens our sign-in page) or a personal API key from /account/developers. Keys display once on generation; thereafter only a hash is kept on the bench.
What you can do
Through the API or MCP, you can search the catalogue and pull full listing details. If you own a product on Rovexa Launch, your assistant can draft new listings and update existing ones with your approval. This is useful for keeping launch data in sync across your own systems.
Constraints on the bench
Rate limits and daily quotas apply to all requests. Any charge triggers a checkout link from the API; you complete payment on this site itself. Note: votes cannot be bought and are not available through either route—the readout there comes only from visitor activity.
Questions people ask
- How do I create an API key?
- Visit /account/developers to generate a personal key. It will display once; save it then, as only a hash is stored after that.
- Can my AI assistant help manage listings?
- Yes, if you grant permission. Your assistant can draft new listings and update existing ones, but you must approve changes on this site.
- Where do I find API documentation?
- The full specification is at /api/v1/openapi.json. General developer guidance is at /developers.