Billing and usage

1. 1Open Billing to see the monthly usage meter, the current included-credit balance, and any separate purchased-credit balance.
2. 2Use Last 30 days by feature to review usage grouped by metered kind. Each row combines the recorded count and credit cost for that kind.
3. 3Use the plan-usage meter for the current billing period. The included monthly grant refreshes each billing period; this guide does not assume whether unused included credit carries over.

1. 1Free includes $1 in monthly usage credit.
2. 2Starter includes $10 in monthly usage credit.
3. 3Pro includes $50 in monthly usage credit.

See the pricing usage details for the public rate summary. The Billing breakdown uses these metered kinds:

1. 1AI builder, AI Assist, and knowledge ingest. Input and output tokens are priced from the provider list price multiplied by 1.5×.
2. 2Knowledge answers. $0.002 per invocation, including the query embedding.
3. 3Code runs. $0.003 per wall-clock second.
4. 4Connector calls. $0.002 per invocation.
5. 5Message sends. The initial fallback is $0.001 per message until the Meta delivery status identifies a category. The Fluenta credit rate is then reconciled to Marketing: $0.0015 Utility: $0.0008 Authentication: $0.0006 Service: $0.0004 Free: $0.

Fluenta credits are a platform charge. Meta bills conversation charges directly to the Meta Business account that owns the connected WhatsApp Business Account; Fluenta does not include, resell, mark up, or pass through Meta’s conversation charges.

1. 1Message sends keep working until the total credit balance is 5% of the monthly grant below zero. Once it falls below that buffer, message sending pauses rather than creating silent overage billing.
2. 2Free uses a $0.05 overdraft buffer, derived from its monthly grant.
3. 3Starter uses a $0.5 overdraft buffer, derived from its monthly grant.
4. 4Pro uses a $2.5 overdraft buffer, derived from its monthly grant.
5. 5Add purchased credits from the available top-up presets: $5.00 $20.00 $100.00 . Purchased credit is separate from the monthly plan grant.

A message charge appears before its Meta category is visible.

The initial message charge uses the fallback rate until the delivery-status webhook supplies the category. Fluenta then reconciles its own credit charge to the reported category.

Message sending pauses after the credit balance goes negative.

Check the total balance against the overdraft buffer for the current plan. Add a top-up or wait for the next monthly grant refresh before sending continues.

A Meta invoice does not match the Fluenta credit total.

Treat them as separate charges. Fluenta credit usage is a platform fee; Meta charges the connected business directly for its own conversation pricing.

The Billing view shows a total but not the operation that caused it.

Open the Last 30 days by feature breakdown and compare the count and cost for each metered kind, such as code runs, knowledge answers, messages, or connector calls.