How credits work

Credits pay for Falconer’s metered work. Go and Pro organizations share one credit balance across their members. Your personal usage records credit spending attributed to you; it is not a separate wallet.

Credits added to your balance

Source	Credits	Expiry
Starting grant	2,000 once per organization	60 days after the grant
Pro subscription	4,000 per purchased seat each month	60 days after each grant
Credit purchase	The pack you purchase	One calendar year after payment

Both monthly and annual Pro subscriptions grant credits every month. Annual payment does not add a year’s credits upfront. See Plans and billing for purchased seats and subscription changes.

The starting grant is issued once, rather than on every sign-in, organization switch or plan change. Buying credits adds to the shared balance without changing your subscription.

Rollover and expiry

Unused credits roll over until their expiry dates. Falconer consumes the credits expiring soonest first. When a grant expires, only its unspent remainder is removed. Buying another pack or receiving another monthly grant does not extend older credits’ expiry dates.

For example, unused Pro credits can remain available after the next monthly grant, but expire 60 days after their own grant date. An unused purchased pack remains available for one calendar year after its payment date.

Owners can inspect expiry dates and the credit history in Settings → Organization settings → Plan and credits. Enterprise agreements can have different terms; see your agreement and the Enterprise Knowledge Health pricing guide.

What uses credits?

AI requests and workflows can use credits for model usage and platform operations. The amount depends on the selected model and the work performed, such as the amount of text processed, searches or generated media. Knowledge Health records usage as it works through a run.

Manually creating, editing and saving documents is free. Activity quantities, such as documents edited or suggested updates applied, describe work performed; they are not a credit price list. An unapplied suggested update is not counted as an applied update. An agent request that drafts an update can still consume credits.

Credit history shows recorded charges and grants. Usage may appear after the request or background work settles; the shared balance is the place to check available funding.

Using your own provider key

When a model request uses your organization’s provider key, the provider bills your organization for that model usage instead of Falconer charging those model credits. Other models and platform operations, including platform-provided embeddings, can still consume Falconer credits. Using your own key does not make every operation free.

Interrupted work and low balances

Ordinary agent turns are charged when they complete successfully. Knowledge Health can already have recorded charges for measured work when a run is stopped, fails or pauses for credits. Stopping a run does not reverse those recorded charges.

Work already in progress can finish beyond the available balance, leaving a negative balance. New work can be blocked until funding is restored, and a monthly spending limit can block a member even when the organization still has credits. When a submitted chat request fails, review the restored draft before sending it again. Funding does not automatically resend ordinary failed chat requests.

Buy credits or manage auto reload when your balance runs low. Track usage and set spending limits to review where credits were spent.