Real-time football transfer intelligence — rumours, credibility scores, and multi-source verification
Get real-time transfer rumour data aggregated from multiple sources, with AI-powered credibility assessment. Free tier includes trending topics with no credits required.
| Endpoint | Method | Data Sent | Purpose |
|---|---|---|---|
https://api.risingtransfers.com/api/v1/intelligence/hot-topics | GET | None | Trending transfers (free, 0 credits) |
https://api.risingtransfers.com/api/v1/intelligence/transfer | 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.
RT_API_KEY is sent as X-RT-API-Key header to api.risingtransfers.com onlyThis 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.
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.
When the user asks about:
Examples:
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 |
Call:
GET https://api.risingtransfers.com/api/v1/intelligence/hot-topics
Headers: X-RT-API-Key: <RT_API_KEY> (optional for free topics)
Present the top 10 results sorted by heat_score:
Call:
POST https://api.risingtransfers.com/api/v1/intelligence/transfer
Headers:
X-RT-API-Key: <RT_API_KEY>
Content-Type: application/json
Body: { "name": "<player_name>", "team": "<team_if_mentioned>" }
Present:
Call:
GET https://api.risingtransfers.com/api/v1/intel/verify?q=<player>+to+<club>
Headers: X-RT-API-Key: <RT_API_KEY>
Parse audit.score and audit.verdict, present as:
Truth Meter: [player] to [club]
Score: 74/100 — LIKELY
━━━━━━━━━━━━━━━━━━━━━
Source Authority: 32/40
Official Signals: 15/20
Progress Signals: 14/20
Market Heat: 13/20
Community Mood: +3 (mostly believe it)
Include top evidence sources from evidence.top_sources.
| Error | User Message |
|---|---|
| 401 | "Your RT_API_KEY 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." |
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.
| 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.
risingtransfers — api.risingtransfers.com
ZIP package — ready to use