Overview
Connect an AI assistant or a tool to your FanConvert account with an fc_sk_ key.
FanConvert opens up to your tools in two ways, with the same key:
| AI assistant (MCP) | Tool or developer (REST API) | |
|---|---|---|
| For | you and your team | a developer or an automation tool |
| Examples | Claude Code, or any MCP client | Zapier, Make, CRM, Google Sheets, your own script |
| Address | https://app.fanconvert.ai/mcp | https://app.fanconvert.ai/public/v1 |
| What you do | ask questions about your creators in plain language, no code | read your data, receive sales live (webhooks) |
What never changes
- No key can send a message to a fan. Neither the API nor the MCP server has a sending route.
- Admins only: only the organization's admins create and use a key.
- The same isolation as the dashboard: a key only sees the creators chosen when it was created; any other creator answers "not found".
- Revocable at any time in Settings › API & MCP: the key is cut off from its next request.
Beta
The public API and the MCP server are in Beta: some routes and fields may still change. Every change is listed in the changelog.
Where to start
Create a key
Settings › API & MCP › New key
Connect your assistant
Claude Code, or any MCP client
Get started with the REST API
First request in curl, JavaScript, Python
API reference
Every route, from the OpenAPI contract
For an AI writing code
- Index of this documentation:
/llms.txt, full text:/en/llms-full.txt. - Every page exists in Markdown: add
.mdto its address. - Full contract:
openapi.json(OpenAPI 3.1).
Last updated on