Billing
Manage the organization's plan, payment setup, and credits, including access changes that can follow a plan change.
Billing keeps the organization's plan, payments, and credit supply available for the work its callers perform. Members can read billing state; changes also require org:manage_billing. Reading usage does not authorize a purchase.
Use current billing state and pricing for commercial terms. Model-cost records explain work that ran; they are not a plan quote.
Complete a plan or payment change #
Confirm the organization, current plan status, entitlements, and payment state. If the plan change alters RBAC entitlement in either direction, members and pending invitations reset to Owner. Record intended roles and service-key dependencies before proceeding; Review access before changing entitlements explains what to inspect and restore.
Open the organization's Settings → Billing. Use Plan for available plan changes, or Open billing portal under Payment and invoices to manage payment details. A first credit purchase can start payment setup; follow its returned checkout redirect. A negotiated plan requires the account manager. Inspect the outcome afterward: opening a flow does not establish that a payment or plan change completed.
The billing interface can open a payment portal. Use the payment and invoice records available there rather than assuming Lingo.dev settings duplicates every portal action. Keep the account state and transaction outcome together when investigating a purchase.
Maintain credits for recurring work #
Check the credit balance before starting work that consumes it. A purchase may require payment setup or a checkout redirect. Confirm the transaction and updated balance before repeating a top-up after an ambiguous response.
Automatic top-up has enablement, balance threshold, purchase quantity, and maximum-per-month settings. Choose values within the organization's spending policy and confirm what was saved. Disabling top-up does not reverse completed purchases or consumed work.
The monthly top-up maximum applies to that purchase mechanism. It is not a universal hard cap on every workflow or charge. Credit consumption, provider-model costs, professional review, measurements, and plan charges remain different quantities; Usage explains their accounting boundaries.
For exhausted credits, compare the failure with the balance. An authorization refusal or provider limit needs a different repair. More credits cannot grant a missing permission, and more permission cannot settle an unpaid balance.
Review access before changing entitlements #
Plan changes can affect features and service keys. In particular, an RBAC entitlement transition in either direction resets members and pending invitations to Owner. Treat this as an access change, not merely the role editor becoming unavailable.
Record intended authority before the change, then inspect every member and pending invitation and restore deliberate assignments where applicable. Review API-key dependencies as well as roles.
Finish by reconciling the resulting plan, balance, payment record, and usage. Each supplies part of the account; no single model-cost number establishes the complete invoice or a fixed saving from a different model.