PLAN NOTES

What to confirm at checkout before a Pinnacle API plan

The site publishes prices, quotas and term options. Cancellation, refunds, taxes and renewal terms live at checkout. A checklist for both halves.

The plan pages on this site tell you most of what a Pinnacle API subscription costs: the monthly figures, the prepaid terms, the add-on price. They deliberately do not settle everything. Cancellation, refunds, taxes and renewal terms live at checkout, and the right moment to read them is before you pay. Here is the full checklist, in the order you will meet it.

What the published pages already answer

Start with what is documented, because most of the money questions are. The plans run $99 a month for SSE drop alerts or REST snapshots, $149 for the two combined, and $229 for high-volume REST, as the pricing page lists them, checked 2026-10-01. Three-month billing exists for all four plans, six-month billing for REST snapshots and REST + SSE only, and the raw WebSocket add-on at $99 per 30 days attaches to the three REST plans but not to the SSE plan, per the same pages' billing answers.

Coverage needs no confirmation: every plan reads the same board with the same line depth. If your checklist has a line about sports or markets, the answer is already published.

What only checkout can settle

Four items are deliberately not published as fixed figures. Taxes and payment charges depend on your payment method and jurisdiction. Cancellation conditions and refund eligibility need confirmation at checkout, as the pricing page says directly. And the renewal terms differ by payment method: card and crypto are both listed at checkout, with the renewal terms for each shown there before you pay.

Read those four before confirming the order, and keep the terms you accepted. A saved copy of the checkout terms is worth more than a memory of them at renewal time.

Match the cart to the decision

Choosing a plan on this site creates no order; the cart at checkout is the commitment. So check three identities before paying: the plan matches the loop you sized, the term matches how proven the loop is, and the add-on is in the cart only if your base plan is eligible for it. The plan guide maps each kind of loop to the plan that carries it.

If any of the three is wrong, fix it on the plan side, not at the payment side.

After the payment

Two habits close the loop. Manage the subscription from the account panel, which is where plan, key and billing live. And treat the first response on the new entitlement as a fresh validation: the access checklist notes that free-tier success does not establish streaming access or the exact markets you bought, so run the first-request check again on the new plan.

Published figures first, checkout terms second, first request third. A plan bought in that order never surprises you later.