Usage and limits
Read current usage
Open Bills and usage in your authenticated workspace. The current API reports the private-beta plan, integrations, integration calls in the last 24 hours, pending operations, daily execution limit and integration registry limit. These are not an invoice or an email-delivery counter.
Monthly outbound cap
Email plans cover outbound recipient-emails only, with separate budgets for connected inboxes, AI and SMS. Sending pauses at the monthly cap until an authorized upgrade or the next reset. There are no automatic paid overages. The local implementation uses UTC calendar months, with no rollover; annual commitments retain monthly caps. Production enforcement is not activated.
Understand different limits
Email allowance, API request rate, integration execution budget, provider sending rate and storage capacity are separate controls. Buying a larger email allowance does not bypass membership, API-key scopes, suppression, approval or provider restrictions.
If an action is blocked
For quota_exceeded, check the operation and affected resource before requesting a limit review. For scope_denied, ask the company owner to review your role or key scope. For membership_denied, confirm the selected company and membership. Retrying with new identities or API keys is not a remedy.
Unknown outcomes
A timeout does not prove an email failed. Do not submit a new send to work around an unknown outcome. Keep the operation reference and request reconciliation; provider acceptance and recipient delivery are separate states. Commercial monthly metering and payment synchronization are not connected yet.