Skip to main content
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

FreeStarterAgency
Seats2 includedUp to 5Unlimited, billed per seat
Free viewers and client loginsUnlimitedUnlimitedUnlimited
Clients35Unlimited
Monthly credit pool1,000 + 75 per client8,000 per seat + 200 per client50,000 per seat + 500 per client
Credit weight per output111 (Claude 100, Grok 50)
Tracking cadenceWeekly, monthlyWeekly, monthlyDaily, weekly, monthly
PlatformsChatGPT, Perplexity, Google AIChatGPT, Perplexity, Google AI, DeepSeekChatGPT, Perplexity, Google AI, Gemini, DeepSeek, Claude, Grok
MCP calls included per month505002,000
API calls included per month1005002,500
Manual runs per day10 per user10 per project10 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.

​
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.