Build on Tradewink signals.
Claude-compatible MCP tools, REST API docs, and webhook delivery for signal automation.
MCP server
Ask Claude or another MCP client to read your watchlist, positions, and alerts, run AI analysis, and prepare paper orders that you confirm. Public plans are paper trading only.
Signals API
Fetch published signal objects with entry, stop, target, confidence, reasoning, and outcome status (Pro and Elite).
Webhooks
Send new signals, including exit alerts, into your own automations as signed webhook posts (paid plans).
Which key do I need?
| API | Host | Key | Where to get it | Plans |
|---|---|---|---|---|
| REST API (/v1/...) | tradewink.fly.dev | tw_<64 hex> | /apikey generate in Discord or POST /v1/api-keys | Pro and Elite |
| Signals API (/api/v1/signals...) | tradewink-signals.fly.dev | Signals API key | Signals dashboard: API keys page | Pro and Elite |
Using one key against the other API returns 401 or 403. Both APIs return {"ok": false, "error": ..., "code": ...} on failure; branch on code, not on the message. Both are in the API docs linked above.
Rate limits
REST API limits are per key over a 60-second sliding window (by default 120 requests a minute for read keys, 60 for trade, 30 for admin). Every authenticated /v1/ response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset (seconds until the oldest request leaves the window). A 429 (code: rate_limited) adds Retry-After with that same computed wait, so a client that overran by a second does not sleep a full minute. Limits are enforced per API instance.
Chart patterns (beta)
GET /v1/patterns/{ticker} and the get_chart_patterns MCP tool run rule-based chart and candlestick pattern detectors over daily bars and return each detected pattern with its direction, heuristic confidence and key levels. Read-only: the scan does not change signal scoring or place orders, and a detected pattern is not a forecast.