Usage and overages
How Suede meters usage and bills for overages on paid plans.
Suede tracks five usage dimensions per child org per billing period. How overage is handled depends on your plan tier.
Metered dimensions
| Dimension | What it measures |
|---|---|
| Monitored prompts | Distinct prompt templates running daily across enabled AI platforms |
| Chat tokens | Tokens consumed by the AI assistant |
| MCP calls | Programmatic requests via Model Context Protocol |
| Workflow executions | Automated workflow runs (requires Workflows module) |
| Pitch spaces | Temporary client workspaces for agencies (agency overlay only) |
Hard caps vs. soft limits
Free plan orgs have hard caps. When you reach a limit, the operation is blocked. No additional charges apply.
Paid plan orgs (Pro, Team, Enterprise) have soft limits. When you exceed a limit, the operation continues and the overage is billed at the end of the billing period.
How prompt overage is calculated
Suede takes a daily snapshot of each child org's active prompt count. At the end of the billing period, overage is calculated as the average daily overage across all days in the period, rounded up.
Days where your active prompt count is at or below your plan limit contribute zero overage. Days above the limit contribute the difference. This means short spikes cost proportionally less than sustained overage.
Example: Your plan includes 100 monitored prompts. For 20 days you run 100 prompts (no overage). For 10 days you run 130 prompts (30 prompts over, each day). Average daily overage = (20 x 0 + 10 x 30) / 30 = 10. Billable overage = 10 prompts.
Usage notifications
Admins receive notifications when a dimension reaches 80%, 100%, and 120% of its limit. These notifications appear in the billing dashboard and through your configured alert channels.
Checking current usage
Open the Billing page from your parent org's sidebar. Usage bars show consumption against limits for each dimension, with an "Overage" badge when a dimension exceeds its limit.