OSD Auto Edge (BB)
Core automation script. Required for all OSD workflows.
Tampermonkey Setup — install order: Auto Edge first, then helpers
All script links are hosted on this tools site for direct install & updates. Use Google Chrome.
- Install the Tampermonkey Beta browser extension (Chrome required — beta tracks the latest fix CRX).
- Install OSD Auto Edge (BB) first (required).
- Install one or more bet helpers based on your books.
- In Tampermonkey Settings, set Userscript Update → Check Interval to Always or Every Day.
- Configure OSD Auto Edge (email/password, OSD API key, Kalshi keys).
- Configure each bet helper (auto-login credentials per book).
Userscripts 07
BetMGM Helper
Autofill & execution helper for BetMGM.
Caesars Helper
Autofill & execution helper for Caesars.
DraftKings Helper
Autofill & execution helper for DraftKings.
FanDuel Helper
Autofill & execution helper for FanDuel.
HardRock Helper
Autofill & execution helper for HardRock.
Kalshi Helper
Autofill & execution helper for Kalshi.
ProphetX Helper
Autofill & execution helper for ProphetX — places limit orders in the new-tab betslip popup.
OSD Tail Router
Routes captured picks to the best-priced supported book via BookieBeats. Kill-switch + caps gated.
Juice Reel Sync
Runs on Juice Reel — auto-settles your OSD positions from your settled bets hourly. Set JR + OSD credentials in the helper's Settings panel after installing.
Configure OSD Auto Edge
Auto Edge configuration lives in the Tampermonkey toolbar menu — there is no in-page banner. Open it from any tab where the script is active (the easiest is bookiebeats.com):
- Click the Tampermonkey extension icon in the Chrome toolbar (top-right, next to the address bar). If it's hidden, click the puzzle-piece Extensions icon and pin Tampermonkey.
- The dropdown shows two OSD entries (alongside enable/disable toggles):
- 🔑 OSD Settings — Bookie Beats login + OSD Remote API credentials.
- ⚡ Kalshi API Settings — Kalshi key pair for direct (or hybrid) placement.
- Click an entry — a small popup window opens. Fill in the fields, click Save, then close the popup.
🔑 OSD Settings
Used for Bookie Beats auto-login (so the orchestrator doesn't go offline when BB logs you out) and for the userscript ↔ tools-site sync.
| Field | What to enter | Where to find it |
|---|---|---|
| Email Address | Your Bookie Beats login email. | The email you use at bookiebeats.com. |
| Password | Your Bookie Beats password. | Stored locally in Tampermonkey only — never sent off-device except to the BB login form itself. |
| User ID (Remote API) | Your OSD user id (e.g. fullerbra). |
Sign in at tools.orionsoftwaredev.com/login — your user id is shown on the Account panel. |
| API Key (Remote API) | Your OSD API key — starts with osd_… |
Same page (/login) → Keys panel → click Show to reveal, then Copy. Use Regenerate key if you ever need to rotate it. |
⚡ Kalshi API Settings
Only needed if you want to place Kalshi bets directly via the Kalshi REST API (faster fill, no browser tab required). You can skip this and use Helper mode if you only ever place Kalshi bets through the browser helper.
| Field | What to enter | Where to find it |
|---|---|---|
| API Key ID | The Kalshi-issued key id (a UUID). | kalshi.com → Account → Profile → API Keys → Create new key. Copy the Key ID. |
| Private Key (PEM) | The matching RSA private key block, including the -----BEGIN RSA PRIVATE KEY----- / -----END RSA PRIVATE KEY----- lines. |
Downloaded once at key-creation time on the same Kalshi page (Kalshi will not let you re-download it — save it somewhere safe). Paste the whole file content into the textarea. |
| Placement Mode |
Helper — browser tab places bets (default, safest). API — direct REST placement, no browser. Both — parallel test (use once to compare results, then pick one). |
Start with Helper. Switch to API after you've used Test Connection below and confirmed it returns OK. |
| API Stake ($) | Per-bet stake when placing via API (not the helper). | Pick a small value (e.g. 1) until you've verified end-to-end placement. |
After saving, click Test Connection in the popup. A green ✅ confirms the key pair authenticates against Kalshi. If you get an error, regenerate the key on Kalshi and re-paste both fields.
Configure each bet helper
Every bet helper has the same configuration pattern. Repeat for each book whose helper you installed:
- Open the book's website in Chrome:
- Look for the OSD helper banner at the top of the page (a thin status strip that says something like "OSD helper — standby").
- If you don't see it, the helper isn't running on this domain. Confirm the script is installed and enabled in Tampermonkey, and that you're on the book's actual sportsbook page (not a marketing page).
- On the right edge of that banner, click the small gear icon (⚙). A settings panel slides open.
- Enter:
- Email / Username — your login for that book.
- Password — your password for that book.
- Test it. Log out of the book, then reload the page. The helper should auto-fill the login form and submit it within ~10s. If anything goes wrong it falls back to standby and you can sign in manually — no harm done.
FanDuel only: FanDuel will periodically (~every two weeks) require an SMS MFA code at login. When that happens, OSD will surface the prompt in the BB orchestrator and on the Tools page — enter the code there and the helper will pick it up automatically. No extra setup needed.
Credentials are stored in Tampermonkey's per-script storage on your machine only. They are never transmitted to OSD servers — the helper types them directly into the book's login form.