Presentations.AI’s November 1, 2026 white-label API announcement states that standard generation uses 10 credits per slide. Its API product page repeats that rule, but a separate FAQ example counts an average 15-slide presentation as 75 credits. Those statements do not produce the same usage estimate.
Calculate the slide total first
At 10 credits per slide, a 15-slide presentation uses 150 credits: 15 multiplied by 10. A 75-credit estimate for that same slide count implies five credits per slide. Neither arithmetic operation establishes which charge will appear in an individual account; it establishes that the published examples need reconciliation.
The API page illustrates Growth with 6,000 credits and approximately 80 presentations under its 75-credit assumption. Applying the separate 10-credit rule to 15-slide decks instead gives 6,000 divided by 150, or 40 decks. Treat 40 as a calculation under that stated assumption, not a verified Growth allowance or a promise of completed presentations.
Keep the announcement’s reference rate separate
The November 1 release quotes a standard API reference rate of USD 0.01 per credit, or USD 0.10 per generated slide before discounts. It describes a three-month 50% launch offer whose eligibility depends on commercial terms and the selected package. It also says API pricing is separate from individual and Team subscriptions, and API credits do not carry over between billing periods.
For an illustrative worksheet using only the undiscounted reference rate, 150 credits multiplied by USD 0.01 gives USD 1.50. That is the calculation for the assumed 15-slide generation, not a monthly invoice quote. A package price, its included usage and any applicable conditions must be confirmed separately.
Ask one precise question before budgeting
A useful question to the provider is: for my selected API package, how many credits will this exact 15-slide generation consume, and which published estimate should I use? Include the two source descriptions with the question. Record the answer with the plan name and the date, so an older example does not silently become the budget’s permanent assumption.
Keep planned slide counts visible in your own estimate. If some decks have ten slides and others have twenty, a single average deck count can hide the difference. Calculate each group’s assumed usage, then total the groups. Leave unconfirmed charging rules unresolved rather than choosing whichever estimate makes the plan look cheaper.
What has and has not been checked
This comparison uses the company’s release and publicly readable API page. No account, API request, credit deduction or invoice was tested. The discrepancy is in the inspected documentation; it is not evidence that customers have been charged incorrectly.
Primary sources
- Presentations.AI white-label API announcement, November 1, 2026: https://www.globenewswire.com/news-release/2026/11/01/3392775/0/en/presentations-ai-launches-white-label-ai-presentation-generator-and-editable-powerpoint-api-for-saas-companies-agencies-and-ai-agents-at-0-10-per-slide-with-a-50-launch-discount.html
- Presentations.AI API product page — pricing and slide-credit FAQs: https://www.presentations.ai/solutions/api
Check the credit arithmetic
