Docs
API referenceSee your plan and usage
- Select Organization in the sidebar, then Usage and billing.
- Overview shows the plan, the Subscription, the usage charges so far, and each allowance of this month. When the organization has no paid subscription, select Choose a plan (or Upgrade now on Free).
- Plans shows each plan as a card with its price, allowances, and overage rates. To change your plan, select the button on a card, for example Choose Team.
- Usage shows one month at a time. Select the month at the top, or a row in Months. It shows the bill so far, one card for each meter with its daily series, rate, allowance, budget, and project shares, and the usage statistics that are counted but not billed. Owners and billing admins set a budget for each meter in Budgets. See Usage and budgets.
What Squasher counts
Errors are part of telemetry GB. There is no separate error allowance. One GB is about 200,000
error events, or about 20,000 AI observations (the model calls that your application makes).
On paid plans, telemetry above the allowance is billed per started GB, at the rates in the table
below.
AI credits
The Squasher Agent uses AI credits for the work that it does for you: AI triage of monitor and alert incidents, investigations, auto-fix pull requests, pull request reviews, answers in chat, Slack, and the API, and automation runs. One AI credit is $0.01. Each plan includes AI credits every month. All projects in the organization share them.
Each action uses a fixed number of credits, charged once per action. A retry of the same action
and follow-up questions in the same investigation use no more credits. AI triage of an issue is
included on every plan and uses no credits. AI triage of a monitor or alert incident is a full
agent investigation, so it uses credits. Each project has a daily limit for automatic incident
triage (10 a day by default). You can change the limit or turn automatic incident triage off in
Settings > Incidents.
- Premium model: when you select a premium model tier, the action uses three times the credits.
- Your own model key: when the work runs on your own model provider key, you pay the provider for the model. Squasher charges a platform fee of 20% of the credits, rounded.
- Credits reset at 00:00 UTC on the first day of each month. Unused credits do not carry over.
- Free stops at the included credits. There is no overage on Free.
- Paid plans continue past the included credits. Squasher bills the extra credits in blocks of 1,000, rounded up to the next block, up to the organization’s AI credit budget.
- AI credit budget: the most that the organization pays for extra credits in a month. Each paid plan has a default budget. Owners, admins, and billing admins can change it. A budget of $0 stops AI work at the included credits. AI credits always stop at the budget. See Budgets and usage alerts.
- When the organization reaches the budget (or, on Free, uses all included credits), automatic AI work stops until the next month, and chat and Slack answer with a notice instead of an answer. Issue grouping, alerts, monitors, and paging continue as usual. AI triage of issues uses no credits, so it continues. AI triage of incidents stops.
- Billing admins get an alert when the organization reaches 50%, 80%, and 100% of its included credits, and 50%, 80%, and 100% of its AI credit budget.
- Each project also has a daily limit, so that one busy project cannot use all of the month’s credits in one day. At this limit the agent answers your questions but stops automatic work until the next day.
Use your own model key
You can run the Squasher Agent on your own OpenRouter account. One OpenRouter key covers every model that the agent uses. Other model providers are not supported.- Create a key at openrouter.ai/keys. You can set a spending limit on the key. The limit also limits the agent.
- In Squasher, open Organization settings > AI provider key and select Add key. You must be an owner or admin.
- Paste the key and select Check and save. Squasher checks the key with OpenRouter before it saves it.
- The agent’s model calls run on your key, and OpenRouter bills you for them. Each action uses only a platform fee of 20% of its normal AI credits (see the table above), and AI triage of issues is free. When the month’s credits are used, issue triage keeps working; other actions stop until the next month, or until a paid plan’s AI credit budget allows more.
- The daily limit for each project still applies.
- Squasher stores the key encrypted and never shows it again. Settings show only its last four characters and the model cost that ran on it this month.
- If OpenRouter refuses the key (for example, it was revoked, has no credits left, or reached its limit), the run stops with an error that says so, and settings show the key as Failing. Squasher does not use its own key in place of yours. Fix the key, then select Test key.
- To go back to AI credits, select Remove.
SMS and voice alerts need a paid plan. Free includes none. See
On-call escalation.
Meters marked coming soon belong to features that are not available yet. Their allowances are on
the pricing page so that you can plan. Squasher does not send, count, or bill them yet.
Infrastructure provider metrics count as Telemetry GB. They do not have a meter of their own.
Budgets and usage alerts
A budget is the most that the organization pays above the included amount of a meter in a month. Each paid plan has a default budget for each meter. Owners, admins, and billing admins can change the amount, and for telemetry, session replays, and product events they can choose what happens at the budget:- Alert (the default): Squasher sends an alert, and usage continues. Usage above the budget is billed at the listed rate.
- Stop: Squasher refuses new usage of that meter until the next month, or until you raise the budget. A raised budget takes effect within a minute.
Owners, admins, and billing admins get an alert when the organization reaches 50%, 80%, and 100% of
the included amount of a meter, and again at 50%, 80%, and 100% of its budget. Each alert is sent
once per meter and month.
How monthly allowances work
- Allowances reset at 00:00 UTC on the first day of each month. Unused allowance does not carry over.
- On paid plans, Squasher bills telemetry GB, replay sessions, monitor checks, and AI credits above the allowance in blocks, and rounds up to the next block, up to the budget.
- On Free, telemetry and product events stop at the month’s allowance. See Free plan limits.
- The add-on meters have no overage charge today. AI credits are billed as described in AI credits.
- On Free, new replay sessions are refused when the month’s replay allowance is used. Monitors stop running when the month’s check allowance is used, and start again next month.
Free plan limits
When a Free organization uses the month’s telemetry allowance, Squasher refuses all errors, logs, traces, metrics, and AI observations until 00:00 UTC on the first day of the next month, or until you change to a paid plan. Errors count in telemetry GB, so there is no separate error limit. When a Free organization uses the month’s product event allowance, Squasher refuses new product events in the same way. Telemetry and product events have separate allowances: one limit does not stop the other. Paid plans accept product events above the allowance; this overage is not billed today. A refused request is not stored. Over OTLP/HTTP and the SDK endpoints, Squasher returns HTTP402
with x-should-retry: false, an x-squasher-limit header, and a JSON error message. The header
names the limit: free_monthly_telemetry, free_monthly_replays, or free_monthly_product_events
for the Free allowances, and budget_telemetry, budget_replays, or budget_product_events for a
Stop budget (see
Usage and budgets). Over OTLP/gRPC, it returns RESOURCE_EXHAUSTED without RetryInfo. SDKs and
OpenTelemetry exporters do not retry these responses. For AWS CloudWatch Logs through Firehose, Squasher acknowledges a refused delivery, so Firehose does not retry it. Usage is checked every few seconds, so
Squasher can accept a small amount of data after the allowance is used. Paid plans never refuse
telemetry because of an allowance. They refuse it only when an owner sets the telemetry budget to
Stop and the budget is used.
Features by plan
Plans also limit the number of projects and status page components, and the shortest check
interval: 3 minutes on Free and 30 seconds on paid plans. Plans have no price per seat. Squasher
refuses to create a monitor, heartbeat monitor, status page, or on-call schedule above these limits:
Heartbeat monitors are an advanced monitor type, so plans without advanced monitor types have none.
A heartbeat monitor also counts as a monitor. On-call is in beta: Squasher does not send on-call
texts or calls yet. Use notification routes to reach responders by email,
Slack, Microsoft Teams, or webhook.
Retention
Each type of data has its own retention period, and the periods grow with the plan. Errors are kept longer than logs and traces. The Plans tab shows the retention of each plan, for example “30d errors / 7d logs”.
Rows marked coming soon belong to features that are not available yet. The Data tab lists
them as Coming soon too. ”—” means that the plan does not include the feature.
Retention belongs to the organization’s plan and applies to every project in it. You cannot set
it per project. To see how long a project keeps each type of data, open Settings in the
project, then the Data tab.
Read plan data from the CLI or the API
The plan list is public. It needs no key:Next steps
Auto-fix
See what the Team plan adds for fixes.
Monitors and incidents
See which monitor types each plan has.