RAW API ACCESS: CODE YOUR LAUNCHES
Hit /api/v1 or wire up MCP. Full remote control of your Beast Launches account from code or Claude.
Updated
STRAIGHT TO THE CODE
You get a REST API at /api/v1. Full OpenAPI 3.1 spec lives at /api/v1/openapi.json. No wrappers, no lies—read it and build what you need.
Your AI assistant? Plug it in via MCP at /mcp. Claude, ChatGPT, other MCP clients—they all work. Search launches. Read listings. Draft and manage your own stuff. Permissions are yours to set.
Everything is documented at /developers. Start there.
AUTHENTICATION AND KEYS
Sign in one of two ways:
- OAuth. Your assistant opens a sign-in page on this site. Clean and standard.
- Personal API key from /account/developers. You see it once. After that, only a hash gets stored. Lose it, generate another.
RULES THAT APPLY
Rate limits hit you. Daily quotas exist. Keep both in mind or requests will fail.
Payments always happen here. The API returns a checkout link—you pay on Beast Launches, not through code.
Voting is off-limits via API. That's community. Keep it that way.
Questions people ask
- Can my assistant sign in and manage my launches?
- Yes. Via MCP at /mcp, Claude and other clients can search launches, read your listings, and draft or manage your own with your permission. Sign in using OAuth (opens on this site) or a personal API key from /account/developers.
- What if I lose my API key?
- Keys are shown once only—after that, a hash is stored. If you lose it, generate a new one from /account/developers.
- Do rate limits actually matter?
- Yes. Rate limits and daily quotas apply to all API calls. Check the OpenAPI spec at /api/v1/openapi.json for the exact thresholds.