Check the complete key from Account → API, its validity and the account it belongs to. Remove copied Bearer/Authorization prefixes and whitespace. Never substitute a Cookie or browser session.

403 or billing_api_not_available?

The key owner must already administer the current team. Custom billing may be excluded even for administrators. Confirm the team's billing eligibility with Resemble; do not widen permissions, switch plans or supply a session Cookie as a workaround.

402 or billing authentication required?

Check billing notices in the official app with the account owner. Quota Monitor never completes payment authentication, charges a card or changes a plan. Do not pay merely to debug this read.

Missing/null total or invalid_response?

The total must be an official numeric balance_cents value. Null is unknown, not zero; the last successful snapshot remains. Valid missing breakdowns appear as unknown. Share only the redacted error and query time.

Confirm account and team access, wait for rate limiting to clear and retry later. A changed endpoint may require an adapter update; do not try a mirror or custom URL. Check whether the displayed timestamp is still old.

Why are balances duplicated or different from credits/usage?

The wallet is shared by the current team; Quota Monitor projects do not partition it. Compare the official USD total, not usage, plan quantities or a voice project's quota. Switching team context can change the selected wallet; verify scope again.

Resemble AI Balance: Team Wallet & API Key Setup

Awaiting live-account verification

Guide updated 2026-10-15

Implemented against official Billing API documentation; real-account verification is pending. Please validate key setup, current-team selection, amounts and these steps. Automated tests are not live reconciliation.

Required credentials: Resemble administrator API key
Monitoring currency: USD · US dollars
What is monitored: Team wallet balance · USD; Fixed GET https://app.resemble.ai/billing/api/v1/wallet. The authoritative wallet.balance_cents / 100 is the current team's USD balance (scope=current_team). balance_cents=4250 means $42.5. Cash and promotional balances are shown separately; they are not added again.

Check Resemble without sharing an API key

Sign in to the official Resemble app and select the team that pays for your API use.
Open its billing/wallet area and read the USD total plus any cash/promotional split. Do not compare product quotas or automatic-reload settings.
Record the team and time. No key needs to leave Resemble; ask its support if a custom billing arrangement has no wallet view.

Open official Resemble AI page

Connect Resemble AI to Quota Monitor

Confirm the billing team
Open the official Resemble app below. Sign in yourself, select the team paying for your API use, and find its billing/wallet area. Note the team, USD amount and time before creating a connection.
Check: compare the wallet, not a subscription allowance, product quantity or voice-project usage. Do not change plans or add funds merely to test monitoring.
Open official Resemble AI page(opens in a new tab)
Check administrator access and key risk
Confirm that the account which will own the key is already an administrator of this current team. The official Billing API requires that role; a working model key alone does not prove billing access.
Check: your organization permits storing this privileged key. There is no documented wallet-only scope or copyable read-only IAM policy. Do not promote a user or expand permissions just for monitoring; use manual checking if this requirement is unacceptable.
Open official Resemble AI page(opens in a new tab)
Open Account → API
Follow the official Account → API link below. Create a dedicated key if the page offers independent key creation, and name it Quota Monitor if naming is supported. Keep the same account and team selected.
Check: do not reset a production key. If the page only exposes one existing key or a regeneration control, stop and ask the account owner about safe rotation; continue with manual checking until custody is approved.
Open official Resemble AI page(opens in a new tab)
Store and copy only the secret value
Save the complete API key in your password manager and copy its secret value into the masked form, without Bearer, Authorization:, quotes or spaces. Resemble uses the standard key for both application and billing servers.
Check: no key is in chat, screenshots, support tickets, browser URLs or MCP arguments. The billing base is /billing/api/v1, not /api/v2; you do not need to type a URL in Quota Monitor.
Open official Resemble AI page(opens in a new tab)
Add the connection inside your project
In Quota Monitor, open the target project, add a provider connection and select Resemble AI (USD team wallet). Give it a recognizable name, paste the key into the masked field and save. MCP users should use the secure setup link, never send the key to the agent.
Check: the currency is USD. There is no team, project or key-ID override. Linking the same connection to another project does not create a separate upstream wallet.
Wait for a successful first sync
Wait for the initial sync, or request the latest balance once. Confirm that the sync succeeded and the query timestamp changed; respect any manual-refresh cooldown.
Check: an old amount can remain after a failure. Read the status and timestamp together. A missing/null total is not zero, and an absent cash or promotional breakdown is not assumed to be zero.
Reconcile the same team's wallet
Return to the same team's billing/wallet area and compare USD totals at similar times. For example, balance_cents=4250 means $42.5. Cash and promotional components are informational, not extra funds to add to that total.
Check: REST/MCP resembleBalance.balance matches the card with scope=current_team. Do not subtract lifetime_consumed_cents again or compare an auto_reload threshold. If the numbers differ, recheck team selection and query time rather than estimating a correction.
Open official Resemble AI page(opens in a new tab)
Maintain access and complete real-account testing
Use Open provider on the card to return to Resemble when funds run low. Only an authorized account owner should decide on payments. For rotation, prepare an approved replacement key, update the connection securely and verify a successful sync before revoking the old monitoring key.
Check: removing a project link or deleting a Quota Monitor connection does not revoke Resemble's key. Report only redacted error codes, timestamps and amount differences; never send the key or full account response.
Open official Resemble AI page(opens in a new tab)

What Quota Monitor reads from Resemble AI

This is the key owner's current team wallet, not a voice project, individual key allowance or Quota Monitor project wallet. Several connections can share it; never sum duplicate balances. Recheck scope after team membership or current-team changes.
Only wallet.balance_cents supplies the total. cash_balance_cents and promotional_balance_cents are breakdowns; _dollars display fields and lifetime_loaded_cents/lifetime_consumed_cents never replace or adjust the total. Promotional credits are not withdrawable cash.
The server sends one uncached GET with Bearer authentication, no body and no redirects. It does not call models, list transactions, change subscriptions, configure auto_reload or initiate payments. The credential itself is not read-only.
REST/MCP resembleBalance.balance, cashBalance and promotionalBalance contain exact USD strings. Missing or null breakdowns remain unknown; a missing/null total or failed read retains the previous successful amount and timestamp, never zero.
Custom billing arrangements may not support this API. A positive wallet does not guarantee access to every product. Query time is not a settlement guarantee; zero and negative amounts are preserved.
The dashboard shows the latest successful snapshot. Manual refresh queries the provider again but cannot eliminate upstream billing delays. An old balance is not a new result after a failed query.

Resemble AI FAQ and troubleshooting

401: key rejected?: Check the complete key from Account → API, its validity and the account it belongs to. Remove copied Bearer/Authorization prefixes and whitespace. Never substitute a Cookie or browser session.
403 or billing_api_not_available?: The key owner must already administer the current team. Custom billing may be excluded even for administrators. Confirm the team's billing eligibility with Resemble; do not widen permissions, switch plans or supply a session Cookie as a workaround.
402 or billing authentication required?: Check billing notices in the official app with the account owner. Quota Monitor never completes payment authentication, charges a card or changes a plan. Do not pay merely to debug this read.
Missing/null total or invalid_response?: The total must be an official numeric balance_cents value. Null is unknown, not zero; the last successful snapshot remains. Valid missing breakdowns appear as unknown. Share only the redacted error and query time.
404, 429 or timeout?: Confirm account and team access, wait for rate limiting to clear and retry later. A changed endpoint may require an adapter update; do not try a mirror or custom URL. Check whether the displayed timestamp is still old.
Why are balances duplicated or different from credits/usage?: The wallet is shared by the current team; Quota Monitor projects do not partition it. Compare the official USD total, not usage, plan quantities or a voice project's quota. Switching team context can change the selected wallet; verify scope again.

Official Resemble AI references

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.