A monthly equivalent is not a monthly bill
When you choose a prepaid term, the service charges the term amount. The effective monthly number is only that amount divided by the number of months. It is useful for comparing options, but it does not mean you can pay that smaller amount each month or leave after one month.
The selector uses checked base-term prices and the documented raw WebSocket add-on schedule. The add-on is quoted in 30, 90 and 180-day blocks, while base plans use month-based labels. Confirm renewal alignment before paying. The total assumes the selected terms start together; it is not a quote for adding streaming halfway through an existing subscription. Mid-cycle purchases are handled in the account dashboard. Taxes, payment charges, cancellation conditions and refund eligibility need confirmation at checkout. Checked against the current pricing and add-on documentation, September 26, 2026.
Three useful plan-fit decisions
You need snapshots for a server-side application. Start by assessing the REST snapshots allowance against your actual polling schedule. Count every sport and request, then leave capacity for failures and resynchronization. A published per-second limit does not grant permission to run permanently at that ceiling. Back off when instructed, and review the account’s current limits.
You need processed odds-drop notifications. The SSE drop alerts plan includes SSE but retains much smaller REST quotas. If your application also refreshes event snapshots frequently, compare REST + SSE. Raw WebSocket is not an upgrade path on SSE drop alerts; choose an eligible base plan if you need raw frames.
You need to build your own view of a raw feed. Budget for an eligible base plan plus the raw WebSocket add-on, and for your own reconstruction, recovery and monitoring work. Paying for raw frames does not remove the need to handle partial market updates. The WebSocket guide describes the implementation boundary.
The free option is a validation step
Pinnacle data documents a free REST allowance of 20 requests per minute and 100 per day, with no card and no expiry: the key doubles as the account login. All windows matter: the per-minute allowance does not imply you can keep that rate all day. A three-day full demo covering SSE, raw WebSocket and 10 requests per second is available on request. This site does not supply a separate free API. Checked against the current documentation, September 26, 2026.
The free key is enough to validate your parser and failure handling against real responses. It does not establish streaming entitlements or the exact markets you will buy at checkout.
Before you choose a longer term
- Verify the exact sport, competition, event type and markets you need with the service.
- Confirm whether you need snapshots, processed alerts or raw frames; names alone are not interchangeable entitlements.
- Ask for the actual charge, renewal date, refund terms and any fees in writing or at checkout.
- Validate your parser and recovery behavior before increasing request volume.
Identical published prices do not establish identical service quality; verify the current offer and terms at checkout.
To size the REST side before choosing a tier, the API cost calculator on pnclAPI turns a polling schedule into requests per billing period, and the capacity planning page on pnclENGINE works out the per-second peak.