> ## Documentation Index > Fetch the complete documentation index at: https://docs.openlens.com/llms.txt > Use this file to discover all available pages before exploring further. # Limits and allowances > Every plan number in one table. Seats, clients, the credit pool, platforms, MCP and API calls. One page, every number. This is the reference for what each OpenLens plan includes. For your org's live numbers, open **Usage** in the dashboard. ## The numbers | | Free | Starter | Agency | | ---------------------------------- | ------------------------------ | ---------------------------------------- | -------------------------------------------------------------- | | **Seats** | 2 included | Up to 5 | Unlimited, billed per seat | | **Free viewers and client logins** | Unlimited | Unlimited | Unlimited | | **Clients** | 3 | 5 | Unlimited, 100 per paid seat soft ceiling | | **Monthly credit pool** | 1,000 + 75 per client | 8,000 per seat + 200 per client | 50,000 per seat + 500 per client | | **Credit weight per output** | 1 | 1 | 1 (Claude 100, Grok 50) | | **Tracking cadence** | Weekly, monthly | Weekly, monthly | Daily, weekly, monthly | | **Platforms** | ChatGPT, Perplexity, Google AI | ChatGPT, Perplexity, Google AI, DeepSeek | ChatGPT, Perplexity, Google AI, Gemini, DeepSeek, Claude, Grok | | **MCP calls included per month** | 50 | 500 | 2,000 | | **API calls included per month** | 100 | 500 | 2,500 | | **Manual runs per day** | 10 per user | 10 per project | 10 per project | ## How the credit pool works Every plan includes a monthly pool of credits, pooled across your whole org and never caged per client. One output is one answer from one AI platform for one prompt, and on most platforms one output draws 1 credit. Claude draws 100 and Grok draws 50. We reach those two through direct official APIs, and an answer there is significantly more expensive for us than one from the consumer surfaces. Scheduled tracking reserves credits up front. Each scheduled project commits prompts × cadence × platform weights per month, so a weekly prompt on one standard platform draws about 4.33 credits a month and a daily one draws 30. Whatever your schedules don't reserve stays as slack for manual runs. The whole pool resets on the 1st of each month, UTC. ## What counts as a seat You only pay for teammates who can edit. A seat is a write-capable member: an owner, an admin, or a member with manager access to at least one project. Read-only members and client logins are free and unlimited on every plan. A member who holds write access at any point in a billing period counts as a seat for that period. Seats bill when you add them, prorate up mid-cycle, and true down at renewal. The credit pool trues down the same way, at renewal and never mid-cycle. ## MCP and API calls Every plan includes a monthly band of MCP calls and API calls, even Free. The bands reset on the calendar month, and they only ever move up. Calls are role-blind: a viewer's MCP call or a client's API call draws from the same org bands as an admin's. ## Manual runs On Free, manual runs meter per user: each user gets 10 a day. On paid plans they meter per project: 10 per project per day, and they don't pool across projects. Manual and API-triggered runs both count against the daily number. Scheduled runs bypass it entirely. And re-running the same project has a 5 minute cooldown, on every plan. ## Readiness Site / Agent Readiness has its own limits, separate from the credit pool. See [Readiness](/manual/readiness) for what the product does. | | Free | Starter | Agency | | ------------------------------------ | -------------------------------- | --------------------- | ---------------------- | | **Pages per run** | 50 | Unlimited (full site) | Unlimited (full site) | | **Monthly page allowance** | 150 | 5,000 per seat | 200,000 per seat | | **Lighthouse pages sampled per run** | 1 | 10 | 50 | | **Per-page detail** | Taste (first 2 fail/warn checks) | Full | Full | | **Scheduled cadence** | None | Weekly, monthly | Daily, weekly, monthly | Two levers gate a run. The first is per-run crawl scope: the pages a single run may crawl. The second is a calendar-month page allowance, pooled across your whole org. Effective scope is `min(requested, tier per-run cap, remaining allowance)`. A run that exceeds your remaining balance is clamped to what's left, not blocked. The allowance reserves pages on start and refunds the unused portion on finish, then resets on the 1st of each month, UTC. Free includes a flat 150 pages a month. Starter and Agency allowances scale with the number of paid seats in the org for that billing period. Lighthouse is decoupled from crawl size: a flat sample of 1, 10, or 50 pages per run, so a larger crawl never multiplies the slow Lighthouse calls. ## AI Indexing AI Indexing has its own monthly page allowance, separate from Site / Agent Readiness and separate from the credit pool. See [AI Indexing](/manual/ai-indexing) for what the product does. | | Free | Starter | Agency | | -------------------------- | ------------------- | -------------------------- | ---------------------- | | **Pages per run** | 50 | Unlimited (full site) | Unlimited (full site) | | **Monthly page allowance** | 150 | 1,000 per seat | 10,000 per seat | | **Visible page rows** | 50 URL/verdict rows | Up to 500 URL/verdict rows | Full | | **Scheduled cadence** | None | Weekly, monthly | Daily, weekly, monthly | AI Indexing page allowance resets on the 1st of each month, UTC. Starter and Agency allowances scale with the number of paid seats in the org for that billing period. ## Grandfathering Accounts created before the new plans launched keep their prior allowances as a floor, permanently. If your Free account had 5 clients before the change, you keep 5.