Seven feed types, one schema

Standard is the core back-vs-lay output — each bookmaker back price paired to a current exchange lay price, rated, with the qualifying loss computed. It's the heaviest, always-live type and what an oddsmatcher renders by default. Dutching covers the case where you split a stake across books to cover every outcome; each row carries the return on investment and needs no exchange, which makes it the arbitrage-shaped output.

Each-way and extra-place serve horse racing: each-way pairs the win-and-place bet with its fraction, and extra-place surfaces the races where a book pays more places than the market, sorted for the offers that matter. Best-odds-guaranteed (BOG) flags the racing selections where the guarantee applies. 2up captures the early-payout lock-ins some books run on football. Price-boost covers layable boosted prices, carrying the original odds alongside.

Every type returns the same processed shape, so adding a type is a parameter, not a project. A platform that starts on standard can turn on each-way, dutching or 2up without touching its rendering layer — the offer-specific tools consume the same rows as the everyday oddsmatcher. That's what makes the matched feed a whole product surface rather than a single endpoint. The response shapes for every type live in the docs.

Which types matter depends on what you're building: oddsmatchers lean on standard, each-way and extra-place; arbitrage tools lean on dutching; football-offer tools use 2up and price-boost. The use-case pages map jobs to the types that serve them.

All seven types are pre-match, on roughly a three-second polling cycle, monitored, with published freshness — the cadence pre-match matched betting and arbitrage need. There's no in-play streaming, and we don't sell it. Volume varies by type in the natural way: standard is dense, the racing types populate around the racing calendar, and price-boost is available as a type but carries low and variable volume — we surface it as available, not as a guaranteed stream.