Hosting
Do the editor, the CLI and the MCP server use my API requests?
No. The allowance is for production reads from your own front end. Editing in the Visual Editor, opening a draft preview, running the CLI, regenerating types with bettercms-codegen and driving the MCP server are workspace tools rather than visitor traffic, and they are not counted against it.
The per-second rate limit is a separate thing and does apply to every caller, tools included. It protects the service from a burst, which is a different problem from a monthly total.
Why tooling is not metered
The allowance exists to size production reads — how much content your live site pulls. Counting the tools against it would mean a developer regenerating types in a watch loop, or a marketer with the editor open all day, could exhaust a plan without a single visitor arriving. That would make the number mean something other than what it is sold as.
So the editor, draft previews, the CLI, bettercms-codegen and the MCP server are outside it. Working on a site does not cost you the capacity to serve it.
What is metered instead
Uncached Content API requests from your own front end. In a headless setup that is your build or your server; in a hybrid one it is the framework half. Cached responses and asset delivery are not counted, and asset delivery is bandwidth.
The rate limit still applies
Monthly capacity and the per-second rate limit are different controls, and the second one applies to every caller. A build that fetches two hundred pages in parallel can hit it in a few seconds while using a trivial share of the month, and the fix is to batch or throttle the build rather than to buy more requests. Requests over the limit return HTTP 429.
Also in hosting
Still have a question left
Thirty minutes with the product team, and a straight answer.