Guide updated
Based on official documentation reviewed on 2026-10-16. Real-account permissions, workspace scope, signed-in navigation and allowance reconciliation await user testing. This is not a cash balance or PAYG wallet integration.
- Required credentials
- Restricted ElevenLabs API key · user_read
- Monitoring unit
- credits · allowance units, not currency
- What is monitored
- Subscription allowance remaining · derived
- Fixed GET https://api.elevenlabs.io/v1/user/subscription, authenticated with xi-api-key. planQuota.used=character_count and limit=character_limit; remaining=max(limit-used,0), overage=max(used-limit,0), all exact integer strings. resetsAt is only next_character_count_reset_unix converted to UTC; null means not reported. refreshPeriod is never guessed. balanceAmount/costAmount/budgetRemaining are null; XXX means no currency.
Check allowance directly in the official console
- Open Subscription and verify the account/workspace; read this period's usage and limit without viewing or sharing a secret.
- Separate subscription counters, rollover, PAYG and per-key caps. Total available credits need not equal this interface's derived remaining allowance.
- Compare the successful observation time with the official reset. Keep unknown dates and pending payment states unknown; ask official support rather than running a paid test.
Connect ElevenLabs · subscription allowance to Quota Monitor
Confirm the account, workspace and subscription
Open the official Subscription page below in the ElevenLabs account you actually use. Check the selected workspace and plan. Read the current period's counters and reset separately from rollover and PAYG; do not record or share any secret.
This is not a cash wallet or a report of every product's available credits. If you only need PAYG funds, a region-specific host or private deployment, check its official billing page manually. Do not top up, upgrade or generate media for this test.
Open API Keys for that workspace
Use the official Developers → API Keys link below; the older Settings API Keys URL redirects there. Check that the account/workspace has not changed. Prepare a separate monitoring key, optionally named QuotaMonitorReadOnly.
Personal keys inherit the user's workspace access and require a Full Seat to create. Existing multi-seat customers can use service accounts managed by their existing admin. If you lack access, ask the responsible owner or check manually; do not buy a seat or raise your role just to monitor allowance.
Enable only the User read permission
When creating the dedicated key, keep Restrict Key enabled and set User to Read, corresponding to user_read. Keep other features inaccessible; do not select Read and Write, user_write, generation or workspace management. A key's own credit quota is a request cap, not the subscription limit shown here. Leave application keys unchanged.
The JSON below is the minimum official service-account key creation body, for an existing service account's admin to use in their own secure tool with the official path and authentication. Personal keys use the UI and do not need JSON. Quota Monitor never creates keys or edits privileges. This read scope still exposes user information; choose manual checking if that is unacceptable.
Minimal existing service-account key body · personal keys use the UI
{ "name": "QuotaMonitorReadOnly", "permissions": ["user_read"] }Copies the complete JSON without keys or account details.
Save the full secret privately and plan rotation
Save the complete secret privately when it is first created; the official UI subsequently shows only its name and last four characters. A key ID, copied header, password, Cookie or screenshot is not the secret. Never place it in chat or MCP arguments. If lost, create a new monitoring key without revoking application keys.
Personal keys have an Expire After selector: choose your policy and rotate before expiry. Service-account keys currently do not expire. An IP allowlist must match the actual server-side egress; if you cannot confirm it, do not guess, widen access or expect Quota Monitor to change provider settings.
Add the connection in Quota Monitor
Open the target project, add a provider connection and select ElevenLabs · subscription allowance. Give it a recognizable name, paste the new secret into the masked field and save. MCP users enter secrets only through the secure setup page; the help drawer does not need the key.
Paste only the key, without xi-api-key or Bearer, JSON, account password or a custom API URL. It is encrypted on save and only the suffix appears in lists. This is not USD monitoring: there is no currency switch, money budget or daily burn configuration.
Check a successful synchronization and the raw counters
Wait for the first sync or use the existing refresh action, then confirm the successful observation time changed. The card shows usage, limit, derived allowance remaining and next reset. Old counters and an old timestamp after failure are not a newly successful query.
For character_count=1000 and character_limit=10000, planQuota.remaining=9000 credits. Usage 12000 against limit 10000 yields remaining=0 and overage=2000 credits, not a money debt. Only the fixed GET is sent: no content generation, top-up or plan mutation.
Reconcile the reset without inventing other funds
Return to Subscription in the same workspace and compare used and limit for the same period. next_character_count_reset_unix is displayed in UTC; null or absence is shown as not reported, never calculated from billing_period. Payment processing can delay updates briefly; check time and subscription scope first.
PAYG, rollover, model-dependent character discounts and key limits can make the console's total credits differ. Compare only the two official subscription counters. Do not infer a top-up's dollar value from total credits or add shared allowance across keys or projects.
Rotate safely and handle expired or denied access
Create a replacement monitoring key with only user_read in the same workspace, replace it using this connection's secure credential update flow and wait for a new successful query before deleting only the old monitoring key in the official UI. Do not revoke application keys or copy generation permissions.
For 401, check the complete secret, expiry, revocation and the owner's workspace access. For 403, check read permission and the IP allowlist; for 429, allow backoff. Share only error codes and times, never keys. If it still fails, check Subscription manually or contact support, without granting admin access.
What Quota Monitor reads from ElevenLabs · subscription allowance
- ElevenLabs renamed characters to credits; credits consumed per text character depend on the model. These counters are not cash, USD value or a number of model calls. Only the authenticated subscription counters are monitored, with no price-based balance or service-availability inference.
- PAYG top-ups, rollover not reflected in these two counters, per-key limits, overage charges and product/agent permissions are not inferred or added. Above-allowance usage is a separate credit count, not an invoice. Multiple keys or Quota Monitor projects may share the subscription: never sum duplicate allowances.
- Only the fixed global api.elevenlabs.io host is used, without account/project/key filters or regional endpoint overrides. Missing counters, errors and failed synchronization preserve the previous successful snapshot and time, never turn null into zero. No monetary budgets, low-funds/runway alerts or paid tests; absent reset dates are not reconstructed from a month or billing cycle.
- The dashboard shows the latest successful allowance or cap snapshot. Refresh cannot remove upstream reporting delays. An old value and timestamp after a failed query are not a new result or a wallet balance.
ElevenLabs · subscription allowance FAQ and troubleshooting
- Why is the key rejected with 401?
- Use the full secret, not its ID or header. Check Expire After, revocation and the owner's workspace access, then confirm user_read. Do not use a Cookie or enable all permissions to debug.
- What should I check for 403 or missing access?
- Have the existing responsible owner verify User: Read under Restrict Key and the server IP allowlist. Read access can still expose user data; use manual checking if unsuitable, never enable management or generation.
- Why does this differ from total credits or a key's limit?
- Only character_count and character_limit derive the subscription remainder. PAYG, rollover absent from those counters, per-key caps and product access are separate. They are not added or converted to dollars using a price estimate.
- Why is reset unknown on an annual or other plan?
- Null/missing next_character_count_reset_unix means unknown; an unknown refreshPeriod remains null. Billing and refresh periods are different. Never assume the first of the month, one month or one year; follow your official account notice.
- What do overage, old counters or 429/5xx mean?
- Overage is a credit count, not an invoice. Zero allowance does not prove model calls are blocked. Allow 429 backoff; 5xx or malformed responses keep the previous successful snapshot. Check its time instead of treating old data as a new query.
- Will this generate content or change a subscription?
- No. It uses only fixed global GET https://api.elevenlabs.io/v1/user/subscription, never paid models, payment, key-management or permission writes, and never follows redirects with a secret. Real-account and signed-in workflow testing remain pending.
Official ElevenLabs · subscription allowance references
- Official reference · elevenlabs.io/docs/api-reference/user/subscription/get(opens in a new tab)
- Official reference · elevenlabs.io/docs/api-reference/authentication(opens in a new tab)
- Official reference · elevenlabs.io/docs/help-center/technical/how-do-i-authorize-myself-using-an-api-key(opens in a new tab)
- Official reference · elevenlabs.io/docs/overview/administration/workspaces/api-keys(opens in a new tab)
- Official reference · elevenlabs.io/docs/api-reference/service-accounts/api-keys/create(opens in a new tab)
- Official reference · github.com/elevenlabs/elevenlabs-python/blob/main/src/elevenlabs/types/permission_type.py(opens in a new tab)
- Official reference · elevenlabs.io/docs/overview/administration/billing(opens in a new tab)
Prepared by Quota Monitor, not an official provider tutorial. Interfaces and permissions may change; check official pages. Verification is limited to the scope stated here.