Odds API cost

The subscription is only the visible half of the bill. The other half is engineering: collecting prices from each bookmaker yourself, mapping every bookmaker's names onto one schema, pairing back prices against exchange lay, and keeping all of it working whenever a bookmaker changes its site. A cheap raw API can leave the pairing and its upkeep with you.

Four things move the price of the data itself. Breadth is how many bookmakers and markets a plan reaches. Freshness is how old a price is when it arrives. Shape is whether prices come raw or already matched against the exchange, and support is whether a person answers when an integration breaks.

In the OddsRelay feed

OddsRelay charges in tokens, drawn from one pool per account that resets monthly. A call's price comes from the request, meaning the product and the filters named on it, never from the size of the reply. GET /v2/pricing publishes the table every call is priced from, and each reply to a valid key states its own cost in the X-Tokens-Cost header.

Any data request can be priced before it is made. Adding quote=true returns cost, remaining and rate_card in place of the data, free, so a developer sees what a filtered call costs before wiring it in. The kick-off window filter is never priced. A price above the balance is refused with 402 insufficient_tokens, which also costs nothing.

Polling habits decide the rest. A request that sends back the last ETag as If-None-Match gets a 304 when nothing has changed, and a 304 costs nothing, as do replies with no events, discovery routes and every refusal. On the raw feed, following changes with a recent updatedSince pays a reduced share of the query's price.

OddsRelay publishes its plans on the pricing page. Every plan gets every product and bookmaker its region serves, and plans differ only in tokens, so choosing a plan comes down to how much a product will call. Enterprise is quoted.

Related