Bet Angel Guardian Explained: Automation Setup for Betfair (2026)

Why Guardian Matters for UK Betfair Traders

Manual ladder trading works until you are juggling six horse races, three football matches and a tennis tie-break at the same time. Miss one price trigger and a planned scalp becomes an accidental hold into the off. Guardian exists so Bet Angel traders can monitor many markets from one command centre and let software execute rules they would otherwise click by hand.

Unlike a dedicated bot platform, Guardian lives inside a full trading terminal. You can scalp manually on one ladder while Guardian handles pre-race entries on a Watch List two screens over. That hybrid model suits traders who want discretion on some markets and iron discipline on others — without maintaining two separate applications.

This guide translates the official Bet Angel manual into a practical automation workflow for UK exchange traders. For pricing, charting and ladder depth, start with our Bet Angel review. For football in-play context, see in-play football guide.

Step-by-Step: Guardian Setup

Work through these steps in order. Skipping session limits or simulation is the most common reason new Guardian users blow through a bank in a single Saturday card.

1. Install and connect — download from betangel.com/trial, log into Betfair, confirm API status is green.
2. Complete ladder basics — stake presets, one-click settings and shortcuts per ladder trading setup.
3. Open Guardian — from the main menu; dock it beside your primary ladder workspace.
4. Load markets — use Market Finder or import from an open market; add to a new or existing Watch List.
5. Set session stop-loss — define max loss in pounds for this Guardian session before any rules fire.
6. Create a simple rule — e.g. "5 minutes before off, if back price < 4.0 and volume > £500, back £10".
7. Attach a Servant — link exit Servant: lay at entry minus 2 ticks, or time exit 60 seconds before off.
8. Run simulation — Bet Angel simulation mode uses live prices without sending real bets; log 20+ scenarios.
9. Go live at minimum stakes — one Watch List, one rule chain; expand only after a full session review.

Model lay liability before any lay Servant with our lay liability calculator. For tick-based stops, use the stop-loss tick calculator to translate ticks into pounds.

Watch Lists: Organising Multi-Market Sessions

A Watch List is Guardian's filing system. Instead of hunting through Market Finder every time a race goes in-play, you pre-load everything you intend to trade and let Guardian refresh prices on a schedule.

Practical Watch List layouts

• UK horses — next hour — all Win markets starting within 60 minutes at tracks you follow.
• Premier League — kick-off window — Match Odds for today's fixtures; separate list for in-play only.
• LTD session — football Match Odds filtered to leagues with liquid Draw markets; rules fire at kick-off.
• Tennis — live sets — Match Odds for ATP/WTA matches currently in-play; manual override on weak liquidity.

Name lists by strategy, not just sport. "Saturday scalps" beats "horses" when you return Monday and cannot remember which rules were attached.

Refresh and monitoring

Guardian can auto-refresh Watch List markets on an interval you define. Tighter refresh burns API calls; looser refresh misses fast steam. Pre-race horse scalping typically needs faster refresh than pre-kick-off football. If orders fail to submit, check Betfair API status before blaming your rules.

Aggregate P&L across the Watch List gives session-level visibility — essential when five small greens and one bad drift net to a loss you would not spot on a single ladder.

Triggered Betting and Servants

Triggered betting is Guardian's conditional engine. You define when something should happen (time to off, odds threshold, traded volume, in-play flag) and what should happen (back, lay, cancel, hedge). Servants are the reusable actions triggered rules call.

Common trigger types

Servant chains

Real strategies rarely stop at one bet. A pre-race scalp Servant chain might look like:

1. Entry Servant — back favourite at market if conditions pass.
2. Profit Servant — lay 2 ticks better when price shortens.
3. Stop Servant — lay 5 ticks worse if price drifts against you.
4. Time Servant — cancel all unmatched 90 seconds before off.

Servants you build once can attach to multiple Watch Lists. Document each Servant's purpose in a spreadsheet — Guardian's flexibility becomes a liability when you forget which list calls which exit.

Stuck on Servant syntax or Guardian columns? Ask Bob indexes the Bet Angel user guide and can cite the relevant manual section.

Lay the Draw Automation Frame

Lay the Draw is the strategy Guardian users ask about most. The frame below is a starting template — adjust stakes, minutes and price bands to your bankroll and league set.

LTD Guardian workflow

1. Add today's Match Odds markets to an LTD Watch List (filter by league liquidity).
2. Entry rule — at kick-off (or T−2 min), lay Draw at best available or at a minimum price (e.g. 3.25+).
3. Goal Servant — on in-play goal detection or Draw price lengthening past target, invoke green-up Servant.
4. Time stop — if no goal by minute 75 (or your cut-off), trade out at market to cap liability.
5. Session cap — Guardian session stop-loss; e.g. −£50 on a £2,000 bank.

Model hedge stakes with our green-up calculator before you hard-code Servant prices. LTD without a time stop is a systematic loser on many league samples — see our full LTD guide for the statistics.

If you want the same rules running while you sleep, BF Bot Manager is the more common UK choice for unattended LTD — Guardian suits traders who watch matches and want automation as a safety net.

Session Stops and Bankroll Protection

Guardian will execute every rule you enable until a limit blocks it. Session stop-loss is non-negotiable:

• Set a maximum session loss in pounds before the first market loads.
• Optionally set per-market loss caps on volatile in-play football.
• Define a profit lock — stop new entries after +£X if you tend to give back afternoon gains.
• Write the same numbers on paper above your monitor; software limits only work if you do not override them.

Use our stop-loss tick calculator and bankroll risk calculator on calm mornings, not mid-session after a red card goes against you.

Guardian vs BF Bot Manager

Both automate Betfair rules. The difference is product shape and typical UK use case.

Full head-to-head: BF Bot Manager vs Bet Angel. Running both on one Betfair account is possible but respect the two API connection limit — pick one primary automation engine per session.

Guardian vs Geeks Toy OCO

Geeks Toy OCO links two orders: when one matches, the other cancels. It is fast to configure for simple profit/stop pairs on a single ladder. Guardian handles broader logic:

• OCO (Geeks Toy) — one runner, two legs, manual ladder context; ideal for tick scalps.
• Guardian — many markets, nested time + price + volume rules; ideal for Saturday cards and LTD lists.
• Green-up — Geeks Toy binds a greener shortcut for instant hedge; Guardian uses Servants on P&L or price triggers.
• Learning curve — OCO is minutes; Guardian rewards an afternoon reading the manual.

Many UK football traders live on Geeks Toy ladders for speed and move to Guardian or BFBM stop-loss rules once logic outgrows a two-leg OCO pair.

Worked Example: Pre-Race Horse Scalp

Scenario: back the favourite on a competitive 8-furlong handicap when steam appears five minutes before the off, exit on a 2-tick profit or 4-tick stop, flat stakes.

1. 08:55 — market added to "UK scalps" Watch List; Guardian refresh every 2 seconds.
2. Entry trigger — T−5:00, if back price < 3.80 and traded volume > £1,500, Servant backs £15.
3. Profit Servant — when back price ≤ 3.70 (2 ticks), lay £15 to lock green.
4. Stop Servant — when back price ≥ 4.00 (4 ticks against), lay to cap loss — stakes checked in stop-loss tick calculator.
5. Time exit — T−1:00, cancel all unmatched; if still exposed, market lay via Servant.
6. Session rule — stop new entries if Watch List P&L ≤ −£40.

Log slippage vs simulation. Thin races at smaller tracks slip more than Guardian's Training scenarios suggest. After 30 logged trades, tighten or widen stops based on data, not frustration.

Common Guardian Mistakes

• No session stop before loading markets — one bad rule chain can fire across an entire Watch List.
• Overlapping Servants — profit and stop Servants both firing creates duplicate lays; test cancel logic in simulation.
• Refresh too slow on steam races — triggers miss the window; tighten refresh or narrow the Watch List.
• Ignoring non-runners — adjust exposure when horses are withdrawn; stale rules can back wrong prices.
• Scaling before logging — add markets only after 20+ reviewed trades on one list.
• Two automation tools, one account — BFBM on VPS plus Guardian without a clear split causes missed bets and API conflicts.
• Lay stakes without liability check — Servant lays at £20 stake ≠ £20 risk; use the liability calculator.

Key Takeaways

Related Guides

• Bet Angel ladder setup
• Bet Angel in-play football
• Bet Angel review
• BF Bot Manager hub
• Lay the Draw strategy
• Stop-loss tick calculator
• Green-up calculator
• Ask Bob — Bet Angel manual Q&A

Disclaimer: Betting involves risk. Educational content only — not financial advice. Automation does not guarantee profit; test in simulation and trade within your means.