Usage & work credits

Work credits are the monthly usage budget included in your plan. Alex and your AI employees use this budget when they process information or attempt actions in connected apps. A credit is not a message: one task can use several credits, depending on its length and the actions it needs.

One accepted user message with a usable Alex response consumes one Alex message. Assistant chunks, internal calls and model retries do not consume additional Alex messages. A saved workflow consumes one workflow run per logical execution, including scheduled and app-event runs. Approval resumes and recovery do not start another run.

Gemini execution uses one work credit per 1,000 observed tokens, rounded up per model request. Input, output and thought tokens are included. Each dispatched integration tool attempt uses 1 work credits. These are resource units, with no fixed dollar exchange rate. Provider prices can differ by model. Ordinary conversation does not consume a saved-workflow run.

For example, one AI request using 2,500 tokens at the standard rate uses 3 credits. Two app-action attempts add 2 more, for a total of 5 credits. A task can involve several AI requests, each rounded up separately. Tokens are small pieces of text used by the AI, including your input, its response, and internal reasoning. Model multipliers, when listed below, adjust the token charge.

Your message, workflow-run, and work-credit allowances are separate limits. A task must fit within all applicable allowances. If you run out, wait for your next billing cycle or change plans to continue.

Execution reserves credits before work begins and settles measured usage afterward. Unused reservations are released when usage is known. A request that exceeds its estimate records actual consumption and can leave no credits for further work. An interrupted request with an unknown provider outcome retains its reservation for reconciliation. We never buy extra credits automatically.

Monthly allowances reset at the subscription billing period. Failed chat requests with no usable response do not consume a message; resources already consumed by an attempted external action can still consume work credits. Retries that dispatch another provider request consume the underlying resources.

A paid subscription is required to use Alex and execute workflows. Subscription level never overrides safety or application permissions. Creating an account does not start a subscription or charge your card.

Current policy: 2026-11-08-v2:4b71b65317f179e6