Install
openclaw skills install rising-transfers-dna-finderFind cheaper, style-matched footballer alternatives using Rising Transfers vector DNA search
openclaw skills install rising-transfers-dna-finderFind statistically similar footballers at lower market values. Powered by the Rising Transfers Intelligence API using pgvector cosine similarity across 2,000+ player profiles.
| Endpoint | Method | Data Sent | Purpose |
|---|---|---|---|
https://api.risingtransfers.com/api/v1/intelligence/dna-search | POST | { "name": "<player_name>" } | DNA vector similarity search |
https://api.risingtransfers.com/api/v1/intelligence/player | POST | { "name": "<player_name>" } | Player profile lookup (optional enrichment) |
No data is sent to any other endpoint. No data is stored locally.
RT_API_KEY is sent as X-RT-API-Key header on every request to api.risingtransfers.com onlyThis skill may be invoked autonomously by OpenClaw when you ask about finding similar players, cheaper alternatives, or DNA-matched footballers. You can disable autonomous invocation by setting skill.auto-discover false in your OpenClaw config. Every API call consumes credits from your Rising Transfers account (10 credits per DNA search).
By using this skill, the player name you query is sent to Rising Transfers (api.risingtransfers.com). Only install this skill if you trust Rising Transfers with that information. Rising Transfers is a football intelligence platform — no financial, personal, or sensitive data is involved in these queries.
When the user asks to:
Examples:
Extract the target player name from the user's request. If a team is mentioned, note it for disambiguation.
Call the DNA search endpoint:
POST https://api.risingtransfers.com/api/v1/intelligence/dna-search
Headers:
X-RT-API-Key: <RT_API_KEY>
Content-Type: application/json
Body:
{ "name": "<player_name>", "team": "<team_name_if_provided>" }
If the response contains error: "INSUFFICIENT_CREDITS", inform the user their Rising Transfers credits are exhausted and direct them to api.risingtransfers.com to top up.
If the response contains error: "PLAYER_NOT_FOUND", ask the user to clarify the player name or provide the current club.
Parse the data.alternatives array from the response. For each alternative player, present:
Present results as a ranked table, most similar first. Example format:
| Rank | Player | Club | Similarity | Value | Saving vs [Target] |
|---|---|---|---|---|---|
| 1 | Name | Club | 91% | €15M | €65M cheaper |
After the table, offer to dive deeper: "Want a full scout report on any of these players?"
Do not fabricate statistics. If the API returns no alternatives, say so clearly and suggest the user try a different player.
| Error | User Message |
|---|---|
| 401 Unauthorized | "Your RT_API_KEY is invalid or expired. Get a key at api.risingtransfers.com" |
| 403 Insufficient Credits | "You've used all your DNA search credits. Top up at api.risingtransfers.com" |
| 404 Player Not Found | "Player not found. Try the full name (e.g. 'Jude Bellingham') or add the club name." |
| 429 Rate Limited | "Too many requests. Please wait a moment before trying again." |
| 5xx Server Error | "Rising Transfers API is temporarily unavailable. Please try again in a few minutes." |
api.risingtransfers.com)| Action | Credits Consumed |
|---|---|
| DNA similarity search | 10 credits |
| Player profile enrichment (optional) | 1 credit |
Free tier: 2 DNA searches/day (20 credits/day total for this skill). Pro tier ($29/mo): 50 DNA searches/day.
risingtransfers — api.risingtransfers.com