# Access and authentication

DivvLaunches has one public, read-only API and one MCP server. Neither needs a key, a token or an account.

## Reading

- REST: GET requests to https://www.divvlaunches.com/api/v1 and the paths listed there. Contract: https://www.divvlaunches.com/openapi.json.
- MCP: Streamable HTTP at https://www.divvlaunches.com/api/mcp, no authorization header. Discovery: https://www.divvlaunches.com/.well-known/mcp.json.
- Rate limit: 120 requests per 60 seconds per IP address, reported in RateLimit-* headers on every response. A 429 carries Retry-After.
- CORS: GET and OPTIONS from any origin.
- Errors: RFC 9457 Problem Details (application/problem+json) with code, detail, hint and retryable.

## Writing

There is no write API. Booking a launch, editing a listing, voting, commenting, subscribing and buying happen on the website by a signed-in person (Google sign-in), or through Dodo Payments checkout for purchases. Agents may link people to those pages; they may not act for them.

- Book a launch: https://www.divvlaunches.com/submit
- Pricing and purchases: https://www.divvlaunches.com/pricing
- Directory submissions: https://www.divvlaunches.com/directory-submissions

## Identity and data

- The API returns only public listing data: product names, taglines, descriptions, websites, maker names and public X handles, votes, launch dates, podium results, directories and blog posts.
- It never returns email addresses, account ids, moderation state, badge checks or anything from the dashboard.
- Questions, abuse reports and partnership requests: divv@divvlaunches.com.

Version 1.0.0. Terms: https://www.divvlaunches.com/terms. Privacy: https://www.divvlaunches.com/privacy.