Skip to main content

Billing and Credits

Faberiq bills on a credit wallet: your workspace holds a balance of credits, and executed work spends them. Everything lives under Account, then Billing & Credits (the /billing page), which has three tabs: Billing (overview and subscription), Payments (payment methods), and Credits (buying credits and purchase history).

Two Kinds of Money, Kept Apart​

Do not confuse these:

  • Platform billing (this page): what you pay Faberiq, handled through Stripe checkout on the Billing & Credits page.
  • Your customer payments: what your customers pay you, through your own connected accounts, such as Square quotes and invoices or your own connected Stripe account and Plans. That money never touches your Faberiq credit wallet.

The Credit Wallet​

Your balance is the sum of separate buckets, spent in a sensible order:

  • Trial: new workspaces start with 1,000 trial credits.
  • Subscription: credits granted by an active plan.
  • Coupon: credits added by promo codes.
  • Purchased: credits you bought as one-off packs.

The Billing tab shows the total, a usage bar, your subscription state, and shortcuts to buy credits or manage payment methods.

What Consumes Credits​

Credits are tied to executed work in the workflow runtime, not to seats or channels. Two layers:

  1. Orchestration: each workflow execution costs 1 credit to start (deterministic data-sync runs are exempt).
  2. Per-task charges as the execution moves through its states:
WorkCredits
Agent turn / response composition8
Decision preparation3
Knowledge base search4
Deep research25 base + 5 per research query (4 queries by default, so typically 45)
Receiving a message or email1
Sending a message or email reply2
Calendar availability check3
Calendar event create / update5 / 4
Data read (data.query)5
Data write (data.sync)6
Invoking another workflow4
Any other connector skill4

So a typical channel exchange (receive, agent turn with one knowledge search, reply) costs about 16 credits. A single execution can never spend more than 300 credits, a hard per-execution cap that protects you from runaway loops.

These rates reflect the current runtime and can change as the platform evolves.

Buying Credits​

On the Credits tab:

  • Credit packs: 1,000 credits per pack, priced in CAD (currently 5 CAD per pack), paid through Stripe Checkout. Purchases appear immediately and are listed under Recent credit purchases (your last 10 checkouts).
  • Subscription: the Pro Monthly plan grants a monthly credit allowance (currently 4,000 credits for 20 CAD/month), also via Stripe Checkout.
  • Auto top-up: optionally, when the balance falls below a threshold (400 credits by default), Faberiq automatically charges your saved payment method for a top-up, with a monthly cap so a bug cannot spend without limit.
  • Promo codes: redeem a code to add coupon credits.

The Payments tab manages the cards behind all of this: add a payment method, choose the default, and maintain the billing address.

Running Out of Credits​

When the wallet cannot cover an execution:

  • The run is refused up front with an HTTP 402 Payment Required error ("Payment required to continue execution"). API callers see the 402 directly; in the studio, chat and workflow runs surface the same insufficient-credits error.
  • Channel bots stop answering, because each incoming message tries to start an execution that is refused. Customers simply get silence, so treat a low balance as urgent.
  • Nothing is deleted. Your workflows, connectors, and data are untouched; buy credits (or wait for the subscription renewal) and everything resumes without reconfiguration.

Auto top-up exists precisely to prevent this: with a saved card and auto top-up enabled, the balance refills before executions start failing.

tip

Watch the burn: the Billing tab's usage bar plus the per-task table above make it easy to estimate. A bot handling 100 conversations a day at roughly 16 to 30 credits each needs 2,000 to 3,000 credits daily.