All pages
Billing and payouts
All app payments run on craving rails. On each app sale (plans and metered usage), craving keeps your Resident platform fee (20% on Free and Go, 10% on Plus, 5% on Pro and Team, or your agreed rate) plus a 10% marketplace fee, and transfers the rest to you. Paid plans and usage meters require Stripe payouts set up on your Resident account; free apps need no payout setup.
Charging installers
In the Pricing section of your app page, you can create up to 12 plans, each scoped to individual Resident accounts (account) or agencies (agency):
- Free: the installation activates immediately.
- One-time ($1 to $1,000): paid once at install.
- Monthly ($1 to $1,000): paid at install for the first 31 days. Agency monthly plans can charge per Resident (
per_seat) managed by the agency. After 31 days plus a 3-day grace period (34 days total), an unpaid monthly installation pauses (status: "disabled",installation.updatedwithreason: "payment_due") until the installer pays for the next month in Your apps.
Paid installs start as pending until Stripe Checkout settles, then activate and fire installation.created. Plans with active or pending installs lock their price and billing kind; create a new plan to offer a new price.
Metered usage
With usage_meters (and scope payments.app), you can define up to 20 meters (handle, unit price from $0.01 to $1,000, and optional monthly cap from $1 to $10,000) and report usage events via POST /v1/usage-events. Unbilled usage is summed per meter (capped at cap_cents) and collected on the installer’s next checkout or when they tap Pay usage in Your apps. Events are idempotent per (installation, idempotency_key) and accepted while the installation is active and for 24 hours after an uninstall.
Visitor checkout
fan_charges lets an app create items a Visitor buys on craving checkout (such as merch or custom bookings), split between the Resident, your app and craving. Every version declaring fan_charges requires human review and a working refund path; payment never happens inside your iframe.
Partner preview. The Visitor checkout API (POST /v1/fan-items and the /c/… checkout link it returns) is currently in partner preview. Versions declaring fan_charges stay in human review until your developer account is enrolled; email developers@craving.com with what you want to sell. Until then, link Visitors to the Resident’s existing craving offers (Memberships, Tips, Bookings, Personal Requests).
AI agent sales
When you register an OAuth client under Agents in craving Apps and a Visitor buys a Resident’s offer through offer_purchase on the MCP server, you earn 10% of the sale out of the Resident’s AI fee, transferred to your connected Stripe account.
Ledger and payouts
Every charge books a row on your developer ledger with the platform and marketplace fee percentages frozen at the moment of purchase, so later fee changes never alter past transactions. Installer checkouts run as Stripe Connect destination charges that transfer your net share to your connected Stripe account at settlement. Refunds and disputes reverse the developer leg; any reversal that exceeds an unpaid balance is recorded as a clawback balance and netted from future payouts.
Taxes and invoices
You are responsible for reporting and paying your own taxes. craving issues the receipt to the buyer, and your app stats and Stripe account show the gross, fees and net for every transaction.