PairDesk Builder
An open toolbox your Grok bot or Claude Code — any capable AI agent — uses to build a pair trading dashboard, journal, screener or pairs desk from templates. Parts, blueprints and statistical functions that bolt onto one local database: your bot, your build, your data, your machine.
Statistical research only, not investment advice. General information. Does not consider your objectives, financial situation or needs.
What a build looks like
Two of the shipped blueprints, assembled: the hero pair page and the watch book. Every blueprint is an executable spec — region map, state table, bindings and acceptance checks — so your bot can build it, check it, and restyle it. The captures on this page are template mock-ups on synthetic data.
What's on the shelves
Parts, not a product. Your bot shops the manifest and bolts together exactly what you asked for — a journal, a research station, a monitoring dashboard, a test desk — nothing more.
- Start Here — The front door: manifest, bot rules, build recipes, starter prompts. Your bot reads this first, always.
- The Spine — One local SQLite database every part speaks. If it doesn't speak the Spine, it doesn't bolt on.
- Feeds — Plug in any market — PairSync derived data (keyed), worldwide daily pulls, CSV. One contract, adapter-blind downstream.
- The Math Desk — Pure statistical functions: cointegration, OU fitting, z-scores, spread candles. Numbers in, numbers out, nothing decided.
- The Engine-Room — Fetch → store → compute → notify, once per market close. Calendar-aware freshness. Boring on purpose.
- The Blueprints — The pages as executable specs — hero pair page, watch book, journal, pair cards — with acceptance checks. Skin is yours.
- The Screener — Ships assembled: statistical composite, half-life, Hurst, spread vol and live z across a whole universe, with named hooks for your own bolt-ons.
- The Test Desk — Arm a condition, then watch a crossing build, send and track a real order — on a test network or broker paper account, over your own data.
- The Gatehouse — Proof routines: settlement checks, reconciliation, freshness asserts. The bot never rewrites a gate.
Two ways to run it
Every part declares which targets it supports; nothing assumes one. The choice is a deployment tradeoff, nothing else.
- In your Grok bot's workspace — Zero install; the build lives where your bot lives, viewed in the browser there. Routine-based scheduling suited to a once-daily statistical cadence.
- On your own machine — Assembled by Claude Code, Grok Build or any coding agent you run locally. Persistent local SQLite and a real scheduler; records never leave the machine. Supports higher observation cadence, at the cost of install and upkeep.
The data that fills it
All the code is free and open. What makes a build come alive is PairSync's nightly refit output — ranked pairs, diagnostics, fitted statistical levels — delivered once per market close through the keyed PairSync API. Every account includes a free key with 100 calls, no card.
No key? Every part still works — from your own CSVs or daily worldwide pulls — and live columns show an honest "—" instead of a number. See also the MCP connector for conversational access to the same statistics.
Frequently asked questions
Can my Grok bot build a pair trading dashboard with this?
Yes — that is what the toolbox is for. Point your bot at the repo: it reads the manifest and the bench rules, picks a recipe, and assembles the parts into a dashboard over your own local database.
Is there a pair trading journal template?
Yes. The Logbook blueprint and the Record Book schema give you a journal keyed to pairs and positions, with append-only history. A journal-only build is one of the shipped recipes.
How do I build a pairs desk with Grok?
Hand your Grok bot the repo link and a starter prompt from the guidance shelf. It works through the manifest — spine, feeds, statistics, blueprints — and asks you the build questions as it goes.
Can Claude Code build a pair trading desk with this?
Yes — the toolbox is agent-agnostic. Point Claude Code (or Grok Build, or any capable coding agent) at the repo's manifest and hand it a starter prompt; the bench rules read the same for every agent, and the verification gates prove the build.
Do I need a PairSync subscription?
No. The toolbox is free and open source under Apache-2.0, and every PairSync account includes a free API key with 100 calls — no card. Without a key, every part still works from CSV or daily Yahoo pulls, with live columns showing "—".
Does PairDesk Builder place trades?
PairSync publishes research data and does not execute trades. The toolbox's Test Desk connects to test networks and broker paper accounts only.