Pinnacle API cost calculator

From interval to usage

Estimated requests = (3,600 ÷ interval in seconds) × active hours per day × days × requests per cycle. One request every 10 seconds for 24 hours across 30 days produces 259,200 requests. Partial cycles remain fractional in this planning estimate; a real scheduler and billing system may round differently.

Credits = requests × credits per request. Excess credits = max(0, credits − included quota). If an overage is explicitly priced, estimated charge = base charge + (excess credits ÷ 1,000 × overage price). Overage is prorated; this is not a block-billing model.

Use the presets carefully

The presets use the published plans of the Pinnacle feed this site covers, checked 2026-09-27. The free key allows 100 requests a day and 20 a minute. The paid REST plans have no volume cap and are limited by rate instead: 10 requests a second for $99 a month, or 30 for $229. For those, included credits are the most requests the rate allows in the period, and the result flags any schedule faster than the limit. One request returns a whole sport's board, so requests per polling cycle is the number of sports and phases you poll. All entries remain editable.

What this estimate leaves out

Retries, pagination, event growth, idle periods, taxes, feature add-ons, and changes during a month are not inferred. Set requests per cycle and your own multiplier to reflect them. Streaming messages are not REST requests; this calculator makes no streaming cost comparison. For high-volume state, raw frames over WebSocket change the math; compare the delivery models in the transport guide. When the quota is exceeded and no overage is defined, the total is deliberately unknown.

For the request-per-second side of the same budget, sports and phases divided by the poll interval, see capacity planning on pnclENGINE.

Choose a delivery model · Normalize the responses