This policy took effect on September 11, 2026, replacing the earlier 500-credit work-email and recurring personal-email allowances. Check the dashboard for your organization’s actual balance, allowance, and next refill date.
How monthly refills work
An eligible work-email organization’s monthly refill restores its balance to the configured allowance on its refill day. Unused allowance is not added to the next month’s grant. A balance already above the allowance is preserved, including extra credits granted by the Context.dev team. Personal-email organizations have no next monthly refill. Downgrading or cancelling a paid subscription does not grant another one-time personal-email allowance.Understand usage
Operations consume different numbers of credits. For example, a standard Markdown scrape or successful Bytes download costs 1 credit, while Answers costs 10 in Fast mode or 100 in Ultra mode. Check the operation’s reference for OCR, actions, or other additional charges. A usable partial response is a successful, billable result. A failed request is not charged API credits. Readkey_metadata.credits_consumed or the operation’s documented credit header when recording usage, and use the dashboard’s per-key filters to investigate changes.
API keys and team roles do not create separate credit balances or spending caps. The organization shares its credits across direct requests and managed workloads. See API keys and Team access.
For paid allowances, limits, and billing options, use the current pricing page and your organization’s billing settings. Owners and Admins can manage billing. Eligible monthly subscribers can also choose a temporary plan pause from billing; follow the displayed dates and credit details before confirming.