Billing

Production onboarding

Company account → app registration → pricing and company card → installation → verification. The customer personally accepts PAYG terms and enters the card on Stripe. No usage charge occurs at registration. A saved-card thumbnail or return URL alone is not activation; the console synchronizes and reads server state.

All enabled PAYG apps owned by the company share one card and one monthly invoice. Additional apps require separate explicit activation, even when a company card already exists. Existing individually negotiated contracts retain their terms.

Usage and invoices

Review the current catalog before activation. There is no monthly fee or minimum. A valid generated and settled suggestion is billable whether accepted or not; abstention and errors do not add a unit. Identical replays do not generate another unit. Actual usage is invoiced after each UTC calendar month. Zero usage costs zero; small balances may carry forward under the payment processor's minimum charge.

The invoice notice is addressed to the active, verified company developer account email. It includes the usage period, amount and invoice/PDF links when available. Delivery uses the durable email outbox with retries and delivery-feedback tracking. Provider acceptance is not proof of inbox receipt. Deployment requires the email worker and delivery provider to be configured.

Open Apps, usage and billing for totals, app usage and invoices. Company billing is distinct from an individual's Clone subscription.

Budgets and trial

An optional alert budget sends notices without stopping predictions. A separate, explicit company hard limit stops new predictions at that boundary. Neither is silently enabled during onboarding. Payment recovery follows the documented billing policy; a failed invoice does not automatically stop PAYG predictions.

Free sandbox: 1,000 suggestions once, shared across the account. No card and no automatic paid upgrade. Creating or rotating an app does not reset it. Complete billing reference.