This skill should be used when the user asks to "connect to Trading 212", "authenticate Trading 212 API", "place a trade", "buy stock", "sell shares", "place market order",, "place pending order"…
Install the "trading212-api" agent skill from https://github.com/trading212-labs/agent-skills/tree/master/plugins/trading212-api/skills/trading212-api into .claude/skills/trading212-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trading212-api", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add trading212-labs/agent-skills --skill trading212-api -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "trading212-api" agent skill from https://github.com/trading212-labs/agent-skills/tree/master/plugins/trading212-api/skills/trading212-api into .agents/skills/trading212-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trading212-api", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add trading212-labs/agent-skills --skill trading212-api -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "trading212-api" agent skill from https://github.com/trading212-labs/agent-skills/tree/master/plugins/trading212-api/skills/trading212-api into .cursor/skills/trading212-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trading212-api", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add trading212-labs/agent-skills --skill trading212-api -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "trading212-api" agent skill from https://github.com/trading212-labs/agent-skills/tree/master/plugins/trading212-api/skills/trading212-api into .gemini/skills/trading212-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trading212-api", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add trading212-labs/agent-skills --skill trading212-api -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "trading212-api" agent skill from https://github.com/trading212-labs/agent-skills/tree/master/plugins/trading212-api/skills/trading212-api into .github/skills/trading212-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trading212-api", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add trading212-labs/agent-skills --skill trading212-api -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "trading212-api" agent skill from https://github.com/trading212-labs/agent-skills/tree/master/plugins/trading212-api/skills/trading212-api into .opencode/skills/trading212-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trading212-api", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
trading212-api
GitHub stars
129
Token cost
~11k tokens
SKILL.md length
2,566 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT
At a glance
This skill should be used when the user asks to "connect to Trading 212", "authenticate Trading 212 API", "place a trade", "buy stock", "sell shares", "place market order",, "place pending order"…
Works in 2 steps: You're using the correct API key for the… → The API key was generated in the same…
Asks to connect to Trading 212
SKILL.md covers Quick Reference, Authentication, Account and Orders
Calls curl and jq; reaches demo.trading212.com and live.trading212.com; needs T212_API_KEY and T212_API_SECRET
What it does
Trading212 API is an agent skill from trading212-labs/agent-skills. This skill should be used when the user asks to "connect to Trading 212", "authenticate Trading 212 API", "place a trade", "buy stock", "sell shares", "place market order",, "place pending order", "place limit order", "cancel order", "check my balance", "view account summary", "get positions", "view portfolio", "check P&L", "find ticker symbol", "search instruments", "check trading hours", "view dividends", "get order history", "export transactions", "generate CSV report", or needs guidance on Trading 212 API…
Its SKILL.md is about 11k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Business, Finance & HR, covering Trading and backtesting, Codebase onboarding and Authentication. The repository describes itself as: ✨ Supercharge your AI agent with the power of the Trading 212 API. The licence is MIT.
When your agent uses it
Asks to connect to Trading 212
Authenticate Trading 212 API
Place market order
Place pending order
Example prompts
“connect to Trading 212”
“authenticate Trading 212 API”
“place a trade”
“/trading212-api”
Requirements
A credential in T212_API_KEY
A credential in T212_API_SECRET
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
1You're using the correct API key for the target environment
2The API key was generated in the same environment (LIVE or DEMO) you're trying to access
What it can do on your machine
Read from SKILL.md and the folder at commit edd9dc8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
curl
jq
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
demo.trading212.com
live.trading212.com
trading212-reports.s3.amazonaws.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
T212_API_KEY
T212_API_SECRET
API_KEY_ID
API_SECRET
DEMO_API_KEY_ID
DEMO_API_SECRET
LIVE_API_KEY_ID
LIVE_API_SECRET
DEMO_KEY_ID
DEMO_SECRET
LIVE_KEY_ID
LIVE_SECRET
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Trading212 API loads about 11k tokens when it runs. Until then it costs about 163 tokens; SKILL.md has 2,566 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~163
When it runs· the whole SKILL.md, loaded when a task matches
~11k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/trading212-api/SKILL.md (or your agent's skills folder).
name
trading212-api
description
This skill should be used when the user asks to "connect to Trading 212", "authenticate Trading 212 API", "place a trade", "buy stock", "sell shares", "place market order",, "place pending order", "place limit order", "cancel order", "check my balance", "view account summary", "get positions", "view portfolio", "check P&L", "find ticker symbol", "search instruments", "check trading hours", "view dividends", "get order history", "export transactions", "generate CSV report", or needs guidance on Trading 212 API authentication, order placement, position monitoring, account information, instrument lookup, or historical data retrieval.
license
MIT License
metadata.author
Trading 212
metadata.version
1.0.0
Trading 212 API
Note: The Trading 212 API is currently in beta and under active development. Some endpoints or behaviors may change.
Only Invest and Stocks ISA accounts are supported.
Instrument Identifiers
Trading 212 uses custom tickers as unique identifiers for instruments.
Always search for the Trading 212 ticker before making instrument requests.
Authentication
HTTP Basic Auth with API Key (username) and API Secret (password).
Check Existing Setup First
Before guiding the user through authentication setup, check if credentials are already configured:
Semantic rule: Credentials are configured when at least one complete set is present: a complete set is key + secret for the same account (e.g. T212_API_KEY + T212_API_SECRET, or T212_API_KEY_INVEST + T212_API_SECRET_INVEST, or T212_API_KEY_STOCKS_ISA + T212_API_SECRET_STOCKS_ISA). You do not need all four account-specific vars; having only the Invest pair or only the Stocks ISA pair is enough. Check for any combination that gives at least one usable key+secret pair.
bash
# Example: configured if any complete credential set exists
if [ -n "$T212_AUTH_HEADER" ] && [ -n "$T212_BASE_URL" ]; then
echo "Configured (derived vars)"
elif [ -n "$T212_API_KEY" ] && [ -n "$T212_API_SECRET" ]; then
echo "Configured (single account)"
elif [ -n "$T212_API_KEY_INVEST" ] && [ -n "$T212_API_SECRET_INVEST" ]; then
echo "Configured (Invest); Stocks ISA also if T212_API_KEY_STOCKS_ISA and T212_API_SECRET_STOCKS_ISA are set"
elif [ -n "$T212_API_KEY_STOCKS_ISA" ] && [ -n "$T212_API_SECRET_STOCKS_ISA" ]; then
echo "Configured (Stocks ISA); Invest also if T212_API_KEY_INVEST and T212_API_SECRET_INVEST are set"
else
echo "No complete credential set found"
fi
If any complete set is present, skip the full setup and proceed with API calls; when making requests, use the resolution order in "Making Requests" below (pick the pair that matches the user's account context when multiple sets exist). Do not ask the user to run derivation one-liners or merge keys into a header. Only guide users through the full setup process below when no complete credential set exists.
Important: Before making any API calls, always ask the user which environment they want to use: LIVE (real money) or DEMO (paper trading). Do not assume the environment.
API Keys Are Environment-Specific
API keys are tied to a specific environment and cannot be used across environments.
API Key Created In
Works With
Does NOT Work With
LIVE account
live.trading212.com
demo.trading212.com
DEMO account
demo.trading212.com
live.trading212.com
If you get a 401 error, verify that:
You're using the correct API key for the target environment
The API key was generated in the same environment (LIVE or DEMO) you're trying to access
Get Credentials
Decide which environment to use - LIVE (real money) or DEMO (paper trading)
Open Trading 212 app (mobile or web)
Switch to the correct account - Make sure you're in LIVE or DEMO mode matching your target environment
Navigate to Settings > API
Generate a new API key pair - you'll receive:
API Key (ID) (e.g., 35839398ZFVKUxpHzPiVsxKdOtZdaDJSrvyPF)
API Secret (e.g., 7MOzYJlVJgxoPjdZJCEH3fO9ee7A0NzLylFFD4-3tlo)
Store the credentials separately for each environment if you use both
Building the Auth Header
Combine your API Key (ID) and Secret with a colon, base64 encode, and prefix with Basic for the Authorization header.
Optional: To precompute the header from key/secret, you can set:
When making API calls, use the first option that applies (semantically: pick the credential set that matches the user's account, or the only set present):
If T212_AUTH_HEADER and T212_BASE_URL are set: use them in requests.
Else if T212_API_KEY and T212_API_SECRET are set: use this pair (single account). Build header as Basic $(echo -n "$T212_API_KEY:$T212_API_SECRET" | base64 -w 0) and base URL as https://${T212_ENV:-live}.trading212.com. Do not guide the user to derive or merge; you do it.
Else if both account-specific pairs are set (T212_API_KEY_INVEST/T212_API_SECRET_INVEST and T212_API_KEY_STOCKS_ISA/T212_API_SECRET_STOCKS_ISA): the user must clearly specify which account to target (Invest or Stocks ISA), unless they ask for information for all accounts. Use the Invest pair when the user refers to Invest, and the Stocks ISA pair when the user refers to ISA/Stocks ISA. If the user wants information for all accounts, make multiple API calls—one per account (Invest and Stocks ISA)—and present or aggregate the results for both. If it is not clear from context which account to use (and they did not ask for all accounts), ask for confirmation before making API calls (e.g. "Which account should I use — Invest or Stocks ISA?"). Do not assume. Build the header from the chosen key/secret and base URL as https://${T212_ENV:-live}.trading212.com.
Else if only the Invest pair is set (T212_API_KEY_INVEST and T212_API_SECRET_INVEST): use this pair for requests; if the user asks about Stocks ISA, only the Invest account is configured.
Else if only the Stocks ISA pair is set (T212_API_KEY_STOCKS_ISA and T212_API_SECRET_STOCKS_ISA): use this pair for requests; if the user asks about Invest, only the Stocks ISA account is configured.
Use the T212_AUTH_HEADER value in the Authorization header when it is set:
bash
# When T212_AUTH_HEADER and T212_BASE_URL are set:
curl -H "Authorization: $T212_AUTH_HEADER" \
"${T212_BASE_URL}/api/v0/equity/account/summary"
When only primary vars are set, use the inline form in the curl:
bash
# When only T212_API_KEY, T212_API_SECRET, T212_ENV are set:
curl -H "Authorization: Basic $(echo -n "$T212_API_KEY:$T212_API_SECRET" | base64 -w 0)" \
"https://${T212_ENV:-live}.trading212.com/api/v0/equity/account/summary"
Warning:T212_AUTH_HEADER must be the full header value including the Basic prefix.
bash
# WRONG - raw base64 without "Basic " prefix
curl -H "Authorization: <base64-only>" ... # This will NOT work!
# CORRECT - use T212_AUTH_HEADER (contains "Basic <base64>")
curl -H "Authorization: $T212_AUTH_HEADER" ... # This works
Environment Variables
Single account vs all accounts: API keys are for a single account. One key/secret pair (T212_API_KEY + T212_API_SECRET) = one account (Invest or Stocks ISA). To use all accounts (Invest and Stocks ISA), the user must set two sets of key/secret: T212_API_KEY_INVEST / T212_API_SECRET_INVEST and T212_API_KEY_STOCKS_ISA / T212_API_SECRET_STOCKS_ISA. When both pairs are set, the user must clearly specify which account to target; if it is not clear from context, ask for confirmation (Invest or Stocks ISA) before making API calls.
Primary (single account): Set these for consistent setup with the plugin README:
bash
export T212_API_KEY="your-api-key" # API Key (ID) from Trading 212
export T212_API_SECRET="your-api-secret"
export T212_ENV="demo" # or "live" (defaults to "live" if unset)
Account-specific (Invest and/or Stocks ISA): Set only the pair(s) you use. One complete set (key + secret for the same account) is enough. For example, only Invest:
bash
export T212_API_KEY_INVEST="your-invest-api-key"
export T212_API_SECRET_INVEST="your-invest-api-secret"
export T212_ENV="demo" # or "live"
For both accounts, set both pairs:
bash
export T212_API_KEY_INVEST="your-invest-api-key"
export T212_API_SECRET_INVEST="your-invest-api-secret"
export T212_API_KEY_STOCKS_ISA="your-stocks-isa-api-key"
export T212_API_SECRET_STOCKS_ISA="your-stocks-isa-api-secret"
export T212_ENV="demo" # or "live" (applies to both)
Optional – precomputed (for scripts or if the user prefers): The user can set the auth header and base URL from the primary vars, but they do not need to; when making API calls you (the agent) must build the header and base URL from primary vars if these are not set.
bash
# Build auth header and base URL from T212_API_KEY, T212_API_SECRET, T212_ENV
export T212_AUTH_HEADER="Basic $(echo -n "$T212_API_KEY:$T212_API_SECRET" | base64 -w 0)"
export T212_BASE_URL="https://${T212_ENV:-live}.trading212.com"
Alternative (manual): If you prefer not to store key/secret in env, set derived vars directly. Remember: API keys only work with their matching environment.
bash
# For DEMO (paper trading)
export T212_AUTH_HEADER="Basic $(echo -n "<DEMO_API_KEY_ID>:<DEMO_API_SECRET>" | base64 -w 0)"
export T212_BASE_URL="https://demo.trading212.com"
# For LIVE (real money) - generate separate credentials in LIVE account
# export T212_AUTH_HEADER="Basic $(echo -n "<LIVE_API_KEY_ID>:<LIVE_API_SECRET>" | base64 -w 0)"
# export T212_BASE_URL="https://live.trading212.com"
Tip: If you use both environments, use separate variable names:
Important: Always check quantityAvailableForTrading before placing sell orders.
Instruments
Ticker Lookup Workflow
When users reference instruments by common names (e.g., "SAP", "Apple", "AAPL"), you must look up the exact Trading 212 ticker before making any order, position, or historical data queries. Never construct ticker formats manually.
CACHE FIRST: Always check /tmp/t212_instruments.json before calling the API. The instruments endpoint has a 50-second rate limit and returns ~5MB. Only call the API if cache is missing or older than 1 hour.
Generic search: Match the user's search term in the three meaningful fields: ticker, name, or shortName. Use one variable (e.g. SEARCH_TERM) with test($q; "i") on each field so "TSLA", "Tesla", "TL0", etc. match efficiently. For regional filtering (e.g. "US stocks", "European SAP"), use the ISIN prefix (first 2 characters) for country code or currencyCode after the grep.
IMPORTANT: Never auto-select instruments. If multiple options exist, you are required to ask the user for their preference.
All historical endpoints use cursor-based pagination with nextPagePath.
Pagination Parameters
Parameter
Type
Default
Max
Description
limit
integer
20
50
Items per page
cursor
string/number
-
-
Pagination cursor (used in nextPagePath)
ticker
string
-
-
Filter by ticker (orders, dividends)
time
datetime
-
-
Pagination time (used in nextPagePath for transactions)
Pagination Example
bash
#!/bin/bash
# Fetch all historical orders with pagination
NEXT_PATH="/api/v0/equity/history/orders?limit=50"
while [ -n "$NEXT_PATH" ]; do
echo "Fetching: $NEXT_PATH"
RESPONSE=$(curl -s -H "Authorization: $T212_AUTH_HEADER" \
"$T212_BASE_URL$NEXT_PATH")
# Process items (e.g., save to file)
echo "$RESPONSE" | jq '.items[]' >> orders.json
# Get next page path (null if no more pages)
NEXT_PATH=$(echo "$RESPONSE" | jq -r '.nextPagePath // empty')
# Wait 1 second between requests (50 req/min limit)
if [ -n "$NEXT_PATH" ]; then
sleep 1
fi
done
echo "Done fetching all orders"
# Get the download link from the response
DOWNLOAD_URL=$(curl -s -H "Authorization: $T212_AUTH_HEADER" \
"$T212_BASE_URL/api/v0/equity/history/exports" | jq -r '.[0].downloadLink')
# Download the CSV file
curl -o trading212_report.csv "$DOWNLOAD_URL"
Report Status Values
Status
Description
Queued
Report request received
Processing
Report generation started
Running
Report actively generating
Finished
Complete - downloadLink available
Canceled
Report cancelled
Failed
Generation failed
Pre-Order Validation
Before BUY - Check Available Funds
bash
#!/bin/bash
# Validate funds before placing a buy order
TICKER="AAPL_US_EQ"
QUANTITY=10
ESTIMATED_PRICE=185.00
ESTIMATED_COST=$(echo "$QUANTITY * $ESTIMATED_PRICE" | bc)
# Get available funds
AVAILABLE=$(curl -s -H "Authorization: $T212_AUTH_HEADER" \
"$T212_BASE_URL/api/v0/equity/account/summary" | jq '.cash.availableToTrade')
echo "Estimated cost: $ESTIMATED_COST"
echo "Available funds: $AVAILABLE"
if (( $(echo "$ESTIMATED_COST > $AVAILABLE" | bc -l) )); then
echo "ERROR: Insufficient funds"
exit 1
fi
echo "OK: Funds available, proceeding with order"
Before SELL - Check Available Shares
bash
#!/bin/bash
# Validate position before placing a sell order
TICKER="AAPL_US_EQ"
SELL_QUANTITY=5
# Get position for the ticker
POSITION=$(curl -s -H "Authorization: $T212_AUTH_HEADER" \
"$T212_BASE_URL/api/v0/equity/positions?ticker=$TICKER")
AVAILABLE_QTY=$(echo "$POSITION" | jq '.[0].quantityAvailableForTrading // 0')
echo "Sell quantity: $SELL_QUANTITY"
echo "Available to sell: $AVAILABLE_QTY"
if (( $(echo "$SELL_QUANTITY > $AVAILABLE_QTY" | bc -l) )); then
echo "ERROR: Insufficient shares (some may be in pies)"
exit 1
fi
echo "OK: Shares available, proceeding with order"
Rate Limit Handling
Understanding Rate Limits
Rate limits are per-account, not per API key or IP address. If you have multiple applications using the same Trading 212 account, they share the same rate limit pool.
Response Headers
Every API response includes rate limit headers:
Header
Description
x-ratelimit-limit
Total requests allowed in period
x-ratelimit-period
Time period in seconds
x-ratelimit-remaining
Requests remaining
x-ratelimit-reset
Unix timestamp when limit resets
x-ratelimit-used
Requests already made
Avoid Burst Requests to avoid Rate Limiting
Do not send requests in bursts. Even if an endpoint allows 50 requests per minute, sending them all at once can trigger rate limiting and degrade performance.
Pace your requests evenly, for example, by making one call every 1.2 seconds, ensuring you always stay within the limit.
Bad approach (bursting):
bash
# DON'T DO THIS - sends all requests at once
for ticker in AAPL_US_EQ MSFT_US_EQ GOOGL_US_EQ; do
curl -H "Authorization: $T212_AUTH_HEADER" \
"$T212_BASE_URL/api/v0/equity/positions?ticker=$ticker" &
done
wait
Good approach (paced):
bash
# DO THIS - space requests evenly
for ticker in AAPL_US_EQ MSFT_US_EQ GOOGL_US_EQ; do
curl -H "Authorization: $T212_AUTH_HEADER" \
"$T212_BASE_URL/api/v0/equity/positions?ticker=$ticker"
sleep 1.2 # 1.2 second between requests for 50 req/m limit
done
Caching Strategy
For data that doesn't change frequently, cache locally to reduce API calls:
bash
#!/bin/bash
# Cache instruments list (changes rarely)
CACHE_FILE="/tmp/t212_instruments.json"
CACHE_MAX_AGE=3600 # 1 hour
if [ -f "$CACHE_FILE" ]; then
CACHE_AGE=$(($(date +%s) - $(stat -f %m "$CACHE_FILE")))
if [ "$CACHE_AGE" -lt "$CACHE_MAX_AGE" ]; then
cat "$CACHE_FILE"
exit 0
fi
fi
# Cache expired or doesn't exist - fetch fresh data
curl -s -H "Authorization: $T212_AUTH_HEADER" \
"$T212_BASE_URL/api/v0/equity/metadata/instruments" > "$CACHE_FILE"
cat "$CACHE_FILE"
Safety Guidelines
Test in demo first - Always validate workflows before live trading
Validate before ordering - Check funds (cash.availableToTrade) before buy, positions (quantityAvailableForTrading) before sell
Confirm destructive actions - Order placement and cancellation are irreversible
API is not idempotent - Duplicate requests may create duplicate orders
Never log credentials - Use environment variables
Respect rate limits - Space requests evenly, never burst
Max 50 pending orders - Per ticker, per account
Cache metadata - Instruments and exchanges change rarely
Trading212 API next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Trading212 API compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Trading212 API this skilltrading212-labs/agent-skills
A skill your agent uses when an agent needs to register a Superior Trade account, verify an email OTP, configure x-api-key authentication, or recover from missing or invalid credentials before using…
A skill your agent uses when the user asks anything about blockchain wallets, transactions, signing, token transfers, supported chains, wallet balances, perpetual futures trading, prediction…
基于东方财富数据库,支持通过自然语言输入筛选A港美股、基金、债券等多种资产,支持多元指标筛选,含技术面、消息面、基本面及市场情绪等,可用于全球资产速筛、跨市场监控、投资组合构建、策略回测等场景。返回结果包含数据说明及 csv 文件。Natural language screener for investment assets across global markets, including…
This skill should be used when the user asks to "connect to Trading 212", "authenticate Trading 212 API", "place a trade", "buy stock", "sell shares", "place market order",, "place pending order"…. Trading212 API is an agent skill from trading212-labs/agent-skills.
When should I use Trading212 API?
Trading212 API fits situations like: asks to connect to Trading 212; authenticate Trading 212 API; place market order; place pending order.
How do I install Trading212 API in Claude Code?
Run `npx skills add trading212-labs/agent-skills --skill trading212-api -a claude-code`. Or copy the skill folder (plugins/trading212-api/skills/trading212-api in trading212-labs/agent-skills) into .claude/skills/trading212-api in your project. Claude Code loads it when a task matches its description.
How do I install Trading212 API in Codex?
Run `npx skills add trading212-labs/agent-skills --skill trading212-api -a codex`. Or copy the skill folder (plugins/trading212-api/skills/trading212-api in trading212-labs/agent-skills) into .agents/skills/trading212-api in your project. Codex loads it when a task matches its description.
Can I use Trading212 API in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add trading212-labs/agent-skills --skill trading212-api -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/trading212-api, .gemini/skills/trading212-api, .github/skills/trading212-api and .opencode/skills/trading212-api in your project.
What does Trading212 API need to run?
Going by SKILL.md and its folder, Trading212 API needs the command-line tools its instructions call (curl and jq) and credentials named T212_API_KEY, T212_API_SECRET, API_KEY_ID and API_SECRET. Our summary lists: A credential in T212_API_KEY; A credential in T212_API_SECRET.
Does Trading212 API access the network?
SKILL.md names 3 domains. In commands or code: demo.trading212.com, live.trading212.com and trading212-reports.s3.amazonaws.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Trading212 API safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Trading212 API use?
Trading212 API is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Trading212 API use?
About 11k tokens (SKILL.md is roughly 43k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Trading212 API?
Skills that share tags, products or a category with Trading212 API: Regime (jackson-video-resources/markov-hedge-fund-method, 484 stars), Superior Trade Auth (Superior-Trade/superior-skills, 215 stars), Metamask Agent Wallet (nirholas/three.ws, 230 stars) and Mx Stocks Screener (hiboys/ExploreFinance, 365 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Trading212 API?
trading212-labs (a GitHub organization) maintains it in trading212-labs/agent-skills, which has 129 GitHub stars. The repository was last updated on September 8, 2026.
Source: trading212-labs/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.