Why do model calls work but balance access fails?

Enable balance-query permission on this exact key. A 403 is a permission error, not zero balance. Share only the error code and time.

Use a complete 302.AI key that is not expired, disabled, or deleted. Keys from other aggregators or upstream providers do not work.

Why is this USD instead of CNY or a key quota?

PTC is defined as USD at 1:1. Actual CNY top-up payments and key limits are different figures.

Why is an old amount still visible after failure?

It is the last successful snapshot. Check its time and the error. Retry rate limits or network errors; missing fields never create a new zero balance.

302.AI Balance Monitoring and API Key Permissions

Live test reported

Guide updated 2026-09-27

A user reported a successful live-account test on September 27, 2026. This does not verify all accounts, permission errors, or MCP flows. Check your own console balance.

Required credentials: API Key with balance-query permission
Monitoring currency: USD · 1 PTC = 1 USD
What is monitored: Shared account balance; The data.balance returned by /dashboard/balance. Shared 302.AI account funds, not a key spending cap or project wallet.

Connect 302.AI to Quota Monitor

Open API Keys for the correct account
Sign in to the account you use and top up. Under Use API → API Keys, create a dedicated Quota Monitor key and set an expiry if needed.
Open official 302.AI page(opens in a new tab)
Enable balance-query permission
Enable balance queries in that key’s permissions and save. No other management capabilities are needed. Consult the official endpoint documentation if the interface changes.
Open official 302.AI page(opens in a new tab)
Connect it to your project
Select 302.AI and enter the full key in the secure field. No account password, login cookie, upstream provider key, or provider project ID is required.
Verify the shared balance
After a successful refresh, compare the same account’s balance, not key daily or total limits. Manual refresh cannot eliminate upstream posting delays.
Open official 302.AI page(opens in a new tab)

What Quota Monitor reads from 302.AI

The API omits currency. The platform defines 1 PTC = 1 USD; no CNY exchange or substitution of top-up payments is performed. Verify on first use.
Applications, API usage, and keys may share funds. Do not add the same balance across projects. Key limits, upstream provider wallets, and automatic top-ups are not queried.
Cash/promotional splits and model availability are not returned and are never inferred. A positive balance does not guarantee a key can call a model.
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.

302.AI FAQ and troubleshooting

Why do model calls work but balance access fails?: Enable balance-query permission on this exact key. A 403 is a permission error, not zero balance. Share only the error code and time.
Why do I get 401?: Use a complete 302.AI key that is not expired, disabled, or deleted. Keys from other aggregators or upstream providers do not work.
Why is this USD instead of CNY or a key quota?: PTC is defined as USD at 1:1. Actual CNY top-up payments and key limits are different figures.
Why is an old amount still visible after failure?: It is the last successful snapshot. Check its time and the error. Retry rate limits or network errors; missing fields never create a new zero balance.

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