Billing
How client usage is metered, rolled up, and charged to you as a tech provider
Wexio does not bill your managed clients directly. Usage (messages and AI) is metered per client, rolled up to you once a month, and charged as one usage-based invoice at the rates in your provider contract.
- Clients never appear in Wexio billing. You bill them however you like.
- A managed client org has no plan of its own. It has none of the downgrade enforcement a direct customer sees.
What Changes for Your Own Organisation
Becoming a tech provider (org kind TECH_PROVIDER) replaces retail billing for you and for every client org you provision.
Tech provider and its MANAGED children | A normal org | |
|---|---|---|
| Retail subscription | Cannot open, switch or cancel a plan. Billing is usage-based only. | Picks a plan. |
| Own payment method (children) | Refused. The provider is billed. | Adds a card. |
| Referral rewards | Not granted. | Granted. |
These are enforced server-side. A subscription call from a provider org or one of its children is refused with This organisation is billed by usage or is billing-exempt; retail subscription changes do not apply. (or, for a managed child, Managed client organisations are billed by their partner and cannot manage their own subscription.). Any commercial adjustment goes through your provider contract.
Live Usage
partnerUsageSummary returns the current-period rollup. The full field list is in Usage.
query Usage {
partnerUsageSummary { children opsUnits aiUnits estimatedAmountCents }
}The rollup counts your clients and your own provider org's usage. MCP tool calls are metered to the client named in orgId, the same as GraphQL calls.
Your Rate Card
Your provider contract holds the terms your invoice is calculated from.
| Term | What it means |
|---|---|
| Ops rate | Price per operation unit, in USD. |
| AI rate | Price per AI unit, in USD. |
| Billing day | The day of the month your charge fires. |
Wexio sets these as part of your provider agreement. They are not self-serve, and there is no API to change them. If a term needs to change, talk to your account manager.
Your Allowance Is a Rolling Bank
Your account can hold a free allowance of operations and AI units. Wexio grants it, and it is not refilled automatically each cycle. Usage draws the bank down, and whatever is left carries forward. To add more, ask your account manager.
When your charge is computed:
- The period's total usage is taken from the bank.
- Only usage above the bank is billable.
- Whatever is left in the bank carries forward to the next period.
Ops and AI have separate banks. Unused AI allowance never offsets ops usage, and neither bank goes negative. If your account has no allowance, or the bank runs out, you are billed from the next operation.
The Charge
charge = billable ops × ops rate + billable AI × AI rate
billable = max(0, total usage − bank) // per metricA period with nothing billable produces no invoice. There is no monthly minimum.
A Worked Example
A partner with this contract and bank:
| Term | Value |
|---|---|
| Ops rate | $0.01 per op |
| AI rate | $0.05 per AI unit |
| Ops bank | 5,000 |
| AI bank | 1,000 |
| Billing day | 15th |
In a period where three managed clients between them used 2,750 ops and 560 AI units:
| Ops | AI | |
|---|---|---|
| Bank available | 5,000 | 1,000 |
| Usage | 2,750 | 560 |
| Billable | 0 | 0 |
| Left in the bank | 2,250 | 440 |
The charge comes to $0 because the usage sat inside the bank. The leftover 2,250 ops and 440 AI units stay in the bank for the next period.
Watching the Bank
partnerUsageSummary returns your projected remaining balance.
query Allowance {
partnerUsageSummary {
opsUnits
aiUnits
opsAllowanceRemaining
aiAllowanceRemaining
estimatedAmountCents
currency
}
}opsUnits and aiUnits are total usage, not billable usage. The bank is only netted off when the charge is computed. Read opsAllowanceRemaining and aiAllowanceRemaining for what is left, and estimatedAmountCents for what you will pay.
The remaining balance is a projection of where the bank lands if the period closed now. It is written down only when the period closes and the charge settles, so a failed, retryable charge does not consume your bank for usage that was never billed.
What Wexio Sends You
Your provider organisation receives its own mail, even though your clients receive none.
| When | What |
|---|---|
| Once, when you are set up as a tech provider | An onboarding email pointing at these docs. |
| Each monthly charge that succeeds | A payment confirmation with the per-client breakdown and the allowance used. |
| A charge that fails | A notice asking you to update your card. |
A failed payment does not suspend you. There is no automatic cut-off for a tech provider, and your clients keep working while it is sorted out. Wexio follows up with you directly.
When You Are Charged
Your charge fires on the billing day in your contract, once per calendar month.
| Case | Behaviour |
|---|---|
| No day set | The 1st of the month. |
| A day the month is too short for | Clamped to the last day of that month. A billing day of 31 charges on 30 April and on 28 February. |
A clamped day does not produce a second charge.
What a Client Org Is Like
A client org you provision behaves differently from a retail customer.
| Billing | Usage-based, rolled up to you. No retail plan, no plan limits, no downgrade enforcement. |
| Wexio emails | None. No invites, welcome, mentions, promos or billing mail reaches a client org's members. |
| Who Wexio emails instead | You. See what Wexio sends you. |
| Adding members | Invites are refused with Invites are not available for this organisation; add members directly. Use addOrgMemberDirect, which creates the member already accepted. |
| Functionality | Everything else the product does. |
No platform email means no invite email. A client org's operators never receive a Wexio invitation, so your own product has to get them to a sign-in. Add the member directly, then handle the login journey yourself.
What Clients Cost You
Usage is attributed to the client that caused it, whichever surface produced it.
| Source | Metered to |
|---|---|
| A message sent or received in a client org | That client. |
| A flow card running in a client org | That client. |
| An AI reply in a client org | That client, as AI units. |
A GraphQL call with X-Wexio-Org | The named client. |
An MCP tool call with orgId | The named client. |
The rollup is one invoice to you, but the breakdown underneath is per client, so you can re-bill each customer with your own margin.
Related
- Usage - the
partnerUsageSummaryandpartnerUsageHistoryoperations - Client Orgs - provisioning the clients being metered
- Ops & Usage - what consumes an operation in the first place