Eleven tabs, three spreadsheets, and somebody’s memory is not a Fansly reporting system. AI Fan Summaries consolidates earnings, trends, and period comparisons across every creator on your roster — filterable by account and date, ready before your AM stand-up starts.
Start FreePick a creator or your full Fansly roster, set a date range, and the dashboard does the math. No CSV exports, no copy-paste into Slides, no waiting for the data team.
One account, a pod of five, or the full 60-creator roster. Every metric, chart, and table snaps to the scope you picked. Solo creator check-ins and quarterly board reviews use the same screen — no extra exports.
Last 7 days, a specific calendar month, a launch week, a promotion cycle. The date picker shapes itself to your operating calendar — not the other way around. Built for how agencies run, not how dashboards are wired.
Subscriptions, posts, messages, tips, streams — every revenue category separated and summed. Plus account count, message volume, and media output. The exact line items your finance lead asks for, in the order they ask for them.
3, 6, or 12 months of Fansly earnings (subscriptions, posts, tips, streams) plotted as a single trend. Inflection points jump off the page. A flat decline reads as a flat decline — not 30 rows in a CSV nobody opens past line 6.
Stack two windows side by side. Absolute delta and percent shift across every line. Answer "what changed and by how much" in five seconds, not five minutes — and not after the executive review has already moved on.
Toggle between revenue categories without leaving the page. Surface the signal, skip the noise. Built for operators answering questions mid-call — not analysts running ad-hoc queries the day after.
Three endpoints power the core summary workflow: aggregated earnings overviews, time-series history, and structured period comparisons. Production-ready and fully documented.
Pull total earnings and category-level breakdowns - subscriptions, posts, messages, tips, streams and content stats for any combination of accounts.
Key endpoints
/api/analytics/summary/earningsReturn monthly aggregated revenue data across a configurable time range. Feed the numbers straight into trend charts to spot inflection points early.
Key endpoints
/api/analytics/summary/historicalCompare two time periods and get back summary totals, category breakdowns, and chart-ready data showing exactly what changed and by how much.
Key endpoints
/api/analytics/summary/comparisonWhether you manage 5 accounts or 200, AI Fan Summaries plugs into the workflows you already run — monthly closes, AM briefs, promo measurement, growth coaching.
Generate a consistent performance snapshot per AM: earnings mix, content output, creator-level KPIs. AMs walk into check-ins with answers — not "let me pull that and circle back."
Close monthly and quarterly cycles faster. Pre-structured summary and comparison views show exactly what moved and by how much. No ad-hoc spreadsheet assembly the night before payroll runs.
Line up creators side by side. Spot the outperformers and the underperformers. Redirect team hours toward the accounts with the highest upside — before another pay cycle slips past unnoticed.
Compare custom date windows around a campaign launch, pricing change, or content shift. Measure the lift in hard numbers — subscription dollars, PPV revenue, tip volume — not "felt like a good week."
90-second health check on any creator — or the full Fansly roster — during morning stand-up. Trend deltas tell you what needs attention today, before the issue becomes a quarterly write-down.
Hand creators the same consolidated view your AMs use. They see which earnings categories grew, which stalled, and where to push next — backed by their own data instead of an AM hunch.
What Fansly agencies and creators ask before consolidating their reporting on AI Fan Summaries.
Agencies use AI Fan Summaries to close monthly reporting in minutes and surface earnings shifts before they become problems. Solo creators use it to see exactly where income compounds — and where it leaks. Either way, the data is already waiting.