Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Query OnlyFans data and analytics via the OnlyFansAPI.com platform. Get revenue summaries across all models, identify top-performing models, analyze Free Trial and Tracking Link conversion rates, compare link earnings, and much more! Use when users ask about anything related to OnlyFans.
Query OnlyFans data and analytics via the OnlyFansAPI.com platform. Get revenue summaries across all models, identify top-performing models, analyze Free Trial and Tracking Link conversion rates, compare link earnings, and much more! Use when users ask about anything related to OnlyFans.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
This skill queries the OnlyFansAPI.com platform to answer questions about OnlyFans agency analytics โ revenue, model performance, and link conversion metrics.
The user must set the environment variable ONLYFANSAPI_API_KEY with their API key from https://app.onlyfansapi.com/api-keys. If the key is not set, remind the user: Export your OnlyFansAPI key: export ONLYFANSAPI_API_KEY="your_api_key_here"
Base URL: https://app.onlyfansapi.com Auth header: Authorization: Bearer $ONLYFANSAPI_API_KEY All dates use URL-encoded format: YYYY-MM-DD HH:MM:SS If not specific time is specified use start of day or end of day (for date range ending date) Pagination: use limit and offset query params. Check hasMore or _pagination.next_page in responses. Whenever possible use User-Agent with value: OnlyFansAPI-Skill Try your best to infer schema from the example response of the endpoint. Eg "data.total.total" for earnings scalar value from endpoint.
Steps: List all connected accounts: curl -s -H "Authorization: Bearer $ONLYFANSAPI_API_KEY" \ "https://app.onlyfansapi.com/api/accounts" | jq . Each account object has "id" (e.g. "acct_xxx"), "onlyfans_username", and "display_name". For each account, get earnings: START=$(date -u -v-7d '+%Y-%m-%d+00%%3A00%%3A00') # macOS # Linux: START=$(date -u -d '7 days ago' '+%Y-%m-%d+00%%3A00%%3A00') END=$(date -u '+%Y-%m-%d+23%%3A59%%3A59') curl -s -H "Authorization: Bearer $ONLYFANSAPI_API_KEY" \ "https://app.onlyfansapi.com/api/{account_id}/statistics/statements/earnings?start_date=$START&end_date=$END&type=total" | jq . Response fields: data.total โ net earnings data.gross โ gross earnings data.chartAmount โ daily earnings breakdown array data.delta โ percentage change vs. prior period Summarize: Present a table of each model's display name, username, net revenue, and gross revenue. Sum the totals.
Use the same workflow as above. Rank models by data.total (net earnings) descending. The model with the highest value is the best performer. Optionally also pull the statistics overview for richer context: curl -s -H "Authorization: Bearer $ONLYFANSAPI_API_KEY" \ "https://app.onlyfansapi.com/api/{account_id}/statistics/overview?start_date=$START&end_date=$END" | jq . This adds subscriber counts, visitor stats, post/message earnings breakdown.
List free trial links: curl -s -H "Authorization: Bearer $ONLYFANSAPI_API_KEY" \ "https://app.onlyfansapi.com/api/{account_id}/trial-links?limit=100&offset=0&sort=desc&field=subscribe_counts&synchronous=true" | jq . Key response fields per link: id, trialLinkName, url claimCounts โ total subscribers who claimed the trial clicksCounts โ total clicks revenue.total โ total revenue from this link revenue.spendersCount โ number of subscribers who spent money revenue.revenuePerSubscriber โ average revenue per subscriber Calculate conversion rate: conversion_rate = spendersCount / claimCounts Rank links by conversion rate descending. Present results as a table: link name, claims, spenders, conversion rate, total revenue.
List tracking links: curl -s -H "Authorization: Bearer $ONLYFANSAPI_API_KEY" \ "https://app.onlyfansapi.com/api/{account_id}/tracking-links?limit=100&offset=0&sort=desc&sortby=claims&synchronous=true" | jq . Key response fields per link: id, campaignName, campaignUrl subscribersCount โ total subscribers from this link clicksCount โ total clicks revenue.total โ total revenue revenue.spendersCount โ subscribers who spent revenue.revenuePerSubscriber โ avg revenue per subscriber revenue.revenuePerClick โ avg revenue per click Calculate conversion rate: conversion_rate = revenue.spendersCount / subscribersCount Present results as a table: campaign name, subscribers, spenders, conversion rate, total revenue, revenue per subscriber.
Use the same listing endpoints above. Sort by revenue.total descending. Present the top links with their name, type (trial vs. tracking), total revenue, and subscriber/spender counts.
For agency-level queries that span all models, always: First fetch all accounts via GET /api/accounts Loop through each account and gather the relevant data Aggregate and present combined results with per-model breakdowns
When querying GET /api/{account}/statistics/statements/earnings, the type parameter filters by category: total โ all earnings combined subscribes โ subscription revenue tips โ tips received post โ paid post revenue messages โ paid message revenue stream โ stream revenue
If you are unsure about an endpoint, parameter, response format, or how to accomplish a specific task with the OnlyFans API, consult the official documentation at https://docs.onlyfansapi.com. The site contains full API reference details, guides, and examples for all available endpoints. Always check the docs before guessing.
If ONLYFANSAPI_API_KEY is not set, stop and ask the user to configure it. If an API call returns a non-200 status, show the error message and HTTP status code. If _meta._rate_limits.remaining_minute or remaining_day is 0, warn the user about rate limits. If an account has "is_authenticated": false, note that the account needs re-authentication.
Always present data in markdown tables for readability. Include currency values formatted to 2 decimal places. When showing percentages (conversion rates, deltas), format as XX.X%. For multi-model summaries, include a Total row at the bottom.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.