Affiliate links. Fanvue links pay us.The Fanvue links on this page are affiliate links, marked “affiliate”. If you sign up through one, we earn a commission. It costs you nothing extra and does not change what we write. How it works
In short
- Fanvue has a documented public API and an MCP server that connects AI assistants to a creator account.
- To build an app you need a creator account with KYC completed. Scopes such as read:insights or write:chat set what the app can do.
- The documentation says OAuth 2.0 with PKCE and no static API keys. The API usage policy still describes API keys.
- The default rate limit in Fanvue's API policy is 100 requests per 60 seconds.
- A tool that sends messages to fans for you also raises the question of whether you have to say it is AI.
On this page
Yes, Fanvue (affiliate link, opens in a new tab) has a public API. It comes with documentation, an OAuth sign-in and an MCP server that connects an AI assistant directly to a creator account. Scopes (the permissions you give an app) decide what you can automate. FanvueFanvue Fanvue is a subscription content platform that officially allows AI creators and labels them as AI. Open the glossary’s own documents disagree on how you sign in. Check this before you write any code.
What the API and the MCP server cover
The MCP server at mcp.fanvue.com/mcp connects Claude, ChatGPT, Cursor, Claude Code, Codex and other MCP clients to a Fanvue account through Fanvue’s OAuth sign-in, with no API keys, so an assistant can “reply to fans, pull insights, and manage posts from a single MCP connection”. Its tools cover chats and fan messaging, posts and scheduling, media and the vault, insights including earnings and top supporters, lists and mass messaging, and agency management across creator accounts. “The assistant can only do what your own account can do”, rate limits match the rest of the API, and access can be revoked in Fanvue’s settings.
Fanvue API Documentation — MCP server (opens in a new tab)checked
Access is granted per scope: read:self; read:chat, and write:chat, described as “Create new chats and send messages. This scope is required for any chat-related actions that modify data.”; read:fan; read:creator and write:creator; read:media, and write:media, “Upload, modify, and manage media files and content assets. Also required for vault folder management.”; read:post and write:post; read:insights; read:tracking_links and write:tracking_links; read:agency, and write:agency, “Manage agency team members and invites, including inviting new team members and creators.”
Fanvue API Documentation — Scopes (opens in a new tab)checked
Here are the scopes, sorted by the jobs you would hand over:
| Job | Scopes it needs |
|---|---|
| Reply to fans, send mass messages | read:chat, write:chat |
| Post and schedule content | write:post, write:media |
| Earnings, trends, top supporters | read:insights |
| Track where fans come from | read:tracking_links, write:tracking_links |
| Run several creators as an agency | read:agency, write:agency |
Keep this table next to you when you connect anything. An earnings dashboard needs read:insights and nothing else. If a tool only shows you charts but asks for write:chat, it is asking for permission to message your fans.
How to get access to the Fanvue API
Building an app requires “a Fanvue creator account with KYC completed”, because “only creators can access the Builder area”. Authentication is OAuth 2.0: the app is registered in the developer area to get a client ID and secret, with redirect URIs for development and production, and the starter app requests the read:self scope plus the system scopes openid, offline_access and offline.
Fanvue API Documentation — Quick Start (opens in a new tab)checked
The documentation index describes Fanvue’s authentication as “OAuth 2.0 with PKCE so your app can act on a creator’s behalf, with no static API keys”.
Fanvue API Documentation — Docs for LLMs (opens in a new tab)checked
The KYCKYC KYC (know your customer) is the identity check a payout platform runs before it sends you money. Open the glossary rule matters for agencies. You can only open the developer area with a verified creator account. A developer who builds for an agency has to build under a creator’s identity. Every API call acts for whoever authorised it. Fanvue verification for AI creators explains what that verification involves.
Fanvue API rules and the rate limit
The policy’s authentication rule reads: “All secured endpoints require the header X-Fanvue-API-Key”. It allows one active key per user, states that “Keys are stored hashed and cannot be retrieved after creation”, and sets a default rate limit of “100 requests per 60 seconds per API Key”, answered with a 429 response when exceeded. Prohibited uses include exceeding rate limits, sharing API keys, and creating apps at a third party’s instruction. App builders are responsible for lawful processing of the data they access, and Fanvue may revoke access for breaches or abuse.
Fanvue Legal — API Access & Usage Policy (opens in a new tab)checked
What the sources do not say
Reconciling Fanvue's API policy with its documentation
This section was meant to explain how to get an API key. But Fanvue’s two official sources describe two different systems.
The API Access & Usage Policy describes a static key sent in a header. Each user gets one key, and the rate limit is counted per key. The developer documentation says the API uses OAuth 2.0 with PKCE and no static API keys, and the MCP server connects without keys. Both were read on 15 September 2026.
The likely explanation is that the policy was written before a move to OAuth. But neither page says so, and a guess should not be published as fact.
What to do: build against the documentation, because it describes the current sign-in. Apply the policy’s rules on sharing credentials, rate limits and third-party apps to whatever credential you hold.
Automatic messages to your fans
Any tool with write:chat can send messages that a fan will read as coming from the creator. That raises two questions, and two other articles answer them. Fanvue AI chatbot rules covers Fanvue’s rules on AI messaging and the EU AI Act’s rule on telling people they are talking to a chatbot. If a team writes the messages through agency access, Fanvue manager accounts and chatters covers the manager-account rules.
Before you connect anything to your account
- Give an app only the scopes the job needs. Compare what the app asks for with the table above.
- Never connect an app because a message told you to. Fanvue’s policy does not allow you to create apps because someone else told you to.
- Keep credentials (keys and secrets) out of code and shared documents.
- Know where to remove access: in Fanvue’s settings. That is also where you cut an MCP connection.
- Stay under the rate limit of 100 requests per 60 seconds, or build retries that wait when the API answers with 429.
Building on the Fanvue API or MCP? Ask the members who already have. Ask it in #technical-inquiries. Someone there has usually had the same problem.
An integration only pays off on a platform you plan to stay on. Is Fanvue legit goes through the terms that decide how you get paid. Platforms and payouts shows how to set up and run a Fanvue account for an AI personaAI persona An AI persona is an invented character. Her images, videos and captions are generated with AI instead of photographed, but she is presented and followed like any other account. Open the glossary.
Sources for this article
The platform rules, laws and numbers above come from these documents. The date says when we last opened each one and checked it.
Questions people ask
Does Fanvue have an API?
Yes. Fanvue documents a public API. It covers chats and messages, posts, media and the vault, insights, followers and subscribers, lists, tracking links and agency functions. Fanvue also runs an MCP server on top of it.
How do you get a Fanvue API key?
The current documentation does not use static keys. Apps sign in with OAuth 2.0 and PKCE. To build an app you need a creator account with KYC completed, because only that opens the developer area. Fanvue's API Access & Usage Policy still describes an API key sent in a header, so check which one applies before you build.
What is the Fanvue MCP server?
A server at mcp.fanvue.com that connects an AI assistant such as Claude, ChatGPT or Cursor to a Fanvue account through Fanvue's own sign-in. The assistant can then reply to fans, pull insights and manage posts. It can only do what the connected account can do.
What is the Fanvue API rate limit?
Fanvue's API policy sets a default of 100 requests per 60 seconds. The MCP server has the same limits as the rest of the API.