Can I use a new luma-api- key?

No. It belongs to the newer Agents API. This connection validates legacy credentials and does not try them on another domain. An Enterprise Admin read-only key reads enterprise usage, not this legacy wallet.

Why does 7550 become $75.50?

The official legacy schema defines credit_balance in USD cents, including fractional cents. Divide by 100 exactly once. It is not the web subscription's credit count or a dollar amount to display without conversion.

What should I check for 401 or 403?

Check that the dedicated key comes from the correct legacy account and is complete and active. Replace it through the secure form if revoked. Do not add broad permissions, use a password, or send the key to support/chat.

What if I get 404 or a redirect?

Verify whether your legacy API account has retired or migrated. Quota Monitor will not follow redirects with the key or guess a new endpoint. Use the new platform's manual billing page and ask Luma about migration.

Why does the web or another project show a different value?

Web/app subscriptions, the legacy API and newer Agents billing are separate contexts. Compare the account/key and observation time. Multiple Quota Monitor projects may share the same legacy funds and must not be summed.

What happens after 429, 5xx or a missing balance?

Wait for the rate limit or provider incident to clear, then retry within the displayed cooldown. A missing/null credit_balance or error response fails the query. The last successful amount and timestamp remain visible; failure is never turned into zero.

Luma API balance checker and Dream Machine credits guide

Awaiting live-account verification

Guide updated 2026-10-15

Based on official legacy API documentation reviewed on 2026-10-15. Real-account permissions, legacy dashboard availability and amounts await user verification. The newer Luma Agents API is not covered by this connection.

Required credentials: Legacy Dream Machine API key
Monitoring currency: USD
What is monitored: Legacy API Credits · USD; Fixed GET https://api.lumalabs.ai/dream-machine/v1/credits. credit_balance is USD cents: 7550 means $75.50. lumaBalance.balance is credit_balance / 100; balanceCents preserves the original value. scope=legacy_api_account follows the authenticated legacy account, shared by its API keys.

Check the legacy balance without connecting a key

Open the legacy Billing & Credits page and sign in yourself to the API-paying account.
Read the API wallet amount, account context and current time. Keep web/app subscription credits and newer Agents billing separate.
If legacy billing is unavailable or redirects to the new platform, use that platform's own billing page and confirm migration with Luma. No key, paid call or top-up is required for this manual check.

Open official Luma / Dream Machine (legacy API) page

Connect Luma / Dream Machine (legacy API) to Quota Monitor

Confirm you still use the legacy API
Check your existing integration configuration privately. This connection is for api.lumalabs.ai/dream-machine/v1 and the legacy API key that already pays for that service. Open the official legacy Billing & Credits page below and confirm the account and API wallet.
If your setup uses agents.lumalabs.ai/v1 or a luma-api- key, this is the newer Agents API. Its wallet and Enterprise reports need a different integration. Do not send that key here or guess compatibility. Keep checking the new platform manually.
Open official Luma / Dream Machine (legacy API) page(opens in a new tab)
Open the matching legacy Keys page
In the same signed-in account, open the official Keys page below. Confirm the URL begins with https://lumalabs.ai/dream-machine/api/keys and that this is the account whose legacy API balance you intend to monitor.
If the page no longer provides legacy key management, or takes you only to platform.lumalabs.ai, stop. Ask official support about your account's migration status; do not copy a browser session, Cookie, password or an Enterprise Admin key.
Open official Luma / Dream Machine (legacy API) page(opens in a new tab)
Create a dedicated legacy API key
Use the key-creation control on the legacy Keys page, give it a recognizable monitoring name such as QuotaMonitorBalance if a name field is available, and save the full secret privately when shown. Do not replace an application key or revoke a key used elsewhere.
No separate read-only balance scope is confirmed for this legacy API key. It can generate media and spend credits, although Quota Monitor only reads the credits endpoint. If you cannot accept storing that credential, use the manual billing check below instead.
Add the connection in Quota Monitor
Open the target project, add a provider connection and choose Luma / Dream Machine (legacy API). Give it a clear connection name and paste only the dedicated key into the masked credential field, then save. MCP users should use the secure credential-entry link.
Use USD and leave upstream project/key filters empty. Do not enter a host, account override or a copied Authorization header. A Quota Monitor project organizes monitoring; it does not create a separate Luma wallet.
Check the first synchronization
Wait for the first automatic query, or use the refresh action once the displayed cooldown has ended. Confirm there is a new successful synchronization timestamp and a Legacy API Credits amount.
The server performs only GET https://api.lumalabs.ai/dream-machine/v1/credits with Bearer authentication. It does not run a generation, buy credits or follow a redirect. If it fails, read the current sync error; an old amount retaining its old timestamp is not a new success.
Reconcile cents with the correct wallet
Return to the same legacy Billing & Credits page and compare the API balance and observation time. credit_balance=7550 means $75.50; credit_balance=12.5 means $0.125. lumaBalance.balance preserves exact USD and balanceCents preserves the raw USD cents.
Compare neither Dream Machine web subscription credits nor newer Agents balances. If figures differ, verify the account, key origin and billing update time before trying again. Do not make a paid generation or top-up just for verification.
Open official Luma / Dream Machine (legacy API) page(opens in a new tab)
Review shared funds and migration notices
If several projects or keys show the same value, they may share one legacy account wallet. Reuse an existing connection when appropriate and avoid adding those balances together.
Read any Luma retirement notice for your own account. The published migration guide explains new luma-api- keys and the new base URL; it does not establish that the legacy credits endpoint returns a new Agents wallet. Leave the old connection disabled when it no longer represents active billing.
Replace or retire only this monitoring key
To rotate, create a replacement in the same legacy Keys page, update the credential through Quota Monitor's secure form and confirm a successful balance query before revoking the old dedicated key there.
Removing a Quota Monitor connection does not revoke the upstream key. Revoke only the monitoring key you own, never an application key or all account keys. If legacy key management is unavailable after migration, disable this connection and contact official support.
Open official Luma / Dream Machine (legacy API) page(opens in a new tab)

What Quota Monitor reads from Luma / Dream Machine (legacy API)

This is the legacy Dream Machine developer wallet. Dream Machine web/app subscriptions and their monthly credits are separate. The newer Agents API at agents.lumalabs.ai, its luma-api- keys and Enterprise Admin usage reports are not interchangeable with this wallet.
Official migration guidance says legacy models retire on the date in your account notice. Do not create a new legacy account or buy credits just to use this integration. If the legacy Keys/Billing pages redirect you to a different platform, stop here and use that platform's manual billing page.
No usage subtraction, subscription addition or inferred balance. Duplicate connections may reference the same funds and must not be summed. Zero, negative values and fractional cents are retained exactly. Missing/null balances or failed queries preserve the previous successful amount and timestamp; funds do not guarantee generation access.
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.

Luma / Dream Machine (legacy API) FAQ and troubleshooting

Can I use a new luma-api- key?: No. It belongs to the newer Agents API. This connection validates legacy credentials and does not try them on another domain. An Enterprise Admin read-only key reads enterprise usage, not this legacy wallet.
Why does 7550 become $75.50?: The official legacy schema defines credit_balance in USD cents, including fractional cents. Divide by 100 exactly once. It is not the web subscription's credit count or a dollar amount to display without conversion.
What should I check for 401 or 403?: Check that the dedicated key comes from the correct legacy account and is complete and active. Replace it through the secure form if revoked. Do not add broad permissions, use a password, or send the key to support/chat.
What if I get 404 or a redirect?: Verify whether your legacy API account has retired or migrated. Quota Monitor will not follow redirects with the key or guess a new endpoint. Use the new platform's manual billing page and ask Luma about migration.
Why does the web or another project show a different value?: Web/app subscriptions, the legacy API and newer Agents billing are separate contexts. Compare the account/key and observation time. Multiple Quota Monitor projects may share the same legacy funds and must not be summed.
What happens after 429, 5xx or a missing balance?: Wait for the rate limit or provider incident to clear, then retry within the displayed cooldown. A missing/null credit_balance or error response fails the query. The last successful amount and timestamp remain visible; failure is never turned into zero.

Official Luma / Dream Machine (legacy API) 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.