Fanflet developer resources

Connect an AI agent to Fanflet with MCP. There is no public REST dump of public profiles and no API-key product. Speakers need Pro or Studio.

Machine-readable files

• OpenAPI 3.1 spec — /openapi.json
• Fanflet MCP and OAuth guide — /docs/mcp-for-agents
• llms.txt (when to use Fanflet) — /llms.txt
• MCP Streamable HTTP — /api/mcp
• MCP manifest — /.well-known/mcp.json
• MCP server card — /.well-known/mcp/server-card.json
• OAuth authorization server metadata — RFC 8414
• OAuth protected resource metadata — RFC 9728

Versioning

Current major version is 1. Unversioned /api/mcp is v1. /api/v1/mcp is an alias. Responses send X-API-Version: 1.

Deprecation: we will not remove v1 without a replacement. Deprecated routes send Deprecation and Sunset (RFC 8594) at least 90 days before removal.

Rate limits

Client registration is limited to 5 requests per 10 minutes per IP. Each tool call is limited to 60 per minute per signed-in user. Both counters live in memory on each server instance, so they are best-effort. Responses still send RateLimit-Limit: 120 and the matching remaining and reset headers. That advertised window is not the counter that refuses a call. A refused registration sends Retry-After.

No CLI

Fanflet does not publish an npm, PyPI, or Homebrew CLI. Agents should call MCP over Streamable HTTP after OAuth.