Token导航 LogoToken导航TokenDH.com
开发敏感数据clawhub未标认证来源可访问clear审计提醒

onlyfans-apionlyfans API 文档

Agent Skill

用于辅助 API 设计、接口文档、请求响应结构和服务集成说明。它适合让 Agent 梳理 endpoint、生成 OpenAPI 草稿、检查字段命名、整理错误码或辅助前后端联调。使用时需要确认真实业务语义、鉴权方式、分页和错误处理规则;涉及生成接口文档时,应避免凭空补字段,最好从现有代码、schema 或接口样例中提取事实。

总安装

58,759

周安装

2,377

GitHub Stars

2

下载量

18,446
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:onlyfans-api(onlyfans API 文档)
来源仓库:https://github.com/martingalovic/onlyfans-api
安装命令:
openclaw skills install onlyfans-api
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install onlyfans-api

简介

通过 OnlyFansAPI.com 平台查询 OnlyFans 数据和分析。获取所有模型的收入摘要,确定表现最好的模型,分析免费试用和跟踪链接转化率,比较链接收入等等!当用户询问与 OnlyFans 相关的任何信息时使用。

SKILL.md

name
onlyfansapi-skill
description
>-
compatibility
Requires curl, jq, and network access to app.onlyfansapi.com
metadata
author
OnlyFansAPI.com
version
1.0
allowed-tools
Bash(curl:*) Bash(jq:*) Read

OnlyFans API Skill

This skill queries the OnlyFansAPI.com platform to answer questions about OnlyFans agency analytics — revenue, model performance, and link conversion metrics.

Prerequisites

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"

API Basics

  • 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.

Workflows

1. Get revenue of all models for the past N days

Steps:

  1. 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".

  1. 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

  1. Summarize: Present a table of each model's display name, username, net revenue, and gross revenue. Sum the totals.

2. Which model is performing the best

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.

3. Which Free Trial Link has the highest conversion rate (subscribers → spenders)

  1. 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

  1. Calculate conversion rate:
   conversion_rate = spendersCount / claimCounts

Rank links by conversion rate descending.

  1. Present results as a table: link name, claims, spenders, conversion rate, total revenue.

4. Which Tracking Link has the highest conversion rate

  1. 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

  1. Calculate conversion rate:
   conversion_rate = revenue.spendersCount / subscribersCount
  1. Present results as a table: campaign name, subscribers, spenders, conversion rate, total revenue, revenue per subscriber.

5. Which Free Trial / Tracking Link made the most money

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.

Multi-Account (Agency) Queries

For agency-level queries that span all models, always:

  1. First fetch all accounts via GET /api/accounts
  2. Loop through each account and gather the relevant data
  3. Aggregate and present combined results with per-model breakdowns

Earnings Type Filters

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

When In Doubt

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.

Error Handling

  • 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.

Output Formatting

  • 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.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

91.75%
按下载量换算16,924

安全审计

VirusTotal

可疑

ClawScan

可疑

Static analysis

未展示

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills