Subscriptions and billing API for plans, invoices, and entitlements

ChefSphere subscriptions and billing APIs cover plans, payments, invoices, and entitlement writes so premium features are not a boolean hack in a user profile table. Food apps sell meal-plan tiers, creator memberships, and unlocked publishing libraries that need consistent entitlement state across clients. This module is about subscriber billing and access rights—not prepaid developer token packs, and not in-app wallet gifts for creators.

That distinction matters for search intent: prepaid-api-tokens explains how you pay ChefSphere for API usage, while this guide explains how your end users pay you for plans. Wallet currency covers balances, purchases, gifts, and creator earnings as a different money surface inside the same platform. Keep those three money stories separate when finance asks which ledger does what in your product.

Plans need clear features, renewal behavior, and upgrade paths your support team can explain without inventing policy in a ticket thread at midnight. Payments and invoices need audit-friendly history when chargebacks and tax questions arrive—and they will arrive after you take real money. Entitlement writes should be the source of truth clients check before unlocking catalogs, live rooms, or AI quotas you market as premium.

Subscription writes sit in a heavier band on the prepaid developer token table because they mutate access and money-adjacent state for your customers. That cost is separate from the price your subscriber pays on a plan; do not confuse end-user billing with developer token burn. Packs for API usage still start at $29 for 200,000 tokens once early access is granted, shared across all modules including billing writes.

Pair subscriptions with digital publishing when paid libraries matter, and pair with AI when premium assistants are gated behind a plan your users understand. Pair with marketplace only when you truly sell subscriptions as a commerce SKU rather than confusing checkout with membership renewals. Early access onboarding is where we align which entitlements are version one versus later upsells.

Your integration still authenticates with an X-API-Key and burns prepaid developer tokens per call in the Firebase-style model used across the platform. That meter is how ChefSphere bills platform usage; it is not the subscriber invoice your customer downloads from your app settings screen. Keeping the vocabulary clean prevents finance meetings where everyone means a different token, credit, or entitlement.

Request access, describe plan catalog and markets, and we email when onboarding opens for your subscription use case. Illustrative docs help you plan shapes; production contracts follow access for real entitlement flows you can enforce in clients.

Ship one clear plan and one entitlement check path before offering five tiers with overlapping perks nobody can support without a spreadsheet war. Document what happens on cancel, grace, and failed payment before marketers invent a story that engineering cannot enforce in production. Entitlement clarity is a product moat; ambiguity becomes refunds and app-store complaints you will own publicly.

Related guides on prepaid API tokens, wallet currency, and digital publishing help you place the right money module on each user journey. Request early access with your planned tiers and whether entitlements gate AI, publishing, or live rooms in version one. We contact you when keys and packs are available.