Guide updated
Implemented from official documentation; live-account verification is pending. Key creation, permission behavior and console reconciliation still need your own account test. Automated checks do not replace it.
- Required credentials
- AI/ML API regular API Key
- Monitoring currency
- USD · US dollars
- What is monitored
- Account balance · USD
- GET https://api.aimlapi.com/v2/billing returns current_balance with currency=USD for the authenticated account (scope=account). 25 means $25. Keys and Quota Monitor projects may share this wallet; a key's USD limit is not its own money.
Check AI/ML API balance without sharing a key
- Sign in to the official dashboard with the paying account and select Billing → Overview.
- Read the total USD balance, not Usage spending, a key's USD limit or historical top-ups.
- If necessary, handle funding in the official payment flow and confirm it posts. Manual checking requires no credential to be sent to Quota Monitor.
Connect AI/ML API to Quota Monitor
Confirm the paying account
Open the official dashboard, sign in, then select Billing → Overview. Identify the total USD balance for the account your application actually uses.
Check: this is account funding, not Usage spending or the USD limit on an API key. You do not need to generate content or add money to set up monitoring.
Choose the correct key category
Open the keys page and select API Keys, not Management Keys. Select Create API Key and give the dedicated key a recognizable name such as Quota Monitor balance.
Leave existing application keys unchanged. Management Keys control other keys and are not the credential required here; never provide a browser Cookie or account password.
Review permissions and risk
In the new key's Edit settings, review Endpoint permissions, USD limit and the reset period. Remove unneeded model permissions where supported and Save. Limits reduce spending exposure; they do not make a key read-only.
The documentation does not define a balance-only permission or guarantee that an empty scopes list denies inference. Do not paste an invented permissions policy. If that uncertainty is unacceptable, stop and use the manual check below.
Save the complete secret securely
Copy the new secret while it is visible and store it securely. You need the secret, not the key's name, ID, masked suffix or an Authorization: Bearer header.
Use a dedicated key whose account matches Billing. If the secret can no longer be retrieved, create a replacement; do not send it in chat, a URL, a support ticket or a screenshot.
Add the connection inside your project
In Quota Monitor open the target project → add provider connection → new connection → AI/ML API (USD). Enter a recognizable name and paste the secret into the masked API Key field, then save.
No custom endpoint, account ID or project/key filter is needed. A Quota Monitor project organizes monitoring; it does not create a separate AI/ML API wallet.
Reconcile the first successful sync
Wait for the initial sync, or refresh once the cooldown ends. Check the successful query time and compare Billing → Overview for the same account: current_balance=25 and currency=USD must display $25.
REST/MCP returns the same exact decimal in aimlapiBalance.balance. Account balances are not key spending limits; allow for console rounding and activity between the two reads.
Open official billing when funds are low
Use the card's Open provider button, then Billing → Overview. Confirm the signed-in account before an authorized person decides whether to use Top up.
Quota Monitor never tops up or configures auto top-up. Refresh after the provider posts funds; pending jobs and payment processing can affect when a new balance appears.
Rotate or stop monitoring safely
For routine rotation create a new dedicated key, update the existing connection through the secure form, verify sync, then disable or revoke the old monitoring key. Revoke immediately if exposure is suspected.
Removing a project association does not revoke the upstream key. Other projects may share the connection; handle provider-key revocation and Quota Monitor removal separately.
What Quota Monitor reads from AI/ML API
- The v2 amount is already dollars: do not divide by a credit ratio, subtract usage again or sum the same account across projects. The legacy /v1/billing/balance endpoint is not used.
- The connector makes one read only. It does not request billing details, transaction history, model content or key management, and never runs models, changes permissions or pays.
- Officially reported zero and negative values are preserved. Missing currency, malformed amounts and failed responses keep the previous successful snapshot and time, never fabricate zero.
- observedAt is query time, not a settlement guarantee. In-flight asynchronous work or payment posting can change later balances. Funds do not prove a model or a particular key can run.
- 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.
AI/ML API FAQ and troubleshooting
- What should I do about 401 or 403?
- Check that the complete regular API Key is active and belongs to the intended account. Do not replace it with a Management Key or Cookie or grant broader access just to bypass an error. Review the official documentation or use manual checking.
- Why is my key's limit different from the balance?
- A key allowance limits that key's spending; current_balance is account funding shared by keys. Reaching a key limit can stop its requests even with account money remaining. Quota Monitor does not subtract that limit or label it as funds.
- Why does invalid_response appear?
- Both current_balance and currency=USD are required. Legacy balance-only payloads, nulls, malformed numbers and error envelopes are rejected. The connector does not guess a conversion or retry a legacy/private endpoint.
- What happens after 429 or a failed refresh?
- Wait for the cooldown and check the last successful timestamp. Failed reads keep the old amount and time, not a fresh zero. Share only a redacted error code and timestamp with support.
- Why does the console show a different amount?
- Compare the same account's Billing overview at nearby times. Ongoing jobs, payment posting and display rounding may differ. Do not compare invoices, key limits or another account, or run paid models to test the connector.
- Has a real account passed verification?
- Not yet. Verify the key-creation steps and permissions, then compare a successful Quota Monitor sync and REST/MCP amount with the official dashboard. Deployment and simulated responses are not live-account acceptance.
Official AI/ML API references
- Official reference · docs.aimlapi.com/api-references/service-endpoints/account-balance(opens in a new tab)
- Official reference · docs.aimlapi.com/faq/how-can-i-work-with-my-api-keys(opens in a new tab)
- Official reference · help.aimlapi.com/article/40-starter-guide(opens in a new tab)
- Official reference · docs.aimlapi.com/api-references/service-endpoints/api-key-management(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.