Understand plans, usage, and metered work

Know what consumes an allowance, when a provider is called, and what happens at a boundary.

Open this area in the app ↗
01

Separate platform limits

Sites, team seats, monthly crawls, URLs per crawl, schedules, and provider-backed tools can have separate limits. The Plans page and the current workspace notice are the source of truth for the active tier.

02

Know what starts billable work

Opening a saved report does not start a crawl. Prefilling a tool does not start a provider request. The explicit Run, Refresh, or analysis action begins new work when the plan allows it.

03

Expect a clear boundary state

A locked action should identify the current plan, the required capability, and whether an add-on route exists. A blocked action should not call a provider or save an error as a successful result.

04

Use current plan details

Product packaging can change as capabilities grow. Use the live Plans page for exact allowances, prices, and annual options instead of relying on an old screenshot or support message.

Apply the guideReturn to the evidence and complete one verifiable action.
Open the app ↗
Did this guide solve the task?No account or workspace data is recorded here.