Documentation
OnlyFansAPI credits
Vendor credit model that affects Chatalyze ingest cost — external to our product billing.
External vendorChatalyze does not sell OnlyFansAPI credits. Credits are billed byOnlyFansAPI. Official reference:docs.onlyfansapi.com → Credits.
Chatalyze’s primary live path consumes OnlyFansAPI throughwebhooks (near-real-time) and optionalREST (backfill, account sync, auth). Understanding their credit rules helps you size a plan.
How Chatalyze uses credits
| Chatalyze feature | OnlyFansAPI surface | Credit impact (vendor rules) |
|---|---|---|
| Live message / money ingest | Webhooks | Vendor: typically 1 credit per 100 webhook events(confirm on their credits page) |
| Backfill chats/messages | REST list endpoints | Uncached account-specific calls usually1 credit per request (paginated = per page) |
| Account sync / auth | Accounts REST | Per-request uncached cost |
| Floor / metrics / AI in Chatalyze | None (our Worker) | 0 OnlyFansAPI credits — runs on Cloudflare after data is stored |
Vendor summary (verify upstream)
As of the public OnlyFansAPI credits documentation (always re-check their site before budgeting):
- Webhooks: ~1 credit per 100 events
- Uncached responses: 1 credit per request (including many upstream errors)
- Cached public responses: 0 credits; force with
?fresh=true - Media upload/download: 3 credits per MB (decimal MB)
- Not charged: rate-limit 429 from OFAPI edge, insufficient credits 402, failures before upstream call
Pin live numbersCredit tables change. Treatthe official credits pageas authoritative. Update this wiki page when their published rules change or when Chatalyze changes which OFAPI endpoints it calls.
Best practices for agencies
- Prefer webhooks for ongoing traffic; use backfill sparingly.
- Monitor balance inapp.onlyfansapi.com.
- Enable auto top-up on the vendor side if you run 24/7 multi-account ops.
- Chatalyze intelligence (rules/LLM) does not burn OFAPI credits after messages are stored.