Guide updated
Implemented from BFL's public OpenAPI specification and account documentation. Live-account verification is pending, including signed-in key creation, permissions and organization balance reconciliation. Automated tests are not account verification.
- Required credentials
- BFL API Key
- Monitoring currency
- USD · Credit face value
- What is monitored
- API Credits · USD value
- GET https://api.bfl.ai/v1/credits returns credits for the organization associated with the API key. The key belongs to a BFL project, but funds are shared by its organization. We preserve original Credits and convert exactly at 100 Credits = $1, not into a separate Quota Monitor project wallet.
How to check FLUX API Credits without sharing a key
- Sign in to dashboard.bfl.ai and select the organization that pays for your direct FLUX API usage.
- Open API → Credits and read the balance, not API → Usage. At the official face value, 100 Credits = $1.
- Compare organizations separately. If you call FLUX through another provider, check that provider's billing page instead; no secret needs to be shared for a manual check.
Connect Black Forest Labs / FLUX to Quota Monitor
1. Sign in and identify the organization
Open the BFL dashboard below and sign in with the account that pays for the direct FLUX API. New accounts require email confirmation. Use the organization selector in the sidebar to select the intended organization, then open API → Credits.
Check: you can see that organization's Credits. Note its name and the displayed amount before creating a key. You do not need to create another organization, buy Credits or generate an image merely to connect monitoring.
2. Select a project with key-management access
Within that organization, choose the BFL project used by your application; a new account already has a default project. Open the project's API → Keys. The selected project determines which organization's shared funds this key will query.
Check: you can manage keys. A project Developer can create keys; a Billing Manager is not an API-access role. If you cannot create a key, ask an existing project administrator for help rather than promoting yourself to organization administrator.
3. Create a dedicated monitoring key
On API → Keys, click Add Key, name the new key Quota Monitor, and complete the creation flow. Do not copy an existing production application's key. Naming a key for monitoring does not restrict its permissions.
Check: you accept encrypted storage of a key that can also generate paid content. No verified balance-only policy JSON is available for this connector. If read-only credentials are mandatory, stop and use the manual check section.
4. Save the complete secret before closing
Copy the full secret immediately and keep it in your password manager; BFL displays a newly created key only once. New keys use bfl_, while older migrated keys may retain their original format. If the secret was lost, create a replacement.
Check: you copied the secret, not its name, masked preview or last four characters. Paste only the key, without x-key:, Bearer, quotes, spaces or line breaks. Never place it in chat, screenshots, URLs, support tickets or online API testers.
5. Add BFL to your Quota Monitor project
In Quota Monitor, open the target project → add provider connection → add new connection. Select Black Forest Labs / FLUX (Credits · USD value), enter a recognizable connection name and paste the complete key into the BFL API Key password field, then save.
Check: only one key is required. No upstream project ID, organization ID, API URL or Key ID is needed; the currency is USD. For MCP setup, enter the secret only through the secure Web link, never in the agent conversation.
6. Sync and reconcile the same organization
Wait for the first sync or select Query latest balance and verify a new successful timestamp. Return to the organization owning that key's BFL project and open API → Credits. Compare that balance, not the project's usage totals.
Check: 2450 Credits should appear as $24.5 and 2450 Credits. The exact rule is credits / 100; alert thresholds and daily burn use USD. Do not deduct spending again. Record only redacted amounts, scope and time for first-account verification.
7. Add Credits at BFL only if needed
Use Open provider on the card, select the same organization and open API → Credits. An authorized payer can choose Add Credits, review the amount and complete BFL's payment flow when a purchase is actually needed.
Check: the official balance has updated before refreshing Quota Monitor. Monitoring does not require a purchase or enabling Automatic top-up. Payment methods, taxes and refunds stay with BFL; we never charge your card or change top-up settings.
8. Replace or revoke the monitoring key safely
Create a replacement through the same project's API → Keys, add a replacement connection and verify it. Remove the old connection's project references and delete that connection, then revoke the old dedicated key in BFL's key-management controls.
Check: the replacement uses the intended organization and the old key is no longer active. Removing a Quota Monitor connection does not revoke a BFL key. Do not revoke production keys; if connection slots are full, plan the replacement window first.
What Quota Monitor reads from Black Forest Labs / FLUX
- This is the direct Black Forest Labs API, not FLUX billed through fal.ai, Replicate, Kie.ai or another host. Self-hosted FLUX / ComfyUI and separately billed subscriptions are outside this connector.
- USD face value = credits / 100. It is not withdrawable cash or the amount you paid. No usage is subtracted again, and the API does not provide a cash/bonus split, expiry or per-project allowance. Do not sum the same organization's balance across keys or projects.
- Query time is not guaranteed settlement time. A positive balance does not guarantee model access; permissions, rate limits and account restrictions still apply. Missing, malformed or failed responses keep the last successful snapshot and its time, never a fabricated zero.
- Only the fixed global endpoint api.bfl.ai is used with x-key authentication. No custom host, organization selector, regional fallback, generation request, payment or automatic top-up is performed by this integration.
- 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.
Black Forest Labs / FLUX FAQ and troubleshooting
- Why do I get 401, 403 or an invalid credential?
- Return to the correct BFL project's API → Keys and check that the dedicated key remains active. Re-copy the full secret if available or create a replacement if lost. Remove copied header prefixes and use a direct BFL key, not a fal.ai/Replicate/Kie.ai key. Do not use Cookies or broaden administrator privileges.
- Why is the amount different by a factor of 100?
- The response credits field is measured in Credits, not dollars. 2450 Credits = $24.5. We show both and apply thresholds to USD face value. This is a fixed unit conversion, not a spending estimate, and the two figures must not be added.
- Why do two projects show the same balance, or the wrong organization?
- Keys are project-scoped but Credits are organization-wide. Check which organization owns the project where you created the key; changing the currently selected dashboard organization does not move that key. Use a dedicated key from the intended organization and do not sum duplicated funds.
- Can I use my FLUX key from another host, a read-only role, or a regional endpoint?
- This connector accepts direct BFL project API keys only and uses api.bfl.ai. A console Viewer role is not a verified balance-only API key permission, and Billing Manager does not grant API access. Other hosts, regional-only requirements and self-hosted models should be checked through their own supported billing route.
- What if Credits are missing after a purchase, or a sync returns 429?
- Check the same organization's official Credits and payment status, then wait before retrying after rate limiting. Keep the last successful timestamp in view: a failed read is not a new zero balance. Share only a redacted error code and query time, never keys or raw API responses.
Official Black Forest Labs / FLUX references
- Official reference · api.bfl.ai/openapi.json(opens in a new tab)
- Official reference · docs.bfl.ai/account_management/organizations_projects(opens in a new tab)
- Official reference · docs.bfl.ai/account_management/team_management(opens in a new tab)
- Official reference · docs.bfl.ai/account_management/credits_billing(opens in a new tab)
- Official reference · docs.bfl.ai/quick_start/pricing(opens in a new tab)
- Official reference · docs.bfl.ai/quick_start/get_started(opens in a new tab)
- Official reference · docs.bfl.ai/api_integration/integration_guidelines(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.