ModelsLab balance checker and read-only wallet token guide

Check ModelsLab without storing a token here

1. Open modelslab.com and sign in yourself; confirm the account used for your API billing.
2. Open your account dashboard and locate the USD wallet/balance section. Compare wallet funding, not plan allowance, requests remaining or generated-model usage.
3. Record the amount and time privately. If the dashboard layout or account context is unclear, ask ModelsLab support; no Key, password, Cookie, recharge or connection is needed in Quota Monitor.

Connect ModelsLab to Quota Monitor

1. 01

   Confirm the account and wallet first

   Open ModelsLab below and sign in yourself to the account that pays for your API work. Open its account dashboard and locate the wallet/balance area; note the USD wallet figure and the selected account, separately from plan usage.

   This walkthrough uses your own account's documented email/password login to issue a control-plane token. If you only have Google/SSO login and cannot use this documented flow, keep checking manually or ask official support for a scoped token. Do not extract browser Cookies or change account permissions.

   Open official ModelsLab page(opens in a new tab)
2. 02

   Prepare a private local HTTP request

   In a local HTTP client you control, disable cloud sync, shared workspaces, request history and logging for this operation. Create a new request: method POST, URL https://modelslab.com/api/agents/v1/auth/login, no Authorization, and Content-Type: application/json. Disable redirect following.

   Choose a raw JSON request body and copy the configuration below. This is a local credential-creation step you perform directly with ModelsLab, not a request sent by Quota Monitor. If you cannot keep the request private, stop and use manual checking.

   Minimal token settings · add your login fields locally

   Copy JSON

   {
     "device_name": "QuotaMonitorReadOnly",
     "token_expiry": "1_month",
     "scopes": [
       "wallet:read"
     ]
   }

   Copies the complete JSON without keys or account details.

3. 03

   Request only wallet:read

   Keep device_name=QuotaMonitorReadOnly, token_expiry=1_month and scopes=[wallet:read] from the copyable JSON. In that same JSON object, add string fields email and password with your own ModelsLab login values locally; use your client's JSON editor so quotes are escaped correctly.

   Verify the destination is exactly modelslab.com, then send once. Omitting scopes grants *; do not remove it or add wallet:write, billing:write or tokens:write. The one-month request may be shortened by account policy. No payment or subscription is required by this tutorial.

4. 04

   Check and save only the returned access_token

   A successful response has error=null and data.access_token. Confirm data.scopes contains exactly wallet:read, check data.expires_at and token_lifetime_capped, and keep a private expiry reminder. If scopes are missing or broader than requested, do not connect that token; contact official support.

   Copy only data.access_token, not data.api_key (the ml- generation key), the JSON response or Bearer text. Save it privately, then discard the local request/response and any credential history. Do not share screenshots, passwords, tokens or the full response in chat.

5. 05

   Add the connection to your project

   In Quota Monitor open your target project, add a provider connection, choose ModelsLab and give it a recognizable name. Paste only the access token into the masked credential field and save. MCP users must use the secure credential-entry link, not send the token to an agent.

   Currency is USD. Leave provider project/key filters empty; no account ID, custom host or account switch is supported. Reuse a connection when projects share one wallet, and check the provider and account before saving.

6. 06

   Wait for the first successful balance sync

   Wait for the scheduled sync or request one balance refresh, respecting the displayed cooldown. Success means a new successful query timestamp and a wallet amount, not merely the presence of a previous amount.

   The server sends only the fixed GET with Bearer authentication and no body, Cookie or redirects. It does not use your login password. A 401 after token expiry needs manual token replacement, not a guessed zero balance.

7. 07

   Reconcile the same account in USD

   Return to the same account dashboard's wallet/balance area and compare the USD wallet figure and observation time with modelslabBalance.balance. The official example data.balance=75.50, currency=USD displays $75.50. Plan allowances, API usage and product subscriptions are not this wallet.

   If figures differ, check account context and reporting time first, then retry after upstream billing settles. Do not add another account, switch context, top up or call a paid model just to test monitoring. Keep actual account validation pending until you reconcile it.

   Open official ModelsLab page(opens in a new tab)
8. 08

   Replace before expiry and retire only the old token

   Before expires_at, repeat the scoped login steps, replace the credential in Quota Monitor's secure form and confirm a successful balance read. The token does not renew automatically and deleting the connection does not revoke it at ModelsLab.

   To retire only the old token, in your private local client send POST https://modelslab.com/api/agents/v1/auth/logout with Authorization: Bearer followed by that old token, with redirects disabled. Official self-revocation needs no extra scope. Never use logout-all or revoke unrelated tokens; discard local credential history afterwards.

What Quota Monitor reads from ModelsLab

• Subscription allowances and wallet funding are separate. No usage subtraction, allowance addition, currency conversion, team aggregation or inferred balance. Duplicate connections can refer to the same money; do not sum them.
• Quota Monitor does not log in, refresh tokens, switch accounts, run models, fund wallets or change permissions. A valid wallet balance does not guarantee that a subscription or a particular model is available.
• modelslabBalance.balance remains an exact decimal string in REST/MCP. Zero and negative balances are retained. Missing/null amounts, non-USD currencies, business errors and failures preserve the last successful snapshot and its timestamp.
• 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.

ModelsLab FAQ and troubleshooting

401 or expired credential?

Check expires_at, revocation and the token type. Repeat the private login flow with wallet:read, then replace only access_token in the secure form. Do not paste the ml- generation key or your password.

403 or insufficient_scope?

Check the token was issued with wallet:read and the account email is verified. A login issued without scopes has full access, not a safer fix. Do not grant write access or switch accounts to troubleshoot; use manual checking or official support.

Google-only login or cannot create a scoped token?

This walkthrough does not implement Google ID-token exchange or create a password for you. Keep manual monitoring and ask ModelsLab for the supported least-privilege setup for your account. Never copy browser session credentials.

Why is the wallet different from my plan allowance?

Subscription allowance is a separate resource and may reset with the billing period. We read the wallet only, not remaining plan calls, a key cap or total spending capacity. A low wallet does not prove every model is blocked.

Two projects show the same balance?

Projects organize monitoring; they do not create provider wallets. Multiple tokens can refer to the same account funds. Do not total duplicate connections or assume switching the website account changes an existing token.

404, 429, 5xx, null or unsupported currency?

Check the latest sync error and time, wait for rate limiting/outages to clear, and contact official support if persistent. Only USD and a valid success envelope are accepted. Old successful data remains labelled with its original time; never change the target URL or infer a zero.

Official ModelsLab references

• Official reference · docs.modelslab.com/agents-api/billing-and-wallet(opens in a new tab)
• Official reference · docs.modelslab.com/agents-api/scopes(opens in a new tab)
• Official reference · docs.modelslab.com/agents-api/authentication(opens in a new tab)
• Official reference · docs.modelslab.com/agents-api/overview(opens in a new tab)
• Official reference · modelslab.com/pricing(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.