Multi-module token billing: one balance, different burn weights

Multi-module token billing is how one prepaid balance funds nineteen ChefSphere modules without rebuying a meter each time you enable social, live, or commerce. This guide focuses on relative burn and mix planning using published weights—not the pack SKU story alone, and not X-API-Key hygiene. Read prepaid-api-tokens for packs from $29 / 200k, Growth, and Scale; read api-keys-guide for secret handling; stay here for cross-module capacity math.

Reads are cheap. Writes, media, live sessions, AI, KYC, and checkout cost more by design on the developer pricing table. Unused tokens stay on your balance, so a quiet browse week does not erase capacity you bought for a checkout launch. Early access still gates keys and packs; there is no early access issuing production credentials automatically today.

A catalog-heavy meal planner burns mostly light reads and occasional plan generate; budget generation explicitly if you market AI-assisted weeks. A marketplace launch burns checkout writes and KYC submits far more than browse; do not average them into a fake per-user cost. A creator app with live and gifts stacks live session access, wallet transactions, and maybe moderation scans in the same prepaid month.

Published example weights include catalog read at the bottom and AI vision near the top, with social posts, media uploads, realtime connect, and subscription writes in between. Use those relatives to compare scenarios; do not invent precision about traffic you have not measured. Starter at $29 explores; Growth at $79 and Scale at $149 fit denser multi-module production; enterprise from $300 per month covers custom weights and limits.

Authenticate every call with an X-API-Key so burn attributes cleanly when one module suddenly dominates after a feature flag flips. Composition guides help you sequence modules; this billing guide helps you fund the sequence without surprise invoices. Request early access with your expected mix so onboarding can sanity-check pack recommendations without theater.

Mistake one: treating AI vision like a catalog read because both are “API calls.” They are not priced alike on the weight table. Mistake two: buying Starter for a live-plus-checkout launch because $29 is the smallest number on the page. Mistake three: forgetting media uploads when the feed is image-first and every post carries a transform cost.

Fix them by writing three monthly scenarios—browse, engage, transact—and summing weights before you pick a pack. Revisit after two weeks of real traffic instead of forever debating fictional precision in a spreadsheet. When volume outgrows packs, bring enterprise into the conversation with measured call mixes, not vibes, and keep that dependency map explicit in your early-access request so onboarding stays accurate.

Once your mix is on paper, request early access and attach the module list plus rough monthly call bands for the heavy rows. When onboarding opens, buy the pack that matches the mix, configure keys, and validate burn against dashboards before widening modules. One balance across marketplace, live, AI, social, billing, and the rest is the operational payoff of getting this model right.

Related guides on prepaid packs, API keys, and food-app composition connect capacity math to auth practice and product sequencing. If you are ready to fund a multi-module roadmap on ChefSphere, get in the early access queue now. We email when keys and packs open—early access while rollout finishes.