Key rejected or HTTP 401?

Check that you copied a complete sk-nano-UUID or legacy UUID API key from API keys, with no header prefix or whitespace. A sk-nano-mgmt- management token and a sign-in/recovery key are different credentials. Check whether the dedicated key was revoked; never send it to support.

HTTP 403 or not comfortable with key privileges?

Confirm the key belongs to the intended account and check the controls shown on the API keys page. No balance-only permission is documented; do not grant team/admin access or remove all spending controls to troubleshoot. Ask NanoGPT support about the restriction or use the official Balance page manually.

USD is zero but Nano or a subscription is available?

This connection deliberately reads only usd_balance. nano_balance is another currency and subscription usage is another measurement. They are not converted or added. Zero USD alone cannot say whether a particular model request can still run.

Balance differs from a key cap, team wallet or another project?

Align the account associated with the API key, the USD field and query time. The endpoint has no documented team selector, and a session-selected team is not proof of this key account scope. Key caps are limits, not money. Do not sum duplicate account snapshots.

HTTP 400, 404, 429, redirects or a response error?

Keep the redacted error code and time. For 429, allow the scheduled retry or wait for the manual-refresh cooldown. Missing usd_balance, malformed responses and transport errors preserve the previous successful snapshot; an old timestamp is not a fresh zero. No Cookie or alternate-host fallback is used.

Can a usage-only management token replace the API key?

No. The Management API documents subscription usage under different authentication; it does not document this USD balance with that token. Do not confuse a subscription allowance with money or expand a management token for monitoring. Real-account validation of this integration is still pending.

NanoGPT Balance & API Key Setup Guide

Awaiting live-account verification

Guide updated 2026-10-14

Implemented from official documentation; real-account verification is pending. Key creation, permissions, account scope and first balance reconciliation still need user testing. Automated checks are not live acceptance.

Required credentials: NanoGPT API key
Monitoring currency: USD · US dollars
What is monitored: Account USD balance; Read-only POST https://api.nano-gpt.com/api/check-balance with x-api-key and no request body. The official usd_balance is already dollars: usd_balance=25 means $25 (scope=account). It is not a Quota Monitor project wallet or key allowance.

Check NanoGPT balance without sharing a key

Open nano-gpt.com/balance and sign in to the intended account.
Read the USD balance separately from Nano, subscriptions and team wallets; note the account and time.
If comparing with Quota Monitor, refresh once and compare the same USD field and timestamp. Never provide a secret to complete this manual check.

Open official NanoGPT page

Connect NanoGPT to Quota Monitor

Confirm the account and USD wallet
Open the official NanoGPT Balance page and sign in to the account your application uses. Record the USD amount and account context before connecting.
Look at the dollar balance, not the separate Nano amount, subscription allowance or a team wallet. You do not need to buy credits or make a model call to set up monitoring.
Open official NanoGPT page(opens in a new tab)
Decide whether you can delegate this key
Open the official API integration page. Under API keys, plan to create a separate key for Quota Monitor instead of reusing a production application key.
An ordinary API key can invoke paid services. The balance documentation does not name a balance-only permission. If guaranteed read-only credentials are required, stop here and use manual checking; do not substitute a management token.
Open official NanoGPT page(opens in a new tab)
Create a dedicated API key
On the API integration page, find API keys and choose Create API key. If a name field is offered, use a recognizable name such as Quota Monitor balance, then complete creation.
Review any key-level controls the actual screen offers. A spending limit can reduce exposure but does not make a key read-only. Do not change or revoke existing application keys; no broad team/admin permission is requested here.
Open official NanoGPT page(opens in a new tab)
Copy the complete API secret securely
Save the complete newly created secret in a trusted password manager. New keys use sk-nano- followed by a UUID; legacy UUID-only API keys are also supported.
Paste only the secret, without Bearer, x-api-key:, quotes or spaces. Never paste a sk-nano-mgmt- management token, sign-in/recovery key, Cookie or browser session, and never send secrets in chat, screenshots, URLs or MCP arguments.
Open official NanoGPT page(opens in a new tab)
Add the connection inside your project
In Quota Monitor, open the intended project, add a provider connection and select NanoGPT (USD). Give it a recognizable connection name and paste the secret into the masked API key field.
Save and attach the connection to that project. No custom API URL, currency selector, upstream project ID, team ID or key ID is needed; the key selects the account.
Run the first read-only synchronization
Wait for the first sync or use Query latest balance. Quota Monitor sends the fixed POST with x-api-key and no body, without making a paid model request.
A successful card shows Account USD balance and a new synchronization time. If it fails, follow the troubleshooting steps below; do not broaden permissions or supply a login session to work around the failure.
Reconcile exactly the same account and amount
Open the official Balance page for the same account and compare its USD amount with the card at a similar time. An official usd_balance=25 is $25; Nano units are not an exchange-rate adjustment.
If values differ, check account context, recent spending, timestamps and which wallet is displayed. REST/MCP nanogptBalance.balance should match the card snapshot. Another project using the same account will show shared funds, not a new wallet.
Open official NanoGPT page(opens in a new tab)
Keep access and verification under control
Use Open provider on the card to return to the official Balance page when funds are low; Quota Monitor does not top up. For rotation, create another dedicated key and update the connection securely before retiring only the old monitoring key.
Real-account verification remains pending. Please check key creation, actual permission behavior, account selection, USD reconciliation and the guide itself. Share only a redacted error code and time if something fails.
Open official NanoGPT page(opens in a new tab)

What Quota Monitor reads from NanoGPT

Only usd_balance is monitored. The separate nano_balance is denominated in Nano cryptocurrency: it is not dollars, is not converted and is never added to USD. A USD zero does not prove the whole account is empty.
Subscription allowances, per-key spending caps, other providers and team totals are excluded. The documented endpoint has no team selector; compare the account associated with this API key, not a default team or a session-selected wallet.
Multiple keys and Quota Monitor projects may share one account balance. Do not sum duplicate accounts or subtract usage again. REST/MCP expose nanogptBalance.balance from the same successful snapshot.
Quota Monitor makes only this read-only balance request. It does not run models, create keys, use login sessions, top up or change permissions. Positive USD funds do not guarantee any model will run.
Zero and negative USD values are preserved. Missing fields, invalid values and failed requests retain the previous amount and timestamp; they never become an invented zero. Snapshot time is not a guarantee of instant provider settlement.
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.

NanoGPT FAQ and troubleshooting

Key rejected or HTTP 401?: Check that you copied a complete sk-nano-UUID or legacy UUID API key from API keys, with no header prefix or whitespace. A sk-nano-mgmt- management token and a sign-in/recovery key are different credentials. Check whether the dedicated key was revoked; never send it to support.
HTTP 403 or not comfortable with key privileges?: Confirm the key belongs to the intended account and check the controls shown on the API keys page. No balance-only permission is documented; do not grant team/admin access or remove all spending controls to troubleshoot. Ask NanoGPT support about the restriction or use the official Balance page manually.
USD is zero but Nano or a subscription is available?: This connection deliberately reads only usd_balance. nano_balance is another currency and subscription usage is another measurement. They are not converted or added. Zero USD alone cannot say whether a particular model request can still run.
Balance differs from a key cap, team wallet or another project?: Align the account associated with the API key, the USD field and query time. The endpoint has no documented team selector, and a session-selected team is not proof of this key account scope. Key caps are limits, not money. Do not sum duplicate account snapshots.
HTTP 400, 404, 429, redirects or a response error?: Keep the redacted error code and time. For 429, allow the scheduled retry or wait for the manual-refresh cooldown. Missing usd_balance, malformed responses and transport errors preserve the previous successful snapshot; an old timestamp is not a fresh zero. No Cookie or alternate-host fallback is used.
Can a usage-only management token replace the API key?: No. The Management API documents subscription usage under different authentication; it does not document this USD balance with that token. Do not confuse a subscription allowance with money or expand a management token for monitoring. Real-account validation of this integration is still pending.

Official NanoGPT 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.