# 2fans API vs Fanvue API

Fanvue is the closest comparison. Its Checkout Links are cheaper at 9.7% on cards, and it already has an SDK and an MCP server, but checkout is by approval, with KYC and KYB, and each creator has to be enabled. On 2fans, links work once a creator is verified and their content is approved, and approved apps earn 5% of sales.

| | 2fans API | Fanvue API |
| --- | --- | --- |
| 18+ content | Yes, from verified creators | Allowed on the platform; checkout needs written approval |
| Cost | 15% of each sale; no monthly, setup or listing fee | Checkout Links 9.7% on cards, 15% on BNPL; platform sales 20% |
| Getting checkout | Creator verification and approved content | By approval with KYC and KYB, enabled per creator |
| Earning as a builder | 5% of sales through your links, paid out of our fee | App Store billing: developer 80%, Fanvue 20% |
| API | REST, OpenAPI 3.1, bearer keys | REST, OpenAPI, OAuth 2.0 with PKCE |
| Rate limit | 300 a minute per app key | 200 a minute per user |
| Webhooks | HMAC-SHA256 signed; approved apps | HMAC-SHA256 signed |
| SDK | None published yet | npm @fanvue/builder-sdk |
| Sandbox | None; test with free drops | None |
| MCP server | None yet | Yes |

## Do you need your own processing contract?

**Adding pay-per-view for creators to your CRM: no.** Integrate the 2fans API and creators sell through 2fans links, on a checkout already set up for 18+ content. Providers advertise days or weeks for your own contract; in our experience it takes 6 to 12 months. Here you can be selling today, once the ID check and content are approved. Connecting other people's creators also takes an app review, usually a few business days.

**Selling your own products on your own checkout: yes.** 2fans can't take payments for those. Adult billers such as CCBill, Segpay and Verotel are the usual route.

**Want your own contract later?** Start here and you build real sales numbers first, with reports from the API. They aren't processing history on an account of your own, so each provider decides what they count for, but you'll apply knowing what sells.

## Where 2fans is the better fit

- You build for creators and want a commission on every sale through your links.
- You sell in chats and want per-fan references on Telegram and web links.
- You don’t want each creator to apply for checkout.

## Where Fanvue API is the better fit

- You can get approved and want the lower 9.7% on cards.
- You want an SDK and MCP server today.
- Your creators already earn on Fanvue.

## Create a pay-per-view link

```bash
curl -X POST "https://www.dropfans.io/api/external/v1/drops" \
  -H "Authorization: Bearer $DROPFANS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Beach set", "price": 15, "vaultItemIds": ["VAULT_ITEM_A", "VAULT_ITEM_B"] }'
```

Response:

```json
{ "productId": "…", "buyUrl": "https://www.dropfans.io/buy/…", "mediaCount": 2 }
```

2fans was called Dropfans until October 2026, so the API host is still www.dropfans.io and keys still start with dpfn_.

## Sources

- [Fanvue checkout seller terms](https://legal.fanvue.com/checkout-seller-terms)
- [Fanvue creator earnings](https://legal.fanvue.com/creator-earnings-payouts)
- [Fanvue checkout API](https://api.fanvue.com/docs/checkout/create.md)
- [Fanvue MCP server](https://api.fanvue.com/docs/mcp-server.md)
- [Fanvue rate limits](https://api.fanvue.com/docs/authentication/rate-limits.md)

Competitor details change, so check them before you decide. Last checked 2026-11-02. All pages: https://2fans.dev/llms.txt.