# Plans and limits Read your current entitlement and cost preview before asking Recala to spend. ## Read the active plan The credits command reports the current plan, article balance and cap information returned by the server. Use that result for this organization rather than hard-coding an allowance or price. ``` recala credits ``` ``` recala credits --json ``` ## Preview before generating Generating an article uses one article of the plan. A dry run returns the cost preview and balance without generating. A blocked topic, depleted balance or spending cap can refuse creation with exit 11. ``` recala article create --topic --dry-run ``` AI edits can use paid model calls, with three edits per article. Source ingestion and requests for changes can also use paid model calls. A command that lacks `--yes` is not necessarily read-only. ## Respect both plan and key limits An API key adds its own monthly article cap, daily approval/publication cap and request rate limit. These do not enlarge the company’s plan. Cadence has a separate daily generation cap. A person handles purchases and plan changes in Recala. An agent stops and reports a spending refusal. Read [Authentication](https://recala.co/developers/authentication/#caps) for key limits and [Output and exit codes](https://recala.co/developers/reference/#exit-codes) for retry rules.