One account, two consoles
Sign in with the same Darkbloom account on both consoles. The account is managed by Privy, and the sandbox console reads the same balance as the inference console.
The split follows the products: inference keys and billing are in the inference console, while CI and sandboxes share the sandbox console. You do not need a second account for either console.

The sandbox console Overview: balance shared with inference, active and recent runs, and Macs online. Example data.
Keys by product
Keys are not interchangeable: an inference key does not authenticate a sandbox, and a sandbox key does not call the inference API.
See API key management for the inference endpoints, and sandboxes quickstart for the CLI login flow.
Find your Account ID
The sandbox console shows your Account ID at Settings → Account ID. Darkbloom uses it to grant access:- Agent sandboxes are invite-only and experimental. Send your Account ID, and the platforms you need (
linux_arm64,macos_arm64, or both), to your Darkbloom contact. - A grant for one platform does not cover the other, and until you are granted the sandbox API answers as if it did not exist.

Settings in the sandbox console: your Account ID and API keys. Example data.
How funds work
Darkbloom uses a prepaid balance in US dollars. Add funds at console.darkbloom.dev with a credit or debit card through Stripe; the minimum deposit is $0.50. Credits are non-refundable, do not expire, and cover every product:- Inference deducts each request’s cost after the response completes.
- CI holds funds when a job starts and settles to the job’s billable time at the rate in effect when it started.
- Sandboxes hold an hour at the sandbox’s size price before each boot and settle to the seconds it ran.
If the balance cannot cover a charge, the product refuses the work instead of going negative: inference rejects the request, a CI job is not started, and a sandbox does not boot.

