Usage and limits

Use Usage & limits to inspect the policies and available balances for your organization. Service usage is shared according to the selected service's policy; it is not a separate allowance for each browser session.

Read the current policy

SiteOS is in early access, and services can have different usage policies. The application shows the active policy for your organization. An Unlimited label does not remove technical protections such as request-size limits, crawl budgets or execution timeouts.

Check the current policy before planning large imports, scheduled checks or provider research. Free monthly credits continue beyond early access. Check the application for the current allowance and renewal date.

An agent can read the same balances, limits and recent usage through the read-only siteos_billing_get_usage and siteos_billing_get_history MCP tools. Reading usage never activates a plan, buys credits or spends them.

Understand SEO research usage

SEO currently includes a $10 monthly credit allowance per Organization, shared across Projects, environments and team members. It renews monthly without rollover. All check types are available without a paid subscription, within usage limits.

New keyword, SERP, competitor, backlink and AI visibility measurements use this balance. This includes scheduled AI Visibility checks, which also stop at their own monthly limit, and the research prepared for a new project. AI content checks, Sanity Text checks, AI Visibility tone analysis and generated action plans use it too. Review the scope and available credits before starting. Eligible retries can also use credits. Reserved credits cover admitted work and are separate from settled usage.

Reading a saved report does not start a new measurement. Use existing evidence when it already answers your question, and retain its observation date and selected market when interpreting it.

Technical site audits, Performance, connected Google Search Console reports and deterministic Sanity SEO checks do not use this research balance. Preparing repair briefs and exporting saved reports do not spend it either. See SEO research for choosing the right workflow.

When an action cannot start

Read the service's specific status: an unavailable allowance, a running job, an unsupported input and a failed provider request require different fixes. Do not switch projects or environments to work around an error without checking the intended scope.

Pulse execution budget

With budget enforcement enabled, Pulse includes $10 per month per organization, shared across all Projects, environments, PR checks, manual checks and scheduled monitoring. Standard browser/code execution costs $0.005 per minute; built-in secret scans cost $0.002 per minute, calculated in seconds. The maximum Check cost is reserved before execution. Once it finishes, only measured time is charged and unused funds become available again. Queue time is not charged.

There is no daily PR quota. Concurrency is separate: checks wait when runners are busy. If the available budget cannot cover a Check's maximum duration, it waits for reserved funds to be released or the monthly allowance to renew. Saved reports remain available. Paid overages are not enabled.

When the displayed mode is Estimate · no charges, these values are forecasts: no credits are reserved or deducted and the estimate does not block checks. Old estimates never become charges. Read the displayed renewal date for the organization's cycle. Missing measurements mean unknown, not free; partial PR reports indicate how many checks have measurements.

With a matching CLI/server, siteos pulse usage --json reads these values for the selected Project's organization. The agent can also use the read-only siteos_billing_get_usage MCP tool. Test manifests, PR participation and schedules are unchanged. See Pulse for configuration.