Gee/Fans Developer Docs

Everything needed to drive Gee/Fans programmatically — by an AI agent or your own code. All endpoints are plain HTTPS/JSON under https://www.geefans.com/api/.

Resources

MCP server guide (recommended for agents)Connect directly to https://www.geefans.com/api/mcp — a hosted, streamable-HTTP MCP server. No local process, no repo checkout. Connect with no key to get onboarding tools that walk a new user through account + API key setup, or with a service key for the full authenticated toolset.OpenAPI 3.1 specificationMachine-readable spec of the full Gee/Fans API surface at /openapi.json: every endpoint, request/response schema, and the X-Service-Key security scheme. Load it into any OpenAPI-aware client or agent.Agent Integration Guide (markdown)The full API reference: authentication, the core pipeline (scan → marketing plan → Persona DNA → fan discovery → engagement briefs), and every content agent endpoint with request/response JSON. Written so an AI agent can drive Gee/Fans end to end.llms.txtMachine-readable product overview for LLMs and AI crawlers: what Gee/Fans is, every agent, and how to get started.sitemap.xmlEvery public page on geefans.com.

Authentication

Service key (recommended for agents): send an X-Service-Key header on every request. No account, no cookies, no model API keys needed — text generation runs on platform keys. Service keys are issued by the Gee/Fans team; ask via the Feedback button.

User session: sign up at geefans.com/auth/signup and add your own provider API keys in Settings (BYOK).

Always call https://www.geefans.com (with www) so redirects do not strip auth headers. Generation endpoints are not idempotent — do not blind-retry.

Markdown for agents

Public pages on geefans.com support markdown content negotiation: request any page with Accept: text/markdown and you get a clean markdown representation from the same URL. Nonexistent paths return a real 404 with a markdown body pointing back at these resources.