Credits & usage
What one credit is, which actions cost a credit and which are free, how monthly plan allowances and rollover work, and where to watch your usage in real time.
TEASE bills the deliberate work the platform does against your connected OnlyFans account — reading a conversation, capturing a campaign, checking your cash — in a single, transparent unit: the credit. You are never charged for the OnlyFans website's own background traffic, and never for a read we can serve from cache. You pay for capacity you actually asked for, and you can watch every credit as it's spent.
What a credit is
One credit is one deliberate action against your connected account. Concretely, a credit is spent when the engine, on your behalf, does one of the following:
| Action | What it does | Kind |
|---|---|---|
| Read a conversation | Harvest a DM thread for attribution, LTV, and the inbox | chat_read |
| Send a message | Deliver a 1-on-1 DM or one broadcast message | chat_send |
| Capture a campaign | Read a tracking campaign and its list of claimers | campaign_walk |
| List / create a link | Read your campaigns, or mint a new tracking link | campaign_list · campaign_create |
| Read trial stats | Pull performance for your trial links | trials_stats |
| Read your cash | Read transactions and payouts — the basis of revenue and attribution | money_read |
Each of these is a signed, first-party action the engine takes as your account. It is counted once, when it happens, at one credit — no per-byte surprises for a normal read.
These kind labels are exactly what you see in the panel's request monitor. Every row is
named in plain language («Чтение кассы», «Отправка сообщения») so a credit on your bill
always maps to an action you can point at.
What is free
Two large classes of traffic cost zero credits, always:
- The OnlyFans site's own background traffic. When the engine holds a live session, the OnlyFans web app loads its own feed, stories, subscriber lists, and housekeeping calls. That is the site talking to itself — you did not ask for it, it consumes no capacity we bill, and it never appears on your usage. In the monitor it's tagged «фон» and hidden unless you switch to «Всё».
- Cache hits. A value that hasn't changed since we last read it is served from our copy, not re-fetched from OnlyFans. Slow-moving reads (configuration, link metadata) are cached and reused, so polling a dashboard does not quietly drain credits.
You pay for fresh, deliberate data — nothing else
This is the whole billing philosophy: a credit represents real, fresh work done against your account. Ambient noise and cache hits are free by design, so your bill reflects the capacity you used, not the platform's plumbing.
Plan allowances
Each plan includes a monthly pool of credits. Unused credits and precise per-plan numbers are shown on your billing page; the current allowances are:
| Plan | Monthly credits | Best for |
|---|---|---|
| Free | 500 | Trying the funnel: links, routing, click stats |
| Pro | 25,000 | One model, live: real revenue, fans, and LTV by source |
| Studio | Unlimited | Agencies: multiple models, teams, priority |
Each additional connected account on a metered plan adds 10,000 credits to your monthly pool, so a second model doesn't eat into the first's allowance.
Allowances renew each calendar month. The owner account is never metered. Numbers here are the current defaults and can change as plans evolve — your billing page is always the source of truth for what you have left.
Watch your usage in real time
Two surfaces in the panel show exactly where credits go, reconciled to the same billable set:
Тариф и расход
Credits used vs. your monthly allowance, a breakdown by action kind, and a per-day chart.
Наши запросы
Every deliberate action as it happens, named in plain language — the exact billable rows.
Because the monitor's «Наши запросы» filter and the usage meter are driven by the same definition of a billable action, the count you see in the feed always reconciles with the number on your bill. Switch the monitor to «Всё» to see the free background traffic too — it's shown for transparency, never charged.
How this compares
If you've used a metered OnlyFans API before, the model will feel familiar: one credit per deliberate request, cache and ambient reads free. The difference is that TEASE meters the actions — named, in plain language, visible as they happen — rather than raw HTTP calls, so a credit always corresponds to something you can recognize on your account.
Next steps
- Scanning & data freshness — what the engine does, how often, and how safely.
- Rate limits — 429 backoff, and why fan-message pacing is separate.
- Chat & broadcasts — the inbox and paced, ban-safe sends.