If your AI tool expands a topic into sub-topics, and expands those, the call count is a geometric series. One more level costs you more than everything you have already spent. Work it out before you press run.
—
| Depth | Calls | Added by this level | vs. budget |
|---|
Worst case, assuming every node expands to the full branching factor. Real runs are usually cheaper. Plan for this number anyway.
—
The number is trivial to compute and it is the only thing standing between a user and a surprise bill. Showing it afterwards is an apology, not a feature.
Check and refuse before the call goes out. A counter you inspect afterwards has already spent the money. And the number you show the user should be the number they were billed for — if those two can drift apart, they will.
When the budget runs out mid-way you can keep the partial tree or throw it away. Both are defensible. What is not defensible is not having decided, because the calls are spent either way.
The arithmetic above came out of building Wikibuilder, an AI encyclopedia builder that expands a topic into subtopics and expands those in turn — which is exactly the geometric series this calculator plots. It is sold as source, you supply your own API key, and you pay your provider per call. Its listing carries the same cost warning as this page, because a tool that can spend your money in a loop should say so before you buy it, not after. There is a demo if you would rather look than buy.
The other source products — a Flask grow-tent dashboard, a SwiftUI drive tracker, a dependency-free strategy game template — are listed at bookmonger.gumroad.com/tools, with what each one does not do stated on the page.