Skip to main content
The billing API returns the public plan catalog: limits, retention, capabilities, and overage rates for each plan. Use it when a script or agent needs current plan data. It does not show the billing state of your organization.

Operations

This endpoint does not require project scope. It returns the plan catalog; account-specific billing actions remain separate from this public API surface. Plans include a retention_days_by_feature object because error history, logs, traces, metrics, replays, AI observations, product events, findings, and investigations can have different retention windows. product_event_limit is the number of product events included each month, counted after consent checks and without duplicates. ai_credit_limit is the number of AI credits included each month. Each Squasher Agent action uses a fixed number of credits, once per action. See AI credits. ai_investigation_limit is the number of investigations that the included AI credits pay for. Investigations have no allowance of their own. All agent runs and follow-up questions in one investigation count as one. coming_soon lists the capabilities, overage meters, and retention_days_by_feature entries whose feature is not available yet. The plan lists them so that you can plan. Squasher does not count or bill them until they leave this list. telemetry_gb_limit is the telemetry included each month, in GB. Telemetry counts the uncompressed bytes of errors, logs, traces, metrics, web vitals, and AI observations as Squasher receives them. log_limit is an older name for the same value. Errors and AI observations do not have a meter of their own. status_page_limit is a count. For plans with unlimited status pages, it returns the fair-use limit. status_subscriber_limit is the most confirmed subscribers allowed on all your status pages. It is a plan limit, not a meter. Each overage entry has a billing_status. The overage meters are logs (telemetry GB), replays, checks, ai_credits, sms_alerts, voice_alerts, and product_events. logs, checks, replays, and ai_credits have cataloged paid overages; on Free they return allowed: false, because Free stops at its allowances. logs uses the unit gb and ai_credits the unit credit. sms_alerts, voice_alerts, and product_events return not_billed, allowed: false, and price_cents: 0 while their charges are inactive. Their included amounts are on the pricing page.

CLI and MCP

Use squasher billing plans for terminal workflows. In MCP Code Mode, call search("billing") before executing.

Agent handoff

Related: Plans and billing.