Generate unavailable or no API units?

Token creation requires positive API units according to the official instructions. Confirm the account and API page; with no units, check manually first. Do not purchase automatically just for testing or substitute Studio credits, Cookies or someone else's token.

HTTP 401 or token format rejected?

Check the complete token from Profile → API, remove Bearer, quotes and whitespace, and confirm it has not been revoked. A token name, email or browser login token is not sufficient. Never send the secret to support.

HTTP 403 or strict read-only credentials required?

Confirm the account and your organization's authorization rules. Without a documented balance-only permission, this credential cannot be described as read-only. Check manually or ask Recraft support; do not broaden admin permissions or disable application safeguards.

Why is the USD value 1,000 times smaller than API units?

The API returns credits at 1,000 API units = $1. Both raw units and exact USD face value are displayed. Do not subtract already-charged usage again. Payment tax, discounts and Studio subscription allowances are not this balance field.

Different projects show the same amount, or Studio still has credits?

Tokens of one account share API units; Quota Monitor projects only group connections. Never total duplicate snapshots. Studio and API credits are separate. Recraft hosted by another platform must be reconciled with that platform's bill.

HTTP 404, 429, redirect or invalid response?

Record the redacted error code and time. For 429, allow a scheduled retry or the manual-sync cooldown. A 404 or format change needs official-documentation review. Failed reads retain the old snapshot, never infer zero or try Cookies, private endpoints or paid generation requests.

Recraft API Balance: Check Credits & Set Up Your Token

Awaiting live-account verification

Guide updated 2026-10-14

Implemented from official documentation; real-account verification is pending. Token creation, permissions, account scope, balance conversion and these steps still need your own account test. Automated checks are not live reconciliation.

Required credentials: Recraft API token
Monitoring currency: USD · API units face value
What is monitored: API units · USD value; Fixed GET https://external.api.recraft.ai/v1/users/me returns credits for the authenticated API account (scope=account). The official ratio is 1,000 API units = $1. Quota Monitor converts credits / 1000 exactly and retains the raw units. This is not cash, a key limit or a separate project wallet.

Check Recraft balance without sharing a token

Sign in to the official Recraft Profile → API page and confirm the account your application uses.
Read API units, not Studio allowances. 1,000 API units = $1 in face value, not a cash or refund promise.
Note the account and time. Refresh once to compare the same field with Quota Monitor if needed. Manual checking never requires sending anyone your token.

Open official Recraft page

Connect Recraft to Quota Monitor

Find the API balance for the right account
Open the official Recraft Profile → API page below. Sign in with the account used by your application, find its API units balance and note the account, units and time.
Check that this is API billing, not a Studio workspace subscription. If you use Recraft through fal.ai or another host, monitor the platform you actually pay.
Open official Recraft page(opens in a new tab)
Check token prerequisites and authorization
The official Quickstart requires positive API units to use Generate. If your balance is zero or creation is unavailable, check the balance manually first; do not make a purchase just to test monitoring.
A regular token can run paid models. No compatible balance-only scope or read-only policy is documented. Confirm you may authorize this integration under your organization's rules. If read-only credentials are mandatory, stop here; do not supply sessions or admin credentials.
Open official Recraft page(opens in a new tab)
Generate a dedicated API token
On the same Profile → API page, select Generate to create a token specifically for Quota Monitor. Leave application tokens unchanged. If no name field is offered, record its purpose and creation date in your password manager.
Check that you have a new complete token for the intended account. There is no documented read-only scope or permission JSON for this integration; inventing a permission name does not restrict the token.
Open official Recraft page(opens in a new tab)
Copy and store the secret safely
Save the new token in a trusted password manager and copy only its complete secret. Do not include Authorization: Bearer, quotes, whitespace or masked characters; an email or token name is not the credential.
Check that it is an API token, not a sign-in Cookie. Never share it in chat, screenshots, tickets, URLs or MCP arguments. MCP users enter it through Quota Monitor's secure setup link.
Open official Recraft page(opens in a new tab)
Add Recraft inside your project
In Quota Monitor, open the intended project, add a provider connection and select Recraft (API units · USD value). Enter a recognizable connection name, paste the token into the masked field and save.
Check that the connection is attached to the intended project. The token selects the account. No custom API URL, upstream project or key ID is needed; currency is fixed to USD and the credential is stored encrypted.
Run the first read-only sync
Wait for the initial sync or select Query latest balance. Quota Monitor makes only the fixed balance GET: no image generation, token management, purchases or auto top-ups.
Check for a new successful timestamp, USD value and raw API units on the card. If it fails, use the troubleshooting steps below. A previous snapshot is not relabeled as a new successful read.
Reconcile the same account and units
Return to Profile → API for the same account and compare at a similar time. For example, credits=24500 should show 24500 API units and $24.5, not $24500. The formula is credits / 1000.
Check that REST/MCP recraftBalance.balance matches the card's USD value and credits matches the official raw units. Alert thresholds use USD. Do not compare with Studio allowances or a generation request's cost.
Open official Recraft page(opens in a new tab)
Manage funds, rotation and live verification
Use Open provider on the card when units are low. Confirm the account before an authorized payer decides whether to purchase units. To rotate, generate a replacement token, update the connection securely and verify it before revoking only the old monitoring token.
Removing a project association or deleting a Quota Monitor connection does not revoke the provider token. Please test token creation, balances and this guide with your own account; report only a redacted error code and time, never the secret.
Open official Recraft page(opens in a new tab)

What Quota Monitor reads from Recraft

API units are separate from Recraft Studio subscription, free or daily credits. Recraft models hosted by another provider use that provider's billing.
Only credits from /users/me is a remaining balance. The credits field in an image-generation response means that request's cost, not funds left. No generation endpoint is called here.
All tokens of one account share API units. Do not sum duplicate accounts across Quota Monitor projects or subtract usage again. REST/MCP recraftBalance.balance and credits use the same snapshot.
Official instructions require a positive API units balance to generate a new token. If you have none, check manually first. Quota Monitor never buys units or enables auto top-up for setup.
Zero and negative values are preserved. Failed reads or missing/invalid fields retain the old amount and timestamp, never invent zero. Positive units do not guarantee model access. Email, name and user ID are discarded.
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.

Recraft FAQ and troubleshooting

Generate unavailable or no API units?: Token creation requires positive API units according to the official instructions. Confirm the account and API page; with no units, check manually first. Do not purchase automatically just for testing or substitute Studio credits, Cookies or someone else's token.
HTTP 401 or token format rejected?: Check the complete token from Profile → API, remove Bearer, quotes and whitespace, and confirm it has not been revoked. A token name, email or browser login token is not sufficient. Never send the secret to support.
HTTP 403 or strict read-only credentials required?: Confirm the account and your organization's authorization rules. Without a documented balance-only permission, this credential cannot be described as read-only. Check manually or ask Recraft support; do not broaden admin permissions or disable application safeguards.
Why is the USD value 1,000 times smaller than API units?: The API returns credits at 1,000 API units = $1. Both raw units and exact USD face value are displayed. Do not subtract already-charged usage again. Payment tax, discounts and Studio subscription allowances are not this balance field.
Different projects show the same amount, or Studio still has credits?: Tokens of one account share API units; Quota Monitor projects only group connections. Never total duplicate snapshots. Studio and API credits are separate. Recraft hosted by another platform must be reconciled with that platform's bill.
HTTP 404, 429, redirect or invalid response?: Record the redacted error code and time. For 429, allow a scheduled retry or the manual-sync cooldown. A 404 or format change needs official-documentation review. Failed reads retain the old snapshot, never infer zero or try Cookies, private endpoints or paid generation requests.

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