DC Network Data Services

Trainer / Yard Context API Understand what market support means for the yard behind the horse.

DC Network’s Trainer / Yard Context API analyses how individual trainers have historically performed when their runners receive defined levels of market support or drift.

Trainer Baseline Runs, Wins & Strike Rate
Support + Drift Probability-Point Bands
Uplift + A/E Performance Versus Baseline & Market
Timing Context Open → 1PM → Final
Product Overview

A market move means more when you know the yard behind it.

Two horses can receive identical market support, yet the historical meaning of that support may be completely different depending on the trainer.

Backed Runners

See how often the trainer wins when their runners receive progressively stronger levels of bookmaker support.

Drifting Runners

Measure what happens historically when the market moves against the trainer’s runners.

Market Movement Bands

Probability points — not misleading raw price percentages.

Market shifts are measured using changes in implied probability, allowing short-priced and bigger-priced runners to be compared on the same meaningful scale.

3pp+ Meaningful shift
5pp+ Clear support / drift
8pp+ Strong market move
12pp+ Major shift
15pp+ Extreme market move
Yard Performance Matrix

See how the yard responds at every move level.

Backed Performance Matrix

Shift Runs Wins SR% Uplift A/E
3pp+ 143 42 29.4% +10.9pp 0.82
5pp+ 101 32 31.7% +13.2pp 0.79
8pp+ 60 22 36.7% +18.2pp 0.80

Drift Performance Matrix

Shift Runs Wins SR% Uplift A/E
3pp+ 127 16 12.6% -5.9pp 0.77
5pp+ 87 13 14.9% -3.6pp 0.88
8pp+ 50 8 16.0% -2.5pp 0.82
Uplift = market-band strike rate minus the trainer’s overall baseline strike rate, expressed in percentage points.

A/E = actual winners divided by expected winners at SP. Above 1.00 indicates more winners than market expectation; below 1.00 indicates fewer.
Plain-English Interpretation

The numbers are also returned as usable context.

A customer does not need to interpret every line of the matrix. The API can return a simple summary alongside the structured data.

Support: The response identifies the strongest reliable support level, shows how far the strike rate rises, and states whether backing at 10am, 1pm or SP has historically been profitable.
Drift: The response identifies whether any drift level creates a serious, reliable warning. If none does, it says so plainly rather than forcing a conclusion from weak evidence.
Timing Intelligence

When the support arrives matters.

A 10pp move completed early in the day is not necessarily the same behavioural signal as a similar move that develops later.

Open → 1PM

Measures the trainer’s historical performance when support is established by the 1pm market point.

Open → Final

Measures the yard’s historical performance when the full pre-race market movement is assessed against the final Market Form price.

Example Customer Output

James Owen — in plain English

What a customer can receive from the Trainer Context API

Trainer / Yard Market Profile

Runs 1,119
Wins 188
Baseline SR 16.8%
Baseline A/E 0.85

Strongest support

The support worth taking seriously is 15pp+. The strike rate rises from 16.8% to 58.8% (20 winners from 34; +42.0 percentage-point uplift). From 39 qualifying bets, backing at 10am returned +28.4pts (+72.8% ROI), while backing at SP returned +11.4pts (+29.2% ROI). These runners were historically profitable even at SP, but the earlier price produced considerably more value.

When the same 15pp+ support was present by 10am

Twenty-five runners had reached this level by 10am. Nine shortened again before SP, so 36% continued to shorten. Returns were +2.9pts at 10am (+11.6% ROI), +3.2pts at 1pm (+12.8% ROI) and +2.5pts at SP (+10.0% ROI). Value generally remained at 1pm, but waiting until SP gave away too much of the price.

Drift

No drift band currently produces a large enough strike-rate fall from a reliable sample to call it a serious warning.

Price timing

Opening to 1pm has been the most informative support window at the first meaningful timing band: 58 winners from 179 runners (32.4%). In that sample, the SP return held up at least as well as the recorded 1pm price.
SupportStrike rateUplift10am ROI1pm ROISP ROI
3pp+22.6%+5.8pp+9.2%+8.1%-2.7%
5pp+28.0%+11.2pp+17.5%+13.6%-0.8%
8pp+34.5%+17.7pp+26.2%+20.4%-1.5%
12pp+48.9%+32.1pp+55.1%+47.6%+23.8%
15pp+58.8%+42.0pp+81.8%+44.1%+35.3%
Customer bottom line: James Owen’s normal strike rate is 16.8%, but it rises to 58.8% when a runner receives 15pp+ support. These runners have historically been profitable at 10am, 1pm and even SP. Support of 12pp+ is also exceptionally strong, while smaller 5pp–8pp moves require an early price because the value has usually disappeared by SP.
Integration Use Cases

Built to add context inside existing racing products.

Racecards
Market Movers Pages
Trainer Profiles
Trading Dashboards
Editorial Tools
Betting Apps
Internal Research
Broadcast Graphics
Technical Documentation

Trainer / Yard Context API

The endpoint returns a complete historical market profile for the requested trainer in structured JSON.

Endpoint GET
https://dc-network.co.uk/wp-json/dcn/v1/trainer-market-profile
Authentication Commercial API key required.
?api_key=YOUR_API_KEY
Trainer Parameter
?trainer=James%20Owen
Example Request
https://dc-network.co.uk/wp-json/dcn/v1/trainer-market-profile?trainer=James%20Owen&api_key=YOUR_API_KEY
Response Section Description
trainer Name of the trainer profile returned.
baseline Overall trainer runs, wins, strike rate, ROI and A/E.
supported Historical performance at 3pp+, 5pp+, 8pp+, 12pp+ and 15pp+ support levels.
drifted Equivalent historical matrix for runners drifting by the same probability-point thresholds.
strike_rate Win percentage within the specific historical band.
vs_baseline_pp Strike-rate uplift or decline versus the trainer’s overall baseline.
ae Actual winners divided by expected winners at SP.
timing Historical performance across key market timing windows.
support_by_10am Uses the same strongest reliable support band and reports how many runners shortened again before SP, plus returns at 10am, 1pm and SP.
price_timing Identifies where historical value generally remained and whether waiting for SP surrendered price value.
drift_context States whether a reliable drift band is serious enough to be treated as a warning.
plain_english Ready-to-display interpretation of support and drift behaviour.
Example Response
{ “success”: true, “data”: { “trainer”: “James Owen”, “baseline”: { “runs”: 1119, “wins”: 188, “strike_rate”: 16.8, “ae”: 0.85 }, “supported”: { “15pp_plus”: { “runs”: 34, “wins”: 20, “strike_rate”: 58.8, “vs_baseline_pp”: 42.0, “qualifying_bets”: 39, “roi_10am”: 72.8, “roi_1pm”: 44.1, “roi_sp”: 35.3 } }, “support_by_10am”: { “matched_band”: “15pp_plus”, “runs”: 25, “shortened_further”: 9, “continued_shortening_pct”: 36.0, “roi_10am”: 11.6, “roi_1pm”: 12.8, “roi_sp”: 10.0 }, “drift_context”: { “serious_warning_found”: false }, “price_timing”: { “most_informative_window”: “open_to_1pm”, “runs”: 179, “wins”: 58, “strike_rate”: 32.4 }, “plain_english”: { “support”: “James Owen’s strike rate rises from 16.8% to 58.8% when a runner receives 15pp+ support. These runners were historically profitable even at SP, but earlier prices returned more.”, “by_10am”: “When the same 15pp+ support was present by 10am, 36% shortened again before SP. Value generally remained at 1pm, while waiting until SP reduced the return.”, “drift”: “No drift band currently produces a serious warning from a reliable sample.”, “customer_bottom_line”: “Support of 12pp+ is exceptionally strong. At 15pp+ it reaches its strongest reliable level; smaller 5pp-8pp moves generally require an earlier price.” } } }
Methodology

Designed around observable market behaviour.

Probability-Point Measurement

Market movement is measured through changes in implied probability so that equivalent behavioural shifts can be compared across different price ranges.

Historical Outcomes

Trainer performance is derived from historical race results matched against recorded Market Form prices and market movement behaviour.

Commercial Access

Add yard intelligence without rebuilding your racing product.

The API is designed as an additional intelligence layer. Customers retain full control of their existing racecards, odds, presentation and user experience.

Integration

REST-based JSON delivery with authenticated commercial API access and integration documentation.

Licensing

Commercial licensing can be structured around expected usage, distribution, territory and product requirements.

Add historical trainer market behaviour to your racing product.

For API access, technical integration questions or evaluation discussions, contact DC Network directly.

DC Network · Market Form® · Trainer / Yard Context API · Horse Racing Market Intelligence