Developers

A free, read-only API for the QueerCade catalog, version 1. No key or sign-in needed. It only returns games and collections that are public on this site — editorial notes, review data and member information are never included.

Endpoints

Base URL: https://queercade.gay/api/public/v1

GET /games

Search by title or LGBTQ+ character name. Filters: genre, platform, theme, year. Up to 48 per page.

Try it

GET /games/{slug}

One game with its full public details.

Try it

GET /collections

Every published collection.

Try it

GET /collections/{slug}

One collection and its games, in order.

Try it

GET /facets

The genre slugs, platform slugs and theme names the filters accept.

Try it

Paging, limits and errors

Paging. Use limit (1–48, default 24) and offset (0–10000). List responses include total and nextOffset; keep following nextOffset until it is null.
Rate limit. About 120 requests every 60 seconds per client. Responses carry X-RateLimit-* and RFC-style RateLimit-* headers; going over returns 429 with a Retry-After header in seconds.
Caching. Successful responses may be cached for 5 minutes. Please cache rather than re-poll.
Errors. Every failure returns { "error": { "code", "message", "status" } }. Codes: invalid_request, not_found, rate_limited, service_unavailable.
Methods and origins. GET only, all origins allowed, no authentication. There are no write endpoints.

MCP server

AI tools can connect straight to the catalog over the Model Context Protocol. Send JSON-RPC 2.0 requests by POST to https://queercade.gay/api/public/mcp. It is read-only and needs no credentials.

search_games — Search by title or character, with the same filters and paging as the API.
get_game — Full public details for one game by slug.
list_collections — Every published collection.
get_collection — One collection and its games, in editorial order.
list_facets — The values the filters accept.

For tools and AI agents

Please be gentle — no bulk scraping.

Versioning and deprecation policy

The current API version is v1. Breaking changes ship as a new versioned path; v1 keeps working. If an endpoint is ever deprecated, the deprecation is announced here with the replacement documented before the old one stops working.