Blog
Notes on market data and bots
Product updates, rate-limit engineering, and how the Market Data API fits with the open-source nexrade stack. Written for people who ship trading bots, not for slide decks.
7 notes~22 min total
- 5 minPinnedContinue reading
For first-time bot developers (or anyone who has never been profitable)
Hard-earned advice from 13 years of trading and 10 years of building bots — edges, TA, AI strategies, Python vs Rust, and why simple EV+ systems beat holy grails.
bots · advice · trading
- 3 minLatestContinue reading
Market data is not the edge (but bad data will kill yours)
Clean feeds, rate limits, and multi-exchange plumbing do not print money — they stop you from lying to yourself while you search for EV+.
market-data · bots · engineering
- 4 minContinue reading
Position sizing for bot builders (the part people skip)
Why “all-in bots” die, how to think about size without fancy math, hard loss limits, and the difference between research size and production size.
trading · risk · bots
- 4 minContinue reading
How to know when a strategy is dead (and kill it)
Edges expire. Here is a practical kill checklist — expectancy after costs, regime change, drawdown rules, and why “one more tweak” is usually denial.
trading · strategy · risk
- 2 minContinue reading
nexrade-cache — Redis-compatible cache for trading bots (Windows, no WSL)
Run a Redis-protocol cache natively on Windows without WSL or Docker. Rust + RESP2/3, and why it is a better fit for local trading bots than shipping a full Redis install.
nexrade-cache · redis · windows
- 2 minContinue reading
Rate-limit bypass for multi-exchange bots
How nexrade_req + the Nexrade API keep public REST traffic under exchange IP ceilings without giving up your trading library.
engineering · rate-limits · nexrade
- 2 minContinue reading
Introducing the Nexrade Market Data API
Proxy-backed public crypto market data — allowlisted domains, plan rate limits, short cache, and how nexrade / nexrade-req fit in.
product · market-data · api