# How Many API Requests Does an OnlyFans Agency Need? Planning RPM and Credits

> Calculate the API requests and credits your OnlyFans agency needs to scale effectively. Learn to optimize throughput using our guide on RPM and plan capacities.

**TL;DR**

- Rate throughput (RPM) runs on a fixed 60-second window shared across the entire agency workspace, with no separate burst allowance.
- API credits measure the data weight of operations, where uncached requests cost 1 credit and cached responses cost 0 credits.
- Continuous polling exhausts both RPM and credits, making webhooks (Basic plan and up) the standard architecture for near real-time notifications.
- OnlyFansAPI plans scale from a Free tier at 60 RPM to a Pro tier at 5,000 RPM.

An OnlyFans agency's API capacity comes from its plan: OnlyFansAPI's Basic plan gives 1,000 API requests per minute (RPM) and 20,000 monthly credits for 1 account, and Pro gives 5,000 RPM and 100,000 monthly credits for 5 accounts, to support chatter workflows and CRM syncing. Planning this capacity requires calculating outbound data volume and transitioning from high-frequency polling to event-driven webhooks (Basic plan and up) to stay well below rate limits.

**Key Takeaways**

- Rate throughput (RPM) runs on a fixed 60-second window shared across the entire agency workspace, with no separate burst allowance.
- API credits measure the data weight of operations, where uncached requests cost 1 credit and cached responses cost 0 credits.
- Continuous polling exhausts both RPM and credits, making webhooks (Basic plan and up) the standard architecture for near real-time notifications.
- OnlyFansAPI plans scale from a Free tier at 60 RPM to a Pro tier at 5,000 RPM.

## Managing Rate Throughput and API Credits

Capacity planning separates how fast a system queries data from how much data it consumes. Throughput is measured in requests per minute (RPM) on a fixed 60-second window. This window is evaluated before cache lookups. Even if a requested resource is cached and costs zero credits, it still consumes one request from the per-minute limit.

Teams can monitor throughput in real time via the response headers `X-Rate-Limit-Limit-Minute` and `X-Rate-Limit-Remaining-Minute`, or through the `_meta._rate_limits` JSON payload object. Over the limit, the API returns `429 Too Many Requests`, and the [rate limits documentation](https://docs.onlyfansapi.com/introduction/essentials/rate-limits) recommends exponential backoff.

Your plan adds a monthly credit allowance to your balance, and unused credits stay in it. Uncached requests deduct 1 credit each, and each page of a paginated list is one request. Heavy data operations cost more. Exporting public profiles requires 3 credits per profile. Downloading media from OnlyFans costs 3 credits per decimal megabyte, while Fansly media downloads redirect directly to CDN sources at 0 credits.

## Planning RPM and Credits by Agency Plan

Every workspace shares a single rate limit pool across all API keys and connected accounts. The [OnlyFansAPI pricing page](https://onlyfansapi.com/pricing) sets exact RPM and credit limits based on operational scale across 320+ endpoints.

- **Free:** Connects 1 account with 60 RPM and 100 one-time credits. This tier has no webhooks, dedicated proxy, Smart Links or link tracking.
- **Basic:** Priced at $69/mo or $690/yr. It connects 1 account with 1,000 RPM and 20,000 credits/mo. It adds webhooks, a dedicated mobile proxy, Smart Links, and advanced link tracking.
- **Pro:** Priced at $299/mo or $2,990/yr. It includes 5 accounts and 5,000 RPM with 100,000 credits/mo. Each extra account (up to 500 accounts) adds 10,000 monthly credits and costs $29, scaling down to $11.60. This plan adds advanced analytics, custom API development, early access endpoints, and priority support.
- **Enterprise:** Custom pricing, recommended from 100+ accounts. It offers custom-built systems and a dedicated technical account manager.

All paid plans include a 60-day money-back guarantee.

## Why Event-Driven Webhooks Outperform Polling

Polling drives rate limit violations and credit exhaustion. Checking for new messages every five seconds generates 17,280 requests per day per creator. Account-specific endpoints are never cached, so each poll costs 1 credit and counts against the workspace rate limit, even when it returns nothing new.

Transitioning to webhooks (Basic plan and up) resolves data-pull bottlenecks. Instead of making continuous GET requests, the platform pushes data directly to your agency endpoint. Inbound webhook processing costs 1 credit per 100 webhook events.

Webhook events for these workflows include:

- `subscriptions.new`
- `subscriptions.renewed`
- `subscriptions.expired`
- `tips.received`
- `messages.received`
- `messages.ppv.unlocked`
- `transactions.new`
- `media_uploads.completed`

Our own Zapier and Make apps offer triggers for new subscriptions, renewals, messages received and PPV purchases, so teams can react to them without writing code.

## How to Stop Getting IP Banned When Pulling Creator Data

To stop getting IP banned when pulling creator data, replace aggressive polling scripts with event-driven webhooks and route each connected account through its own dedicated mobile IP.

Our internal systems apply request pacing matched to normal platform usage. On the Basic plan and up, OnlyFansAPI assigns one [dedicated mobile IP per connected account](https://onlyfansapi.com/onlyfans-proxy) (US or UK) with no rotation to keep every account protected. For a detailed guide on network architecture, read how to [avoid IP bans when pulling creator data](https://onlyfansapi.com/blog/avoid-ip-bans-creator-data).

OnlyFansAPI runs at 99.98% uptime, is used by 1,100+ companies, has 20k+ OnlyFans accounts protected and has recorded zero bans in 5+ years. Our service is not a scraper.

## Structuring Agency Workspace Capacity

Agencies map their usage against API infrastructure to estimate monthly costs and avoid limits.

### Boutique Operations on the Pro Plan

Take an agency managing 5 creator accounts that processes 10,000 inbound webhook events daily (3,000 credits monthly) and sends 1,500 outbound chat replies daily (45,000 credits monthly). Before analytics syncs, this consumes about 48,000 credits per month. The 100,000 credits included in the base Pro plan easily cover this load. 1,500 replies a day average about one request per minute, far under the 5,000 RPM workspace limit.

### High-Volume Agencies on Pro Tier Pricing

An agency managing 25 creator accounts adds 20 extra accounts to the base Pro tier. This brings the total monthly allowance to 300,000 credits. Processing 60,000 daily webhook events and 6,000 daily outbound API requests costs roughly 198,000 monthly credits. A [weekly mass message](https://onlyfansapi.com/onlyfans-mass-messaging-api) is a single API call: our queue sends it progressively, and the `chat_queue.updated` and `chat_queue.finished` webhooks report progress.

OnlyFansAPI has handled 300M+ API requests and webhooks. By watching the rate limit headers, developers can keep their automation under their plan's RPM and credit limits.