UTC_MONTH in YYYY-MM format. credits account reports the effective Free/Paid plan, available credit lots and their next expiry. credits balance reports reservations, the seven-day credit-grace deadline and active meters with their versioned rate cards; credits usage reports measured consumption. Follow the returned cursor to read subsequent pages.
What contributes to consumption
Builds, active database compute, storage and supported service operations are measured through their actual meters. Published credit prices list each quantity and rate. Quiet databases can suspend compute, while retained storage/history and deployed scripts still cost credits. A query may wake a suspended database. Shared Dev/Prod use one data area; isolated areas are metered separately. Change data assignments explains the four confirmed actions without copying data or changing rates. Performance database pricing changes the database-compute rate. Do not multiply the complete bill or already valued usage again.Read the balance correctly
Monthly Free and Paid credits expire on the date shown in Billing and are spent before top-ups. Paid-only top-ups and recharges carry over during uninterrupted Paid membership; their remaining balance expires on downgrade to Free and cannot return after a later upgrade. An unpaid Stripe renewal keeps Paid features and top-ups for up to fourteen days after period end, with no new Paid or Free monthly allowance; cancellation ends Paid at the paid period end.paid_until remains the real invoice period end during renewal grace, so use the account’s effective plan/source. Signup/referral grants keep their recorded terms. In-flight reservations appear as reserved_micros in credits account and credits balance; the portal does not show them.
Some measurements arrive later than the original operation. A low current total is not a guarantee that all running work has settled. Project budgets control the intended monthly limit and its Continue/Stop behavior.
Billing and recharge · Database profiles.