Skip to main content
It depends on whose accounts you are working with. If you run your own OnlyFans accounts, or an agency’s, and want an AI agent to help, use the Operator path: connect your accounts once and point your agent at the OFAuth MCP server. If you are building a product that other creators or agencies connect their accounts to, use the Developer path: an External Integration with OAuth 2.0 and the Access API.

Frequently Asked Questions

Can I use both? Yes. They are separate plans for separate jobs. An agency can run its own accounts on an Operator plan and build a product for other creators on a Developer plan. Do operators need to write code? No. Operators connect accounts in the OFAuth dashboard and connect an AI agent that supports MCP. The agent does the work. Do developers need a real OnlyFans account to start? No. Sandbox returns mock data and never contacts OnlyFans. Real accounts come in at the Test stage. Is Realtime included? Account lifecycle webhooks are free. Realtime activity events, such as new chat messages, are an add-on on Developer plans: one switch for the organization, priced per monthly active account. What does it cost? Both paths bill monthly active accounts: accounts actually used that month. See pricing.

Operator or Developer?

Which Environment Should I Use?

Developers move through three isolated environments. Each has its own client ID, secret, redirect URIs, linked accounts, and webhooks.

Which Add-ons Do I Need?

Which Scopes Should I Request?

Only the ones your features use. Account owners see every scope on the consent screen, and you can ask for more later by running authorization again. Common sets: See the full list in Calling Access.

Learn More