Usage-based billing
API and MCP usage is billed on real consumption, separately from your web app plan quotas. Each plan includes a monthly API allowance; beyond it you can enable on-demand billing with a spend cap you choose.
What is metered?
Section titled “What is metered?”| Operation | Metered on |
|---|---|
Meeting processing (POST /v1/meetings) | audio duration, plus the LLM tokens of the AI meeting report (none with transcribe_only) |
Document generation (POST /v1/meetings/{id}/documents, MCP generate_document) | LLM input and output tokens reported by the model provider |
| Reading data (meetings, transcripts, documents, usage) | not billed (only rate limited) |
Every metered operation writes one immutable ledger entry with the tokens or seconds, the model, the unit price
applied, the cost and how it was paid (wallet, on-demand, or written off above the cap). Token counts are flagged
estimated: true in the rare cases where the provider did not report them.
Operations started from the MCP server (by Claude, ChatGPT…) are billed exactly like API calls, on the same ledger.
Wallet
Section titled “Wallet”The wallet of a month is the API allowance included in your plan plus any prepaid or granted credits. The
period is the calendar month (UTC). Each operation is first debited from the wallet. The included amount and the
current unit prices are shown in Settings > Developers and returned by GET /v1/usage (wallet, rates).
API usage never consumes the web app quotas of your plan (hours of audio, documents per period), and web app usage never consumes the API wallet.
On-demand billing
Section titled “On-demand billing”When the wallet is empty:
- if you have an active Standard or Pro subscription and set a monthly spend cap above 0 in Settings > Developers, usage continues and is billed at the end of the period through Stripe;
- otherwise new jobs are refused with
402 insufficient_balance.
When the spend cap is reached, new jobs answer 402 spend_cap_reached. A job already running can go slightly over
the cap: that part is recorded as written_off and never billed.
Alerts
Section titled “Alerts”You receive an email and a usage.threshold_reached webhook when the month’s usage reaches 50, 80 and
100 % of the wallet, and 80 and 100 % of the spend cap.
Check your usage
Section titled “Check your usage”curl -s "$MEETINGIZE_API/usage" -H "Authorization: Bearer $MEETINGIZE_API_KEY"curl -s "$MEETINGIZE_API/usage/ledger?limit=50" -H "Authorization: Bearer $MEETINGIZE_API_KEY"Scope read:usage. GET /usage returns the period, the wallet (included_eur, credits_eur, used_eur,
remaining_eur), on-demand (enabled, spend_cap_eur, used_eur), totals (cost, input and output tokens, audio
seconds, operations), alert thresholds and the current rates. Each job also reports its own usage once metered.
Amounts are EUR decimal strings.