Hosting
Does traffic to a Cloud site use my API requests?
No. On managed hosting a visitor asks BetterCMS for a page and is served HTML from the CDN. Nothing in that path is a Content API call, so nothing is metered. The monthly API allowance counts uncached Content API requests, which means the calls your own code makes, not the pages we render and serve for you.
That is why a Cloud site’s usage tracks how often you publish rather than how much traffic it gets. A day with a hundred visitors and a day with a hundred thousand cost the same.
What a visitor actually touches
A browser asks your domain for a page and gets HTML back from the CDN. It never speaks to the Content API and does not know it exists. The allowance counts uncached Content API requests, and a cached page served to a visitor is neither.
Images and files are the same story from the other direction: they are served from the media CDN and counted as bandwidth, which is a separate meter with its own number on the plan.
Why the number tracks publishing, not traffic
On managed hosting the content is read when a page is rendered, and a page is rendered when something about it changed — you published, you edited, a scheduled entry went live. Visitors read the result.
The practical consequence is that a Cloud site’s API usage is roughly a function of editorial activity. It is why a marketing site on Starter will not approach a million requests a month however well it does.
Where a Cloud site does use the allowance
If you also call the Content API yourself — a script that syncs entries somewhere, an integration pulling content into another system, a framework page in a hybrid setup — those calls are yours and they are counted. Managed hosting does not exempt a project; it just means the pages we serve are not part of the number.
Also in hosting
Still have a question left
Thirty minutes with the product team, and a straight answer.