Credit System
Understanding credit allocation and subscription plans
Credit calculator
Credit cost overview
Please refer to the table below to get a general overview of the credit cost for our endpoints.
For detailed information about where to find credit information in API responses, see our Response Structure documentation.
| Endpoint(s) | Cost | Notes |
|---|---|---|
| Search Profiles | 1 credit per result | E.g. if your search query has 10 results, you will be debited 10 credits. |
| Media Uploading | 3 credits per MB | Minimum 1 credit per file. For easy calculation, we use decimal measurements. This means that 1MB is 1,000 KB. |
| Media Downloading | 3 credits per MB | Minimum 1 credit per file. For easy calculation, we use decimal measurements. This means that 1MB is 1,000 KB. |
| Webhooks | 1 credit per 100 Webhook events | - |
| Data Exports (Public Profiles) | 3 credits per profile | - |
| Data Exports (Other) | 1 credit per 20 results | Applies to: Transactions, Chat Messages, Media, Trial Links, Tracking Links, Payouts, Chargebacks, Fans, Followings |
| AI Profile Summaries | 200 credits per generation | Applies to both initial generation and re-generation. |
| All other uncached responses | 1 credit per request | - |
| All other cached responses | 0 credits | - |
Cached vs uncached
Cached responses
Public endpoints make use of automatic caching by default, and thus won't cost you any credits if a cached response already exists.
Account-specific endpoints will never be cached, and will always give you a fresh response from OnlyFans.
Forcing a fresh response
You can force a fresh response by appending the endpoint URL with ?fresh=true
Uncached responses
All account-specific endpoints, and endpoints that reply on real-time data, will always return a fresh response from OnlyFans and thus will consume credits.
When are credits charged?
A credit is consumed whenever your request causes a call to OnlyFans or Fansly — including when the upstream response is an error (e.g. a 404, 400, upstream 429, or 5xx).
You are not charged for:
- Responses served from cache
- Requests rejected by our rate limiter (
429 Too Many Requests) - Requests rejected for insufficient credits (
402 Payment Required) - Failures on our side before the upstream call is made
Each page of a paginated list is one request — so one credit per page, if uncached.
Subscription Plans
Our subscription tiers provide different credit allocations:
Basic Plan • 20,000 credits per month
• Perfect for small to medium projects
• Includes all basic features
• Automatic credit tracking
Pro Plan • 100,000 credits per month
• Ideal for larger applications
• Priority support
• Advanced features included
Enterprise Plan • Custom credit allocation
• Tailored to your needs
• Contact us to discuss requirements
• Custom features and support
Buying extra credits
Need more credits than your monthly allowance? You can purchase one-time credit packs directly in the dashboard. Purchased credits are added on top of your monthly allowance and never expire.
| Credit pack | Price | Notes |
|---|---|---|
| 25,000 credits | $50 | - |
| 50,000 credits | $89 | - |
| 100,000 credits | $149 | - |
| 500,000 credits | $499 | Most popular |
| 1,000,000 credits | $799 | - |
| 5,000,000 credits | $3,499 | Best value |
Auto top-up: You can configure a balance threshold that automatically purchases a credit pack of your choice whenever your balance drops below it — so you never run out of credits mid-workflow.
Credit Features
All subscription tiers include:
Credit Rollover
• Unused credits stay in your balance
• Your credits never expire
• Purchased credit packs are added on top
Usage Monitoring
• Real-time balance tracking
• Detailed usage analytics
• Automated notifications
Cache Optimization
• Automatic response caching
• Zero-credit cached responses
• Cache control with ?fresh=true
Monitoring Tools
You can easily track your credit usage through all of our API responses, and through our Console
API Responses
- Real-time credit balance
- Request-specific credit usage
- Cache status indicators
Console Analytics
- Real-time credit balance
- View your rate limit usage
- Easily purchase more credits
Credit Management
Best practices for optimizing credit usage:
Efficient caching
Leverage cached responses when possible.
Credit balance monitoring
Monitor your credit balance regularly.
Usage patterns
Review usage patterns regularly. Consider optimizing your requests.
Cached responses are free and don't consume any credits from your balance. This applies to public endpoints like profile information.
Enterprise Solutions
For high-volume requirements, we offer:
Custom credit packages
Volume-based pricing
Priority support access
Custom SLA options
Please contact our team to discuss your specific needs and get a tailored solution.