Developers

SexyGen for developers

Integrate AI creator management and content generation into your own tools via a REST API or an MCP server. This page is the human-readable overview; the machine-readable references are linked from each section below.

Authentication

Create an account at sexygen.io/register, then generate a self-serve API key from the Developer tab of your dashboard. Send it as the X-API-Key header on REST calls, or as Authorization: Bearer on MCP calls.

REST API

The self-serve API covers creators (real and AI), photo/video generation, and dating-profile packs. Full reference:

/openapi.json — OpenAPI 3.0 specification (endpoints, parameters, auth, error shapes).
/llms-full.txt — endpoint-by-endpoint integration guide with example requests and responses.

Example request

curl https://sexygen.io/api/studio/presets \
  -H "X-API-Key: sk_live_your_key_here"

MCP server

For AI agents (Claude, ChatGPT, and other MCP-compatible clients), SexyGen also exposes a Streamable HTTP MCP server at https://sexygen.io/api/mcp, authenticated the same way as REST. It exposes tools to list and call the API, generate creator photos, and download generated media. See /.well-known/mcp.json for a machine-readable manifest, or /llms.txt for the full agent-oriented overview.

Versioning & deprecation

The current API version is 1, returned as the X-Api-Version response header on every /api/* call. No endpoint is deprecated today. When one is, we'll add Deprecation and Sunset response headers at least 90 days before removal.

Rate limits

Public and auth endpoints (registration, login, the waitlist form) are rate-limited per client IP and return RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and Retry-After (on 429) headers. The self-serve product API is not yet per-key rate-limited — back off on repeated errors in the meantime.

Questions about the API? Visit /contact.