RT Transfer Intel — Football Transfer Intelligence
Get real-time transfer rumour data aggregated from multiple sources, with AI-powered credibility assessment. Free tier includes trending topics with no credits required.
External Endpoints
| Endpoint | Method | Data Sent | Purpose |
|---|
| INLINECODE0 | GET | None | Trending transfers (free, 0 credits) |
| INLINECODE1 |
POST |
{ "name": "<player_name>" } | Player transfer rumour detail (3 credits) |
|
https://api.risingtransfers.com/api/v1/intel/verify | GET |
?q=<player>+to+<club> | Truth Meter credibility score (1–5 credits) |
No data is sent to any other endpoint. No conversation history is transmitted.
Security & Privacy
- - What leaves your machine: Player name and/or club name from your query only
- What does NOT leave your machine: Conversation history, other skills, local files, or your API key value (sent as HTTP header only)
- Authentication:
RT_API_KEY is sent as X-RT-API-Key header to api.risingtransfers.com only - Hot topics (trending list) can be fetched without any API key at 0 credits
- Data retention: Query logs kept for rate limiting (max 24 hours). No personal data stored
Model Invocation Note
This skill may be invoked autonomously when you ask about transfer news, rumours, or whether a specific transfer is likely to happen. To disable autonomous invocation: claw config set skill.auto-discover false. Credit consumption applies only to authenticated (non-anonymous) calls for detailed intelligence.
Trust Statement
By using this skill, player and club names from your queries are sent to Rising Transfers (api.risingtransfers.com). Rising Transfers aggregates public transfer rumour data — no sensitive or personal information is involved. Only install this skill if you trust Rising Transfers with those search terms.
Trigger
When the user asks about:
- - Transfer rumours for a specific player or club
- Whether a transfer deal is likely or credible
- Latest hot transfer topics or trending deals
- Verifying if a transfer story is genuine
Examples:
- - "What are the latest transfer rumours for Mbappé?"
- "Is the Osimhen to Chelsea deal likely to happen?"
- "What are the hottest transfer stories right now?"
- "How credible is the Arsenal to Gyökeres link?"
Instructions
Step 1 — Determine query type
Identify which of three modes to use:
| User Intent | Mode | Credits |
|---|
| "What's trending?" / general hot topics | Hot Topics | 0 |
| Specific player rumours |
Transfer Detail | 3 |
| "How likely is [player] to [club]?" |
Truth Meter | 1–5 |
Mode A: Hot Topics (0 credits, no key required)
Call:
CODEBLOCK0
Present the top 10 results sorted by heat_score:
- - Player name → Destination club
- Heat level (🔥🔥🔥 = high, 🔥 = low)
- Last updated timestamp
Mode B: Transfer Detail (3 credits)
Call:
CODEBLOCK1
Present:
- - Sources citing the rumour (e.g. "Fabrizio Romano", "Sky Sports")
- Transfer probability estimate (%)
- Social media sentiment breakdown
- Timeline: when first reported, latest update
- Key facts: reported fee, contract length, competing clubs
Mode C: Truth Meter (1–5 credits)
Call:
CODEBLOCK2
Parse audit.score and audit.verdict, present as:
CODEBLOCK3
Include top evidence sources from evidence.top_sources.
Error Handling
| Error | User Message |
|---|
| 401 | "Your RTAPIKEY is invalid. Get one free at api.risingtransfers.com" |
| 403 Insufficient Credits |
"Not enough credits for this query. Top up at api.risingtransfers.com/pricing" |
| 404 Player Not Found | "Player not found. Try the full name or add the current club name." |
| 429 Rate Limited | "Rate limit reached. Wait a moment or upgrade your plan for higher limits." |
| 5xx | "Rising Transfers API is temporarily unavailable. Please try again shortly." |
Important: Do Not Fabricate
If the API returns no rumour data for a player, clearly state: "No active transfer rumours found for [player] in the Rising Transfers database." Do not invent rumour details or probability scores.
Requirements
- - RTAPIKEY: Rising Transfers API key. Register free at api.risingtransfers.com
- Hot Topics mode works without a key (anonymous, limited results)
- OpenClaw: v0.8.0 or later
- Network access: Required
Credit Usage
| Action | Credits |
|---|
| Hot Topics (trending list) | 0 — always free |
| Transfer Detail (specific player) |
3 credits |
| Truth Meter (credibility score) | 1 credit (anonymous) / 5 credits (full detail) |
Free tier: 10 hot-topic calls/day, 3 detailed queries/day.
Author
risingtransfers — api.risingtransfers.com
技能名称: rising-transfers-transfer-intel
详细描述:
RT Transfer Intel — 足球转会情报
获取从多个来源聚合的实时转会传闻数据，并附有AI驱动的可信度评估。免费层级包含热门话题，无需消耗积分。
外部端点
| 端点 | 方法 | 发送数据 | 用途 |
|---|
| https://api.risingtransfers.com/api/v1/intelligence/hot-topics | GET | 无 | 热门转会（免费，0积分） |
| https://api.risingtransfers.com/api/v1/intelligence/transfer |
POST | { name: <球员姓名> } | 球员转会传闻详情（3积分） |
| https://api.risingtransfers.com/api/v1/intel/verify | GET | ?q=<球员>+to+<俱乐部> | 真相计量器可信度评分（1–5积分） |
不会向任何其他端点发送数据。不会传输对话历史记录。
安全与隐私
- - 离开您设备的内容：仅包含您查询中的球员姓名和/或俱乐部名称
- 不会离开您设备的内容：对话历史记录、其他技能、本地文件或您的API密钥值（仅作为HTTP标头发送）
- 身份验证：RTAPIKEY 仅作为 X-RT-API-Key 标头发送到 api.risingtransfers.com
- 热门话题（趋势列表）可在无需API密钥的情况下以0积分获取
- 数据保留：查询日志仅用于速率限制（最长24小时）。不存储任何个人数据
模型调用说明
当您询问转会新闻、传闻或特定转会是否可能发生时，此技能可能会被自动调用。要禁用自动调用：claw config set skill.auto-discover false。积分消耗仅适用于经过身份验证（非匿名）的详细情报调用。
信任声明
使用此技能即表示，您查询中的球员和俱乐部名称将被发送至Rising Transfers（api.risingtransfers.com）。Rising Transfers聚合公开的转会传闻数据——不涉及任何敏感或个人信息。仅当您信任Rising Transfers处理这些搜索词时，才安装此技能。
触发条件
当用户询问以下内容时：
- - 特定球员或俱乐部的转会传闻
- 某笔转会交易是否可能或可信
- 最新的热门转会话题或趋势交易
- 验证某条转会消息是否真实
示例：
- - “姆巴佩的最新转会传闻是什么？”
- “奥斯梅恩转会切尔西的交易可能发生吗？”
- “目前最热门的转会故事是什么？”
- “阿森纳与哲凯赖什的传闻可信度如何？”
操作说明
第1步 — 确定查询类型
识别要使用的三种模式之一：
| 用户意图 | 模式 | 积分 |
|---|
| “有什么热门话题？”/ 一般热门话题 | 热门话题 | 0 |
| 特定球员传闻 |
转会详情 | 3 |
| “[球员]转会[俱乐部]的可能性有多大？” |
真相计量器 | 1–5 |
模式A：热门话题（0积分，无需密钥）
调用：
GET https://api.risingtransfers.com/api/v1/intelligence/hot-topics
标头：X-RT-API-Key: APIKEY> （免费话题可选）
按热度分数排序展示前10个结果：
- - 球员姓名 → 目标俱乐部
- 热度等级（🔥🔥🔥 = 高，🔥 = 低）
- 最后更新时间戳
模式B：转会详情（3积分）
调用：
POST https://api.risingtransfers.com/api/v1/intelligence/transfer
标头：
X-RT-API-Key: APIKEY>
Content-Type: application/json
请求体：{ name: <球员姓名>, team: <如提及的球队> }
展示：
- - 引用该传闻的消息来源（例如“法布里齐奥·罗马诺”、“天空体育”）
- 转会概率估计（%）
- 社交媒体情绪分析
- 时间线：首次报道时间、最新更新
- 关键事实：报道的转会费、合同年限、竞争俱乐部
模式C：真相计量器（1–5积分）
调用：
GET https://api.risingtransfers.com/api/v1/intel/verify?q=<球员>+to+<俱乐部>
标头：X-RT-API-Key: APIKEY>
解析 audit.score 和 audit.verdict，展示如下：
真相计量器：[球员] 转会至 [俱乐部]
评分：74/100 — 可能
━━━━━━━━━━━━━━━━━━━━━
来源权威性： 32/40
官方信号： 15/20
进展信号： 14/20
市场热度： 13/20
社区情绪： +3（多数人相信）
包含来自 evidence.top_sources 的主要证据来源。
错误处理
| 错误 | 用户提示信息 |
|---|
| 401 | “您的RTAPIKEY无效。请前往 api.risingtransfers.com 免费获取一个。” |
| 403 积分不足 |
“本次查询积分不足。请前往 api.risingtransfers.com/pricing 充值。” |
| 404 未找到球员 | “未找到该球员。请尝试使用全名或添加当前俱乐部名称。” |
| 429 速率限制 | “已达到速率限制。请稍候或升级您的套餐以获得更高限制。” |
| 5xx | “Rising Transfers API暂时不可用。请稍后重试。” |
重要提示：请勿捏造
如果API未返回某球员的传闻数据，请明确说明：“在Rising Transfers数据库中未找到[球员]的活跃转会传闻。” 请勿编造传闻详情或概率评分。
要求
- - RTAPIKEY：Rising Transfers API密钥。请前往 api.risingtransfers.com 免费注册
- 热门话题模式无需密钥即可使用（匿名，结果有限）
- OpenClaw：v0.8.0 或更高版本
- 网络访问：必需
积分使用
| 操作 | 积分 |
|---|
| 热门话题（趋势列表） | 0 — 始终免费 |
| 转会详情（特定球员） |
3积分 |
| 真相计量器（可信度评分） | 1积分（匿名）/ 5积分（完整详情） |
免费层级：每天10次热门话题调用，3次详细查询。
作者
risingtransfers — api.risingtransfers.com
